Speed is the one part of a website everybody notices and nobody can see. A page that takes four seconds to appear does not look broken, it just quietly loses about half the people who asked for it, and Google reads the same signal your visitors do.
This test loads your page from Australia exactly as a visitor would, then reports what actually happened: how long your server took to answer, how heavy the page is, whether it is compressed and cached properly, and which assets are holding up the first paint. Every finding comes with the specific change that fixes it.
Test my site- Server response time (time to first byte)
- Page weight and compression
- Caching and HTTPS configuration
- Render-blocking scripts and stylesheets
- Image lazy loading, dimensions and formats
What is a good website load time?
Under two seconds to something useful on screen, and under half a second for your server to start responding. Those two numbers are related but different, and the second one matters more than most people realise: time to first byte is how long your server takes to answer at all, and every other optimisation waits behind it. No amount of image compression rescues a site whose server takes a second and a half to think.
Why is my website slow even though it looks simple?
Almost always one of four things. Cheap shared hosting that takes too long to respond. A pile of plugins each doing database work on every page load. Images uploaded straight from a phone camera at eight times the size they display. Or third-party scripts, chat widgets, tracking pixels and embedded fonts, that block your own content from painting while they load.
Do Core Web Vitals actually affect my Google ranking?
Yes, but less than people assume, and content relevance still matters more. Page experience is a genuine ranking signal and it is a tiebreaker between comparable pages. The bigger effect is commercial rather than algorithmic: faster pages convert better, and that shows up in enquiries. Treat speed as a conversion project that helps SEO, not the other way around.
What is layout shift and why does it cost me?
It is the jump that happens when an image or ad loads late and pushes everything down the page. Google measures it as Cumulative Layout Shift, and visitors experience it as tapping the wrong button. The fix is unglamorous and immediate: declare a width and height on every image so the browser reserves the space before the file arrives.
What can this test not see?
This is a genuine measurement of your page from the outside: response time, transfer size, compression, headers and the assets referenced in your HTML. What no external tool can fully measure is the field data Google collects from real Chrome users on real devices and networks, which is what Core Web Vitals ultimately scores. A good result here is strong evidence, not a certificate.
The numbers Google actually uses
Core Web Vitals thresholds, measured at the 75th percentile of real visits.
| Metric | Good | Needs work | Poor |
|---|---|---|---|
| LCP (largest contentful paint) | Under 2.5s | 2.5s to 4.0s | Over 4.0s |
| INP (interaction to next paint) | Under 200ms | 200ms to 500ms | Over 500ms |
| CLS (cumulative layout shift) | Under 0.1 | 0.1 to 0.25 | Over 0.25 |
| TTFB (time to first byte) | Under 0.5s | 0.5s to 0.8s | Over 0.8s |
| Total page weight | Under 1.5 MB | 1.5 MB to 3 MB | Over 3 MB |
How to make a slow website faster
-
1
Measure first
Run the test above so you are fixing the actual bottleneck rather than guessing.
-
2
Fix the server response
Turn on page caching, and move off oversold shared hosting if first byte is over 0.8 seconds. Nothing else matters until this is right.
-
3
Compress and size your images
Serve WebP or AVIF, size them for the space they occupy, and add width, height and lazy loading.
-
4
Turn on Brotli and long cache lifetimes
Text compression and proper cache headers are a hosting setting, not a rebuild.
-
5
Defer non-critical JavaScript
Add defer or async to third-party scripts so they stop blocking the first paint.
-
6
Remove what nobody uses
Audit plugins, tracking pixels and embedded fonts. The fastest asset is the one you deleted.
Fair questions.
Is this the same as Google PageSpeed Insights?
It is a different measurement of the same problem. PageSpeed runs a simulated browser and reports field data from real Chrome users. This test measures your actual server response and page composition from Australia, then explains in plain English what to change. Use both.
My score is fine but the site feels slow. Why?
Usually something that happens after the HTML arrives: heavy JavaScript, fonts that block text from painting, or third-party widgets. The report flags what it can see in the HTML; the rest needs a developer with the site open.
Will this test slow my site down or skew my analytics?
No. It is a single page load, the same as one visitor, and it will not register as meaningful traffic. It changes nothing on your site.
Does hosting really make that much difference?
For time to first byte it is usually the single biggest factor. Moving from oversold shared hosting to decent managed hosting routinely halves the response time on its own, with no code changes at all.
Should I test my homepage or another page?
Test several. Homepages are often the most optimised page on a site. Product, category and blog pages carry more images and third-party code, and are usually where the real problem lives.
Do I need a CDN?
If your visitors are all in Australia and your server is in Australia, a CDN helps less than people expect. If you serve customers overseas, or you have a lot of images, it makes a clear difference.
Why does my score change between runs?
Real networks vary, and so does your server under load. Run it a few times and look at the pattern rather than a single number. The structural findings, compression, caching, image handling, will not move.
Is a perfect score worth chasing?
No. Past a certain point you are optimising for a number rather than a person. Get first byte under half a second, images sensible and nothing blocking the first paint, then spend the remaining effort on the content.
A slow site loses customers and rankings. We make yours load in under two seconds, measured, on real phones.