Playwright-powered scripts
Write standard Playwright scripts in JavaScript or TypeScript. Click, type, navigate, wait for selectors — anything a real user can do.
Synthetic Monitoring
Test the flows
Test the flows
that actually break.
Real headless-browser scripts run from multiple regions on a schedule — login, search, checkout, any multi-step flow. Per-step assertions, screenshots, and full traces captured on failure so you know exactly which step and exactly why.
Free tier included
No credit card
2-minute setup
checkout-flow HealthyLIVE
STEPS6
LAST RUNPass
P954.2s
iad-13800ms
sfo-14100ms
fra-14350ms
sin-15100ms
syd-15400ms
What you get
If it matters to users, script it and monitor it.
HTTP pings confirm the server is alive. Synthetic monitoring confirms the application actually works — that the login form accepts credentials, the cart adds items, and the payment page loads — continuously, from everywhere.
Multi-region execution
Run each script from multiple global locations simultaneously; corroborate failures before alerting so a single-region blip never pages you.
Per-step timing and assertions
Each script step is individually timed and can assert on element visibility, page title, URL, or response status before proceeding.
Screenshots and traces on failure
Every failed run captures a full-page screenshot and a Playwright trace archive so you can replay what the browser saw, step by step.
Configurable schedule and timeout
Run as often as every 5 minutes. Set a per-script timeout up to 5 minutes for flows that cover multiple pages or slow third-party dependencies.
On-demand test runs
Trigger a run immediately from the dashboard or API to verify a fix post-deploy — without waiting for the next scheduled interval.
01 · Catch what pings miss
The server was up.
The server was up.
The checkout wasn't.
An HTTP 200 tells you the server responded. It says nothing about whether the React app hydrated, the payment SDK loaded, or the form actually submits. Synthetic scripts exercise the full user path and fail the moment any step deviates from the expected outcome.
- Test login, search, add-to-cart, and checkout as real user flows
- Assert on DOM elements, text content, and page state at each step
- Detect regressions in SPAs and client-rendered pages that pings skip
login-flow HealthyLIVE
STEPS4
REGIONS5
LAST RUNPass
iad-12100ms
sfo-12350ms
fra-12600ms
sin-13100ms
02 · Debugging made easy
Replay the failure,
Replay the failure,
step by step.
When a synthetic check fails you get more than an error message. Site Qwality stores a full Playwright trace for every failed run — open it in Playwright Trace Viewer to scrub through every network request, DOM snapshot, and action exactly as the browser executed them.
- Full Playwright trace archive attached to every failed run
- Full-page screenshot captured at the point of failure
- Network request log shows which API calls succeeded or timed out
example: checkout script// step 1 await page.goto('https://acme.com/cart');
// step 2 await page.click('[data-id="add-item"]');
// step 3 await page.click('[data-id="checkout"]');
// assert await expect(page).toHaveURL(/payment/);
✓ 4 steps · 3.8s · all assertions passed
// step 2 await page.click('[data-id="add-item"]');
// step 3 await page.click('[data-id="checkout"]');
// assert await expect(page).toHaveURL(/payment/);
✓ 4 steps · 3.8s · all assertions passed
5m
minimum check interval for synthetic scripts
5
global regions execute every script concurrently
100%
of failed runs capture screenshot and trace
$0
free tier — start without a credit card
FAQ
Questions, answered.
Scripts are written in JavaScript or TypeScript using the standard Playwright API. If you already write Playwright end-to-end tests, your existing scripts can be adapted directly for use in Site Qwality.
There is no hard limit on the number of steps. The practical limit is the script timeout, which you can set up to 5 minutes. Complex multi-page flows typically complete well within that window.
Yes. Scripts can fill login forms, handle multi-factor prompts, or use stored session storage tokens. Authentication state can be set up in a beforeAll block and reused across steps to keep run times short.
Every failed run stores a full-page screenshot taken at the point of failure and a Playwright trace archive. The trace can be opened in Playwright Trace Viewer to replay every network request, DOM mutation, and action the browser performed.
Yes. Any script can be triggered on demand from the dashboard or via the REST API. This is useful for verifying a hotfix immediately after a deploy without touching the check schedule.
More of the platform
Explore the rest of the platform
Ready?
Start watching in under a minute.
Every product starts free — uptime, cron, synthetic, logs, RUM, incidents, and status pages. No credit card required.