Website speed test
Measure how quickly your site becomes usable on a phone, and find out exactly which assets are slowing it down.
What we check
Largest Contentful Paint
When your main content actually appears. Google considers under 2.5 seconds good and over 4 seconds poor, and most visitors leave long before four seconds.
Cumulative Layout Shift
How much the page moves while loading. This is why people tap the wrong button and lose their place mid-sentence.
Total Blocking Time
How long the page looks ready but ignores taps. Visitors tap again, decide it is broken, and leave.
Image weight
Oversized and unoptimised images, which are the single most common reason a site feels slow on mobile data.
Render-blocking resources
Scripts and stylesheets that stop the browser drawing anything at all until they have downloaded.
Unused JavaScript
Code that still costs download time, parse time and battery on every single visit even though it never runs.
Why speed is a business problem, not a technical one
Speed is the rare metric that hurts you twice. Slow pages lose visitors directly — people leave before the page finishes — and Core Web Vitals are a confirmed ranking signal, so you also get less traffic to lose in the first place.
It is also unusually fixable. A large share of real-world slowness comes down to a handful of oversized images and a few scripts that did not need to block rendering. Those are afternoon jobs, not rebuilds.
We use Google PageSpeed Insights, so the numbers are the same ones Google uses. Where field data from real visitors exists for your site, that is shown too.
Questions
What are Core Web Vitals?
Three measurements Google uses to describe real user experience: Largest Contentful Paint for loading, Cumulative Layout Shift for visual stability, and Interaction to Next Paint for responsiveness. They are part of how Google ranks pages.
Why is my speed score different each time I test?
Lab measurements vary with network conditions and server load at the moment of the test. Treat a single score as approximate and trends over several runs as meaningful.
What is a good website speed score?
Google treats 90 and above as good, 50 to 89 as needing improvement, and below 50 as poor. Mobile scores are usually lower than desktop, and mobile is what Google indexes.
What if the speed test cannot run on my site?
Some sites block automated testing, and occasionally the API times out on very heavy pages. When that happens the report says performance data was unavailable rather than showing you a number we did not measure, and the rest of your audit still completes.
Run it on your site
One free audit a day. No card, no install.
Related checks
Free website audit
Enter your address and get a complete picture of what is holding your website back — scored, explained, and ra…
Website analyzer
Point it at any address — yours or a competitor’s — and see how the site is built, what it gets right, and wha…
Conversion audit
Traffic that never converts is expensive. Find out what is stopping visitors who were interested enough to arr…