23 July 2026 · 5 min read
Why is my website slow, and what is it costing you?
A slow website costs local businesses real enquiries. Why is my website slow, what actually causes it, and how a freelancer can fix and price the fix.
“Why is my website slow?” is one of those questions a business owner only asks once someone else has already noticed. A landscaper in Kendal is not running speed tests on his own site; he finds out it is slow when a customer mentions giving up and ringing a competitor instead, or he never finds out at all. Page speed is one of the quieter reasons local business websites lose work, because nobody complains about a slow page the way they complain about a broken form. They just leave.
What “slow” actually means
Speed is not one number. The figure that matters most for a first impression is how long it takes before a visitor sees something useful on the screen, not how long the whole page takes to finish loading in the background. A site can look slow even when it technically finishes loading quickly, if the visible content is delayed behind a large header image or a slider that has to load before anything else appears. That is why two sites with a similar total load time can feel completely different to use: one shows the phone number and opening hours immediately, the other makes the visitor wait and stare at a blank space first.
The usual causes on small business sites
A handful of causes account for most of the slow local business sites you will come across. Oversized images are the most common: a photo taken on a modern phone and uploaded straight into a page builder without resizing can be several megabytes, when a well compressed version of the same image would be a fraction of that with no visible difference. Heavy page builder themes and stacks of plugins are another regular culprit, particularly on older WordPress sites where each new feature was bolted on by a different person over several years, and nobody has gone back to remove what is no longer used. Embedded video backgrounds, autoplaying sliders, and fonts and scripts loaded from several different external services each add their own delay, and they add up quietly rather than in one obvious jump. Cheap, oversold shared hosting can be a factor too, though it is worth checking the site itself before blaming the host, since a heavy page will load slowly on good hosting as well as bad.
What it actually costs the business
The honest answer to what a slow site costs is that nobody running a five-page site for a local trade has the analytics set up to measure it precisely, and it is not worth pretending otherwise with an invented percentage. What is observable, rather than measured, is the pattern: a visitor arrives from a search or a recommendation already wanting the business, on a phone, often on the move, and a page that hesitates before showing a phone number or a contact form gives that visitor a moment to reconsider. For a business where the website's only job is to get someone to call or fill in a form, every extra second before that becomes possible is a chance for the visitor to close the tab and try the next search result instead. That is the real cost, not a statistic, and it is worth explaining to a prospect in exactly those terms rather than a made-up number.
How to check, without expensive tools
You do not need a paid subscription to get a useful read on a site's speed. Google's PageSpeed Insights is free, gives a real-world mobile score, and lists the specific issues found on that page rather than just a headline number. Loading the site yourself on an ordinary phone over mobile data, not office wifi, tells you something a lab test cannot: what the actual visitor experiences. And simply counting how many images are on the homepage, and roughly how large the biggest ones are, will often explain most of a slow score before you look at anything else. This sits alongside the wider checks covered in a website audit checklist for local business sites, where speed is one line among several, not the whole story.
Fixing it without a rebuild
Most speed problems on small sites do not need a full rebuild to fix, which matters when you are pricing the work for a client who was not expecting to pay for a new site. Compressing and correctly sizing images is usually the single biggest win for the least effort. Removing plugins, sliders, and embedded widgets the site no longer actually needs is the second, and it is worth asking the client directly whether they even use the feature before removing it, rather than guessing. Switching to a lighter theme or template helps on badly bloated builds, though it is a bigger job and should be scoped and quoted separately rather than folded quietly into a maintenance fee. Where a client's hosting is genuinely poor, moving to a decent host is a small task that is easy to underestimate in how much it improves things.
Turning a speed problem into an easy conversation
Speed is one of the more useful faults to lead a pitch with, because it is provable in seconds and rarely disputed. Show a business owner their own homepage loading on your phone, point at the gap before anything useful appears, and most owners understand the problem immediately without needing it explained in technical terms. That is a more persuasive opening than a general offer to “improve your website”, because it is specific to their site rather than a line that could be sent to anyone.
Finding which local sites are actually slow, rather than guessing from a homepage glance, is the part that takes time when you are doing it by hand for every prospect in a town. Patchscout audits a site's speed alongside its mobile behaviour, SSL and SEO basics as part of every search, so you can see which businesses have a real speed problem before you ever get in touch, rather than finding out on a call. The three free searches on Patchscout are enough to see it against your own town.