Free website speed test. With the video.
Enter your URL. We load it once in a real browser, measure LCP and CLS, plus FCP and TTFB, grade it A to F, and record a video of the load. You get a shareable report link. No signup, no credit card.
- LCP, CLS, FCP, and TTFB from a real browser
- A video replay of your page loading
- One shareable report link
More than a score. A page you can watch.
Real browser, real numbers
We load your page in an actual browser in the cloud, not a synthetic approximation. You get LCP and CLS, plus FCP and TTFB, under controlled conditions.
A clear A to F grade
Every metric is scored against Google’s thresholds and rolled into one letter grade, so you know at a glance whether your page is fast.
A video, on a shareable link
Watch your page actually load. Send the report to your team or client with one link. Most speed tests cannot show you this.
One page is the sample. Peak is the real question.
The free test measures one page, once, with one visitor. Black Friday is many visitors at the same time, moving from product page to checkout. When you want to know whether that holds at your forecast peak, that is a performance test, and it is what Evaluat does.
Speed test questions
Is the website speed test really free?
Yes. Enter a URL and run it, with no signup or credit card. You get the full report, the A to F grade, and the video.
What does Pulse measure?
From a single real-browser page load it captures LCP and CLS (two of the three Core Web Vitals), plus FCP, TTFB, and page-load timings. INP is the third Core Web Vital, but it needs user interaction, so a single cold load does not produce a representative INP. It also records a video replay of the load and rolls the metrics into one A to F grade, which is Evaluat's composite scored against Google's published thresholds, not Google's own grade.
How is this different from PageSpeed Insights or Lighthouse?
Those grade a single page from lab data, and PageSpeed Insights also shows CrUX field data (real-user measurements) when enough traffic is available for your URL. Pulse is a lab measurement in a real browser, and adds a real video of your page loading and a persistent report link you can share. For multi-step journeys or load testing, book a demo to see the full Evaluat platform.
Can I test a logged-in page or a click-through journey?
The free tool tests one page load. To script a journey (sign in, add to cart, checkout) or run it under load, book a demo. That is what the full Evaluat platform does.
Where do you run the test from?
A real browser in the UK or the EU. You pick the location on the form before you run the test.
How long is my report kept?
Reports are permanent. The link keeps working, so you can come back to it, share it, and compare it with later tests of the same page. If you need a report removed, email privacy@evaluat.com and we will delete it.
Is my report public?
Yes. Anyone with the link can open a report, it shows the full URL you tested, and search engines may index it. Tick "Keep this report out of search engines" on the form if you would rather it was not indexed. It stays public either way and still appears in the test history of that page, so do not test a URL that contains anything secret.
Can I see how a page changes over time?
Yes. Every report lists the earlier tests of the same page, and each one opens its own permanent report. Every tested page also has one address that always shows its latest result, with the full history underneath.
What does the what-to-fix list check?
It looks at how the page was delivered and what it downloaded on that one load. That covers the time to first byte, whether the HTML came from a cache, what held back the largest element and what moved in the layout shifts, scripts that blocked the main thread, render-blocking scripts and stylesheets, page weight, image sizes and formats, text compression, redirects, third-party requests, failed requests, the HTTP version, web fonts and console errors. Each finding names the files involved and says what to change, ranked by severity, and the checks the page passed are listed too. It comes from one load under fixed test conditions, so treat it as the place to start rather than a final verdict.
How does Pulse know what a site is built with?
From the same single load. Pulse keeps the evidence the page gave away while it loaded (its response headers, the addresses it requested and its markup), and a language model hosted for us by AWS in the EU reads that evidence to name the platform, frontend, server, CDN and third-party services. Every technology it names has to quote the line of evidence that proves it, and anything it cannot back up is dropped before the report shows it. Nothing extra is fetched from the site. Some sites give very little away, so a short or missing list means the page did not say, not that nothing is there.