Test Scenarios
- Build a journey once. Reuse it everywhere.
- Step-by-step playback with pass/fail per step.
Every virtual user is a real browser. The Core Web Vitals you get back match what your customers actually feel. Not what an HTTP script pretends they feel.
Web Vitals, network logs, console logs, and session video for every virtual user. Not aggregate percentiles. Every session is addressable.
A failure at peak isn't a percentile bump. It's a session. You open it, watch the video, read the logs, and find the request that broke.
How it works
Build a scenario once. Use it as a performance test, a CI smoke test, or a continuous monitor. Same forensic detail comes back every time.
Real-browser performance tests at any scale. Track Core Web Vitals per session and per URL. Find what breaks before peak does.
Tour the platformRun the same scenarios as deployment-gate smoke tests. Catch Web Vitals regressions before they ship, with the per-session detail of a full performance test.
Join the waitlistRun your scenarios continuously from chosen regions. Alert on Web Vitals regressions, with session video to debug them.
Join the waitlistConfigured once at the project level. Captured for every virtual user. Open any session and see exactly what happened.
Push critical paths to 5x, 10x, 20x normal traffic. Find the ceiling before customers do.
Compare two test runs side by side. Catch the regression in the candidate build before it ships, not after a customer reports it.
Set thresholds for LCP, INP, CLS at the URL level. The build fails when a page busts its budget. Not later. Now.
Find the analytics tag, A/B test, or chat widget that's costing you 600ms of LCP. The waterfall makes it obvious.
Run the same scenario from London, Frankfurt, or São Paulo. Compare what your German customers feel vs your American ones.
When the performance test exposes a bug, the session video, network log, and console output for that user are all linked. Find it in minutes.