Why Is My Website So Slow? (And What It's Actually Costing You)
A slow website isn't a minor annoyance — it's a silent revenue leak. Here's what's really causing the lag, and what fast actually looks like.
If you’ve ever loaded your own website on your phone and felt a flicker of impatience waiting for it to appear, that’s not a small thing. That’s a preview of what every visitor experiences, and most of them won’t wait as long as you did.
The number that should worry you
Google’s own research puts it plainly: as page load time goes from 1 second to 5 seconds, the probability of a visitor bouncing increases by 90% (source: Think with Google). Not 9%. Ninety.
That means for every ten people who click through from Google, a search ad, or an Instagram link, several of them are gone before your site even finishes loading. They don’t see your services, your prices, your reviews, or your phone number. They just leave — and you never even find out they were there.
What this actually costs a real business
Say your site gets 1,000 monthly visitors and converts 3% of them into an enquiry — that’s 30 leads. If a slow load time is quietly bouncing 40% of visitors before the page even renders, you’re not looking at 1,000 visitors anymore, you’re looking at 600. Same conversion rate, but now it’s 18 leads. That’s 12 potential customers a month who never even saw what you offer, and it compounds every single month the site stays slow.
So why is it slow?
Most small business websites are slow for a small, repeatable set of reasons:
They’re built on bloated page builders. WordPress with Elementor, Divi, or a stack of a dozen plugins is the most common culprit — see our full breakdown of WordPress vs. a custom build if that’s what you’re running. Every plugin adds its own CSS, JavaScript, and often its own font files and tracking scripts — even on pages that don’t need them.
Images are never compressed. A photo straight off a phone camera can be 4-8MB. On a website, it should be under 200KB. Multiply that difference across a homepage with six images and you’ve added several seconds of pure waiting.
Fonts load from third parties. Every Google Fonts request is a separate trip to another server before the browser can even start rendering your text. It’s a tiny delay that compounds on slow connections.
There’s no real hosting strategy. Shared hosting plans built for WordPress often serve everyone from the same slow server regardless of where your visitors actually are.
Third-party scripts pile up. Chat widgets, heatmap trackers, ad pixels, review-widget embeds — each one is a separate script from a separate server, and most sites accumulate five or six of these over time without anyone auditing whether they’re still needed.
How to actually check your own site
You don’t need to guess. Google’s PageSpeed Insights (free, at pagespeed.web.dev) will score your site out of 100 and tell you exactly which specific resource is slowing you down — an oversized image, a render-blocking script, a slow server response. It’s the same tool Google effectively uses to judge your site for ranking purposes, so it’s worth checking before you spend a cent fixing anything.
What “fast” actually looks like
A well-built site doesn’t need any of that overhead. Static pages, optimized images, self-hosted fonts, and a proper CDN can get a homepage rendering in under a second — not because of a magic trick, but because there’s simply nothing unnecessary left to load.
That’s the difference between a site that was assembled from plugins and one that was actually built. It’s also why speed is one of the first things worth checking before you spend another dollar on ads driving traffic to a page that loses a chunk of visitors before it even appears — and it’s directly tied to whether Google will rank you at all.
If you want a second opinion on where your site is losing people, book a free call — it takes fifteen minutes and you’ll walk away knowing exactly what’s slowing you down.