Fast enough is a published number. Google's thresholds are the largest piece of content painted within 2.5 seconds, a response to the first interaction within 200 milliseconds, and a cumulative layout shift under 0.1. Almost every small business site that fails does so because of images nobody compressed.
That is the whole story most of the time. Somebody uploaded a photograph straight off a phone at four megabytes, the browser has to fetch and decode it before it can paint the page, and a site that would otherwise be quick takes six seconds on a phone with two bars of signal on Route 611.
Why do these three numbers matter?
They are the closest thing to an objective standard anyone publishes, they are measured from real visitors rather than from a lab, and speed is a genuine ranking input rather than a rumour. That said, it is a small input compared with whether your page answers the question.
The bigger reason to care is that people leave. A visitor on a phone who taps your listing and watches a blank screen goes back to the results and taps the next one. You never see it happen and it does not show up as a complaint, which is why it goes unfixed for years.
How do I check?
Run your own site on your own phone, off wifi, from somewhere with ordinary signal. That single test tells you more than any tool, because it is what your customer actually experiences.
Then use PageSpeed Insights for the detail. The field data section is the one to read, because it reports what real visitors got rather than what a test machine got. If there is not enough field data for your site, that itself tells you the traffic is small and speed is not your first problem.
Want to know whether yours passes?
Send us your web address. We will run it against the published thresholds and tell you the one change that would do the most.
Get a free website and marketing auditWhat actually fixes it?
Images, images, then everything else. Resize before uploading, save as WebP, and stop uploading photographs at their original dimensions. A hero image does not need to be four thousand pixels wide, and nobody has ever noticed the difference on a phone.
| Problem | Fix | Effort |
|---|---|---|
| Oversized images | Resize, convert to WebP, set width and height | Low |
| Third party scripts | Remove what nobody uses, load the rest late | Low |
| Too many font weights | Load only the weights the design uses | Low |
| Page builder loading everything | Only where the platform allows it | Medium |
| Slow hosting | Move, but only after the above | Medium |
After images, the usual culprits are a stack of third party scripts, a page builder loading everything on every page, and a font set with nine weights when the design uses three. None of those are exotic and all of them accumulate quietly over years of small additions.
What is layout shift and why do people fail it?
It is the thing where you go to tap a link, an image finishes loading above it, everything moves, and you tap the wrong thing. Deeply annoying, and it is measured.
The fix is mostly to reserve space: give every image its width and height so the browser knows how much room to leave before the file arrives. Late loading banners, cookie notices that push content down and ads inserted after the fact are the other common causes.
Does hosting matter?
Less than the tool reports imply, and more than nothing. Cheap shared hosting can add a slow first response on every request, and no amount of image work fixes that.
The order matters though. Moving host is an upheaval and it is the last thing on the list, not the first, because most sites that feel slow are slow for reasons that travel with them. We have watched a business pay to migrate to faster hosting and gain almost nothing, because the four megabyte hero image moved too. Fix what the page sends before you change where it sends it from, and if the site is still slow afterwards, then the host is a fair suspect.
How fast is fast enough for a local business?
Meeting the thresholds is plenty. Chasing a perfect score is a poor use of money past that point, and we say so to clients who arrive with a report full of red.
The tool score is not the goal. A site scoring in the seventies that loads its content quickly on a real phone is in better shape than one scoring in the nineties that takes four seconds to show anything, and the score can be gamed in ways that make the actual experience worse.
Where we have got this wrong
We once spent most of a day shaving a second off a page load for a client whose real problem was that the page did not say what they did. The site got faster. Nothing else changed. That day would have been better spent rewriting the first paragraph.
Speed is a hygiene factor. Below the threshold it costs you customers; above it, further gains are almost invisible. Get it out of the red, then spend your attention on the words.
Keeping this in shape is part of the website upkeep in the Growth Engine, it is on the checklist for every technical review we run, and the plans that cover ongoing maintenance are on the pricing page.