Small businesses almost always treat speed as a separate chore. First the website, then the copy, then SEO, and somewhere near the bottom of the list sits "make the site faster" as if it were an afterthought. In practice it works the other way round: speed is one of the few things that affects your visibility and your conversion at the same time, and it can be measured objectively on top of that.
That is exactly why Google has been increasingly explicit about it for years. Not because fast sites belong to better businesses, but because a slow page measurably gets abandoned more often. And Google doesn't want to put abandoned pages at the top.
What Google actually measures when it talks about speed
"Fast" isn't a feeling, it's a set of numbers. Google uses three core values, the Core Web Vitals, and each measures something different. Once you know which three, a speed report suddenly becomes readable instead of intimidating.
LCP
How long before the biggest thing on screen — usually your header image or heading — is actually there? Aim for under 2.5 seconds.
INP
How quickly does the page react when someone taps a menu or a button? Anything over half a second feels like a stuttering site.
CLS
Is the layout still jumping while you read? That shifting button you just tapped next to counts here.
An important detail: Google doesn't base this on a quick test from your laptop, but on what real visitors experience in Chrome. Someone looking up your hair salon from a three-year-old phone in a car park counts every bit as much as your fibre connection at the office.
Speed isn't a ranking button, but it is a tiebreaker
This is where a lot of advice goes wrong. Making your site faster won't catapult you from position 14 to position 1. Relevance, content and local signals weigh more heavily. What speed does do is decide between parties who are otherwise roughly level.
And for a local business that is precisely the relevant situation. If three dental practices in the same town all have a tidy site with the same services and comparable reviews, the small differences decide who ends up on top. Speed is one of the few of those differences you have full control over.
Why slow sites lose twice
The sting is in the double hit. A slow page not only scores worse on the metrics Google uses, it also sends visitors back to the search results to click the next link. That behaviour is exactly the signal you don't want to send.
For local businesses that weighs even heavier, because local searches are nearly always mobile and nearly always hurried. Someone searches "emergency plumber" or "sushi delivery near me" and has no patience whatsoever. Waiting three seconds feels like a minute in that moment.
Curious how your site really performs?
We build websites for local businesses that are fast by nature — no heavy themes, no plugin stacks, just a site that ranks and converts.
Where the time usually leaks away
Almost every slow small business website has the same four leaks. It's rarely one big technical disaster; it's usually the sum of things that were once added "just quickly".
- Unprocessed photos — a 4 MB product shot straight from the camera, scaled with CSS instead of actually resized
- Plugins nobody removed — sliders, popups and trackers still loading while no one uses them any more
- Too many external scripts — chat widgets, cookie banners, three analytics tools and a review badge all opening their own connection
- Fonts arriving late — text that is invisible at first and then suddenly shifts once the font lands
Installing a caching plugin and leaving it at that. Caching certainly helps, but mostly it hides the problem: a page with eight uncompressed photos stays heavy, even when it's served neatly from cache.
A practical order for making your site faster
You don't need to be a developer to make progress here. What does help is keeping the right order — the first two steps usually deliver the bulk of the gain.
- Compress your images — resize them to the dimensions they're displayed at and export as WebP. This is nearly always the biggest win.
- Clear out scripts and plugins — remove everything you haven't actively used in the past year.
- Load what isn't immediately visible later — lazy loading for images below the fold, and load your chat widget only after interaction.
- Reserve space for images and ads — fixed dimensions stop the layout jumping while things load.
- Test again on mobile — with a simulated slower connection, not on your own wifi.
Measuring without drowning in tools
You don't need a dashboard full of graphs for this. Google's PageSpeed Insights is enough: paste your URL in and look at the mobile result. At the top you'll see data from real visitors if there is any, below it a lab test with concrete recommendations.
Focus on the mobile score and ignore the temptation to chase a perfect 100. Going from 45 to 80 is something your visitors notice immediately. Going from 92 to 100 usually costs disproportionate effort for something nobody feels.
Conclusion
Speed and SEO aren't two projects you plan separately. They measure the same underlying thing: whether your website gives visitors what they came for, quickly. Google rewards that, and customers reward it too.
For most local businesses the answer isn't complicated engineering but a handful of practical choices: lighter photos, less ballast and a site that was built light from the start. That's an afternoon's work — and it keeps paying for itself as long as your site is online.