Questions we get asked. Real answers.

Evaluat is a real-browser performance testing platform. Every virtual user runs in its own isolated browser instance, so you capture Core Web Vitals (LCP, INP, CLS) and Navigation Timing under load, plus full session video, network logs, and console logs for every user.

No. Evaluat is a hosted commercial platform. Over time we may open-source individual tools, like a Core Web Vitals exporter or the scenario format spec, but the core platform stays closed.

Plans are sized by virtual user-minutes. Tell us roughly on a demo call, and we'll point you at the right tier. See the pricing page for the plan structure.

Mostly no. Reports are written in plain language for non-technical readers, and you can generate an Executive Summary when you need the verdict fast. Building a scenario happens in a visual step editor with no scripts; the one technical bit is pointing steps at the right elements with CSS selectors, which is a job for your developer or your agency. The deeper views (session video, network logs, console logs) are there for them when something needs fixing.

Sales you never see. Visitors leave slow pages before they finish loading, paid clicks land on pages that are not ready, and Google uses page-experience signals (including field Core Web Vitals) among other ranking factors. The honest answer is that the cost is different for every store, which is why we test your actual pages at your forecast traffic instead of quoting industry statistics.

Three common signals. A date is coming when traffic multiplies (Black Friday, a product drop, a press or TV moment). You are changing platform, theme, or checkout. Or the site already feels slower during promotions than on a quiet Tuesday. If any of those apply, one rehearsal will tell you where you stand.

Yes. That is the most common first test: a rehearsal of your real journeys (home, product, cart, checkout) at the number of simultaneous visitors you expect at peak. Generate an Executive Summary for the verdict; the session-level detail shows your team exactly what to fix. Black Friday 2026 is November 27, and fixes need shipping time, so the useful testing window closes earlier than it feels.

Either of you. Some stores run Evaluat themselves and share reports with their agency; some agencies run it for every client through our partner program. Reports have shareable read-only links, so both sides look at the same evidence.

k6 sends HTTP requests and measures how fast your server responds. Evaluat runs real browsers and measures what users actually see: Core Web Vitals (LCP, INP, CLS), plus FCP and 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.

JMeter is a Java GUI-driven HTTP and multi-protocol load tester. It does not render a page in its protocol mode. Evaluat runs real browsers and captures Core Web Vitals. Use JMeter for protocol-level testing (JDBC, JMS, SOAP, FTP). Use Evaluat for the browser-side of your testing. Full comparison.

No. Evaluat tests user-facing applications. If you need to load test a REST or gRPC endpoint, k6 or JMeter is the right tool.

For the customer-facing parts of your app, yes. Pure API and protocol-level testing is a different layer that Evaluat does not cover.

Real browsers. Tell us on the demo call if you have a specific Firefox or WebKit requirement.

The UK and the EU are live today. Tell us what region you need on the demo call. We add regions when customers ask.

Mobile viewport sizing is configurable today. Full device emulation (touch events, device pixel ratio, user agent spoofing) is on the roadmap. Ask on the demo call.

CI integration is the headline feature of Testing Suite, which is planned. Today, Performance Tests run from the UI. Join the Testing Suite waitlist if CI is critical for you.

Five detail 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 the run). You can generate an Executive Summary on top: a plain-language verdict with a health score, the key findings ranked by severity, and recommended fixes. See what a report contains.

Yes. Every report has a shareable read-only URL. No login required to view it. Useful for sharing with customers, contractors, or stakeholders.

90 days on Starter, 12 months on Growth, 2 years on Scale. Configurable on request.

Aggregated metrics export as CSV from report views, and raw console logs are downloadable per session. Session video and full network capture are available in the report UI; bulk raw export of every artifact type is not currently offered.

Plan-dependent. We size concurrency to your forecast peak on the demo call. Higher concurrency targets are available on Growth and Scale.

Each virtual user runs in its own browser instance with its own cache, cookies, and network stack, so session state does not cross between users. Instances still share host compute; the contention you measure is real browser work under the selected test conditions, not a shared-browser approximation of many users inside one process.

Modern headless browsers can render pages and collect paint metrics. The Evaluat difference is not headed versus headless. It is one isolated browser per virtual user under load, with Core Web Vitals, session video, network logs, and console output retained for every session so you can debug the exact run that failed.

Yes. Because each virtual user is a real browser, single-page apps render and execute under the selected conditions: client-side routing, hydration, lazy-loaded chunks. Web Vitals come from that controlled browser session, which is the right instrument for experience under load (and different from field CrUX data).

You pay for how much you test, not for which diagnostic features you may use. Plans are sized by virtual user-minutes: one virtual user running for one minute equals one VU-minute. A 1,000-user test for an hour consumes 60,000 VU-minutes. Each plan has a monthly VU-minute allowance; seats, domains, regions, concurrency, retention, and support scale by tier.

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.

Yes. Every plan can be billed monthly or annually. Annual contracts get a discount versus monthly. Speak to us about specifics.

We alert you when you approach the cap and soft-stop at 100% by default. Top-up packs and metered overage are available on request. We do not auto-bill overages without your say-so.

Test data resides in the region the test ran in: run a test in the UK and its data stays in the UK; run it in the EU and it stays in the EU. Exact storage layout for each artifact type is described in our Privacy Policy, DPA, and Sub-processors list. If you have a specific residency requirement, talk to us before you start. If you have a specific residency or compliance requirement, talk to us.