Most small business owners have never seen their own website the way a customer sees it. You load it on your office wifi, on a laptop, with the whole thing already cached. It appears instantly. It seems fine.
Your customer is standing in a car park on one bar of signal. For them it takes nine seconds. Most of them do not wait.
The number that matters
Google has published the research on this repeatedly, and the pattern is consistent: as a page goes from one second to three seconds, the probability that someone leaves rises sharply. By five seconds it is worse again. By ten, most of the visit is gone.
For a local business this is not an abstract statistic. If forty people a week search for what you do, find you, and a third of them leave before your page appears, that is thirteen enquiries a week going to whoever loads faster.
Check yours in two minutes
Open PageSpeed Insights, paste your website address, and read the mobile score, not the desktop one. Desktop scores flatter everybody.
Under 50 is a genuine problem. 50 to 89 is the normal range for a small business site and there is usually easy work to do. Over 90 means speed is not what is holding you back.
Look at the field data section too, if it appears. That is real Chrome users on real connections, and it is more honest than the lab test underneath it.
What is usually to blame
In our experience auditing local sites, four things account for most of the damage.
Uncompressed images. By far the most common. Someone uploaded a photo straight from a phone camera — four thousand pixels wide, six megabytes — and the page displays it at four hundred pixels. The browser still downloads the whole thing.
Plugin sprawl. A WordPress site that has accumulated twenty-six plugins over six years is loading twenty-six sets of scripts and stylesheets, most of them on every page, most of them unused.
Page builders. Tools that let you drag and drop layouts generate enormous amounts of markup to stay flexible. That flexibility has a weight, and the visitor pays it.
Fonts loaded from somewhere else. Every external font request is a round trip to another server before any text can appear. Self-hosting the same font removes the wait entirely.
What you can fix without a developer
Two of these you can address yourself this afternoon.
Resize your images before uploading them. Nothing on a normal web page needs to be wider than about two thousand pixels, and most photos look identical at a tenth of the file size once compressed.
Then audit your plugins. Deactivate anything you cannot immediately explain the purpose of, and check the site still works. Most sites we look at can lose a third of them without anyone noticing.
When it is worth rebuilding instead
There is a point where patching stops paying. If the site is on an old page builder, if the theme has not been updated in years, or if every fix reveals two more, the arithmetic changes — you can spend $2,000 in developer hours making a slow site slightly less slow, or rebuild it properly for less.
That is the judgement our free audit is meant to help you make. Send us your website address and we will tell you which side of that line you are on, including when the answer is that your site is fine and you should spend the money elsewhere.