Test Scenarios
- Build a journey once. Reuse it everywhere.
- Step-by-step playback with pass/fail per step.
BEYOND HTTP-SCRIPT TESTING
HTTP scripts pretend. Real browsers measure.
Every virtual user is a real browser. Web Vitals captured at load. Network logs, console logs, and session video for every user. The numbers match what your customers actually see.
Trusted by
The platform
Performance reports built for engineers.
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.
It's a session. Open it. Watch the video. Read the logs. Find the request that broke.
How it works
The lineup
One platform. Three products.
Build a scenario once. Use it everywhere. Performance test, CI smoke test, continuous monitor. Same scenario, same configuration, same forensic detail comes back every time.
Performance Testing
Real-browser performance tests at any scale. Track Core Web Vitals per session and per URL. Find what breaks before peak does.
Tour the platformTesting Suite Soon
Run the same scenarios as post-deploy smoke checks. Catch Web Vitals regressions before they reach customers, with the per-session detail of a full performance test.
Join the waitlistMonitoring Soon
Run your scenarios continuously from chosen regions. Alert on Web Vitals regressions, with session video to debug them.
Join the waitlist What's in the box
Configure the run once. Capture everything from every virtual user.
Configured once at the project level. Captured for every virtual user. Open any session and see exactly what happened.
Datasets
- Inject unique data into every virtual user.
- Search terms, SKUs, UTM parameters, accounts.
Popup Handlers
- Dismiss cookie banners, modals, and consent dialogs.
- Configure once at the project level.
Regional execution
- London (UK) and Frankfurt (Germany) today; more regions as customers need them.
- Configurable browser locale and timezone.
Core Web Vitals capture
- LCP, INP, CLS, FCP for every virtual user.
- Aggregated by run, addressable per session and URL.
Network Logs
- Every request, every user, every byte.
- Searchable across millions of rows per run.
Console Logs
- Every console message from every virtual user.
- Deduplicated and counted across the run.
Session Video
- Watch any virtual user's browser end-to-end.
- Step playback timestamped to the millisecond.
In practice
How engineering teams use Evaluat.
Capacity rehearsals
Push critical paths to 5x, 10x, 20x normal traffic. Find the ceiling before customers do.
Release validation
Compare two test runs side by side. Catch the regression in the candidate build before it ships, not after a customer reports it.
Web Vitals budgets
Set thresholds for LCP, INP, CLS at the URL level. The build fails when a page busts its budget. Not later. Now.
Third-party tag analysis
Find the analytics tag, A/B test, or chat widget that's costing you 600ms of LCP. The waterfall makes it obvious.
Regional performance
Run the same scenario from London and Frankfurt. Compare what your German customers feel vs your British ones.
Forensic debugging
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.
For AI agents
Developer and agent reference Agent-ready.
AI coding agents can run a real-browser speed test through the Evaluat MCP server, then read back Core Web Vitals and watch the video. One honest tool, no API key.
Common questions
Questions we get asked.
What is Evaluat?
Evaluat is a real-browser performance testing platform. Every virtual user runs in its own isolated browser instance, so you capture Core Web Vitals and Navigation Timing under load, plus full session video, network logs, and console logs for every user.
How does Evaluat differ from k6?
k6 sends HTTP requests and measures how fast your server responds. Evaluat runs real browsers and measures what users actually see: LCP, INP, CLS, plus the full network and console for every session. Use k6 for API load tests. Use Evaluat for the customer-facing parts of your app. See all comparisons.
How does it compare to JMeter?
JMeter is a Java GUI-driven HTTP and multi-protocol load tester. It can't render a page. Evaluat runs real browsers and captures Web Vitals. Use JMeter for protocol-level testing (JDBC, JMS, SOAP, FTP). Use Evaluat for the browser-side of your testing. Full comparison.
Does Evaluat do API testing?
No. Evaluat tests user-facing applications. If you need to load test a REST or gRPC endpoint, k6 or JMeter is the right tool.
What's in a test report?
Five views: Overview (aggregate Web Vitals, time-series), URL performance (every URL with its own metrics), Sessions (every virtual user, individually addressable, with video), Console logs (deduplicated and counted), Network logs (every HTTP request, searchable across millions). More on reports.
What does "isolated browser" mean?
Each virtual user runs in its own browser instance. Its own memory, CPU, cache, cookies, and network stack. Nothing crosses between users. The contention you measure is real, not what a shared-browser model approximates.
How is that different from headless testing?
Headless browsers (puppeteer, playwright in headless mode) skip the rendering pipeline. Great for end-to-end test automation. Useless for accurate paint timings. Evaluat runs full browsers with the rendering pipeline so Web Vitals match what users actually see.
Is there a free trial?
We don't run a self-serve trial. Every onboarding includes a 30-minute demo on your real site, with a small test run live. The report from that demo is yours to keep, whether you go ahead or not.
More answers on the FAQ page.