
Speed
Why is my website slow?
5 min read
See how long your site takes to load on a phone and a computer, tested from Sydney, plus what's slowing it down and which fixes make the biggest difference.
How long your main content takes to appear on a phone.
The same test on a desktop-sized screen.
Photos that are bigger than they need to be.
Scripts and styles that hold up the first paint.
How quickly your hosting answers each request.
Whether the page jumps around while it loads.
The total size of everything the page downloads.
Google’s PageSpeed Insights is the tool most people know, and it’s a good one. It tests your page from Google’s own servers, which are usually outside Australia, and it deliberately slows the connection down to imitate a mid-range phone on a weak 4G signal. That’s a useful worst case, but it isn’t what most of your customers see, and the overseas round trip makes Australian sites look slower than they are.
Our speed test runs the same engine Google uses, Lighthouse, on our own machines in Sydney. We load your page twice, once as a phone and once as a desktop computer, with no artificial slowdown on the connection or the processor. The load times you see are the times we measured. Your speed score is then worked out from those timings using Lighthouse’s own scale for fast connections, with the phone result counting for 70% of it because that’s where most of your visitors are.
When Google has enough visitors to publish data on how real people experience your site, we show that as well, in its own box beside the score. It covers the last 28 days of Chrome users on phones. We keep it separate so that every site is scored the same way, whether or not it gets enough traffic for Google to report on.
The other difference is what happens after the numbers. PageSpeed Insights gives you a long technical list. We translate the results into plain English and put the fixes in order, starting with the one that will make the biggest difference for the least effort.
A score of 90 or more is good, 50 to 89 needs work, and anything under 50 is poor. The score is a summary, though, and the timings behind it tell you more. These are the bands Google uses for the three Core Web Vitals and the other numbers in your report.
| Measurement | Good | Needs work | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP): when the main content appears | 2.5 seconds or less | Up to 4 seconds | Over 4 seconds |
| Interaction to Next Paint (INP): how quickly a tap gets a response | 200 milliseconds or less | Up to 500 milliseconds | Over 500 milliseconds |
| Cumulative Layout Shift (CLS): how much the page jumps around | 0.1 or less | Up to 0.25 | Over 0.25 |
| Time to First Byte (TTFB): how quickly your hosting answers | 0.8 seconds or less | Up to 1.8 seconds | Over 1.8 seconds |
INP can only be measured from real visitors tapping on your page, so it appears in the real-visitor box when Google publishes it. If PageSpeed Insights has told you your site’s Core Web Vitals assessment failed, it means at least one of the top three is outside the good band for real visitors. Our guide to Core Web Vitals and the “assessment failed” message explains what to fix first.
Every speed test is a single load of your page at one moment, and several things change from one moment to the next. Your hosting might be busier, or an advert or chat widget might load a different, heavier script on one run than the next.
A few points either way is normal and doesn’t mean anything has changed. A drop of ten points or more usually does. If that happens, check what changed on your site recently: a new plugin, a new tracking script or a new hero image are the usual suspects. Our guide to why websites are slow walks through the common causes.
Scores from different tools will also differ, because they test from different places under different conditions. Compare your site with itself over time, using the same tool each time.
Real examples of what a speed report flags, and what to do about each one.
What it means
It's the main thing visitors wait to see, so every extra kilobyte holds up your page on a phone.
What to do
Resize it to the width it's shown at (1600px is plenty) and save it as WebP. It should drop under 200 KB.
What it means
The browser has to download these before it can show anything, so visitors stare at a blank screen.
What to do
Ask your web person to defer non-essential scripts and inline the critical styles.
Most people give up on a page that takes more than about 3 seconds to load, and most small business customers are on their phones. A slow site quietly loses enquiries you'll never know about, and Google ranks faster sites higher too.
Image fixes are often a do-it-yourself job. Slow hosting, heavy themes and too many plugins are a job for your web developer or a speed specialist.
See top-rated speed providers
Speed
5 min read

Speed
5 min read

Speed
4 min read
PageSpeed Insights tests from outside Australia and slows the connection to imitate a weak 4G signal. We test from Sydney without any slowdown and score the timings we measure, so our numbers are usually faster.
On mobile, aim for your main content to appear within about 2.5 seconds. Under 4 seconds is okay. Anything slower is losing you visitors.
Only if your server response is slow. If the report says your hosting is quick, the problem is the page itself: usually big images or too many scripts.
Rarely. Most slow sites get much faster by compressing images, removing unused plugins and turning on caching. A rebuild only makes sense if the theme itself is very heavy.
Paste your web address and see your load times in about a minute.