Your site is slow where it matters most
It loads instantly — on office fibre, on a desktop, from cache. Now stand in a lane outside Brighstone with two bars and open it on a five-year-old Android. That is the load that decides whether you get the enquiry.
Your site loads instantly. You have checked. On the office broadband, on a desktop, with everything already cached.
Now stand in a lane outside Brighstone with two bars of signal and open it on a five-year-old Android. That is the load that decides whether you get the enquiry, because that is where a decent share of your customers actually are when they look you up.
The score is not the experience
A high Lighthouse score and a site that feels slow are entirely compatible. The default test runs on a fast connection from a machine far more capable than the phone in your customer's hand. It is a useful signal, not a verdict.
The number that matters is how long it takes before the person can read something and tap something, on a mid-range phone on mobile data. Everything below is aimed at that.
It is almost always the images
On small business sites, images are the problem far more often than anything else. A photo straight off a modern phone is four or five megabytes. Put six of them on a homepage and you have built a thirty-megabyte page, which on a weak connection is not a slow page, it is a page that never arrives.
- Resize before uploading. If it displays at 800 pixels wide, it does not need to be 4,000.
- Compress. Quality around 70 to 80 is visually indistinguishable and a fraction of the weight.
- Use modern formats. WebP or AVIF where you can, with a JPEG fallback.
- Set width and height. Costs nothing, and stops the page jumping around as images arrive.
- Lazy-load anything below the fold. No reason to download the footer photo before the visitor has read the headline.
Doing only this, properly, fixes the majority of slow small business sites.
The third-party tax
Count what your site loads from somewhere other than your own server. A chat widget, two analytics tools, a font service, a booking embed, a review carousel, a cookie banner to manage the consequences of the rest. Each one is a separate connection, and on mobile data each connection is expensive before a single byte moves.
Go through them and ask what each one earns. The chat widget nobody has answered in four months is costing you real load time to do nothing.
Fonts
Web fonts are worth having and easy to get wrong. Self-host them rather than pulling from a third party, load only the weights you actually use, and set font-display: swap so text is readable immediately in a fallback rather than invisible while the font downloads.
Things that move after they appear
Everyone knows the feeling: you go to tap a link, an image loads above it, the page shifts, and you tap an advert instead. That is layout shift, Google measures it, and it is almost entirely caused by not reserving space for things that load late.
Set dimensions on images and embeds. Give banners a fixed height. It is unglamorous and it makes a site feel twice as solid.
What to fix first
- Resize and compress every image on the site.
- Remove third-party scripts nobody uses.
- Add width and height attributes to images.
- Lazy-load everything below the fold.
- Then, and only then, worry about the clever stuff.
That order is deliberate. The first four are cheap, safe, and account for most of the gain. Everything after them has a worse ratio of effort to result.
How to test honestly
Open Chrome DevTools, go to the Network tab, and throttle to Slow 4G. Run PageSpeed Insights and read the mobile tab, not the desktop one. Then do the thing most people skip: take your own phone off wifi, drive somewhere on the Island with a weak signal, and load your own site.
It takes ten minutes and it tells you more than any score will.