A slow website is the most expensive problem you can’t see. Nobody emails to say “your site took nine seconds so I bought from your competitor.” There’s no error, no crash, no complaint. Visitors just quietly leave, and from where you sit everything looks fine — right up until you wonder why the phone’s been a bit quiet this year.
I’ve diagnosed a lot of slow websites over 12+ years in IT, and there are two things I can tell you before we even look at yours. First: the cause is almost never what the owner suspects. Second: it’s almost never mysterious. Slow sites aren’t cursed — they’re carrying too much weight and standing on cheap foundations, and both of those things are fixable in a very ordered way.
Let’s make the invisible visible: why speed is money, what’s actually slowing sites down, and which fixes genuinely move the needle — versus the ones people burn weekends on for nothing.
First, why speed is money — the receipts
The connection between load time and lost customers is one of the best-studied things in web performance, so we don’t have to hand-wave.
Google’s research found that as a mobile page’s load time stretches from 1 second to 3 seconds, the probability of a visitor bouncing rises 32% — and from 1 second to 10 seconds, it leaps 123% (Google/SOASTA, 2017). Every second your page dawdles, a measurable slice of your would-be customers gives up and taps the next result. You never see them go. That’s the cruel part.
It cuts the other way too, and this is the number that made me sit up when it was published: in a study with Deloitte, Google found that improving mobile load time by just 0.1 seconds lifted retail conversions by 8.4% and average order value by 9.2% (Google + Deloitte, “Milliseconds Make Millions”, 2020). A tenth of a second — a duration you physically cannot perceive — moved revenue by whole percentage points. Speed isn’t a technical vanity metric. It’s margin.
Now the state of play: most of the web is failing this test. The 2025 Web Almanac found only 48% of mobile sites pass all three of Google’s Core Web Vitals — the metrics Google itself uses to judge real-world page experience (HTTP Archive Web Almanac, 2025). More than half the mobile web doesn’t clear the bar, which has a silver lining: clearing it is a genuine way to stand out, in both user experience and search.
And all of this matters most on a phone, because that’s where your visitors are — worldwide, mobile is now 50.29% of all web traffic (Statcounter, May 2026). Your slow page is usually a slow page on a phone, on mobile data, held by someone with somewhere else to be.
What actually slows a site down
Here’s the diagnostic leaderboard, in the order we actually find these things in the wild. Notice that “mysterious gremlins” doesn’t feature.
1. Enormous, unoptimised images. The number one culprit, by a distance, and I will die on this hill. It goes like this: the photographer sends over beautiful 6 MB images straight off the camera, they get uploaded exactly as received, and now every single visitor downloads a poster-sized file to view a picture the size of a postage stamp. Multiply by every image on the page. Properly resized, compressed, modern-format (WebP/AVIF) images routinely cut a page’s total weight by more than half — same photos, same quality to the eye, a fraction of the wait.
2. Plugin and page-builder bloat. The WordPress classic. Every plugin can load its own scripts and styles on every page, whether that page uses the plugin or not. One is nothing. Twenty-five, plus a heavyweight drag-and-drop page builder, and the browser is downloading and executing a small mountain of code before it’s allowed to show your headline. The record I’ve personally seen was over seventy plugins on one site — including three sliders, one of which appeared to exist purely to referee a conflict between the other two. (This is also a security problem, but that’s another article.)
3. Cheap shared hosting. For a few dollars a month, your site shares a server with hundreds of strangers — and your speed is hostage to their traffic. The tell is a slow “time to first byte”: the server takes an age to even begin responding. No amount of front-end optimisation can fix this, because the problem happens before your beautifully optimised page gets a chance to exist. You can’t out-tune a bad foundation.
4. No caching, no CDN. Without caching, your site laboriously rebuilds every page, from scratch, for every visitor — like a restaurant cooking the entire menu fresh each time anyone orders anything. Without a CDN, a visitor in Perth is pulling every file from a server in Sydney or further. Both are solved problems with mature, boring solutions — if someone has actually set them up. Frequently nobody has.
5. Third-party script pile-up. The chat widget, two generations of analytics tags, the Instagram feed embed, a marketing pixel from a campaign that ended in 2024. Each one phones home to someone else’s server, and any of them can hold your page hostage while it dials. They accrete over the years, and almost every site is carrying more than it needs.
The fixes that move the needle — and the ones that don’t
The honest version of performance work: a handful of fixes deliver nearly all of the gain.
- Sort the images. Resize, compress, modern formats, every image. Biggest win, least glamour.
- Fix the foundation. Decent hosting with server-side caching and a CDN in front. This is what makes everything else possible.
- Cull the plugins. Fewer, better, and actually delete the deactivated ones.
- Defer or drop third-party scripts — anything that isn’t earning its keep, especially anything loading before your content.
- Lazy-load below-the-fold images, so the browser fetches them only when needed.
And what’s usually not worth your time: chasing a perfect 100/100 PageSpeed score for the trophy (the gains past “green” are mostly academic), or — my favourite — installing a “speed optimisation” plugin to fix the slowness caused by having too many plugins. You’ve now got one more plugin. Performance is an engineering outcome, not a product you can bolt on; the tools only help when someone understands what they’re tuning.
Check your own site right now — two minutes, two tools
- Google PageSpeed Insights (pagespeed.web.dev) — paste your address and look at the mobile result, not the flattering desktop one. Pay attention to Largest Contentful Paint (LCP) — how long until the main content is visible. It’s the weakest vital across the entire web (only 62% of mobile sites pass it, per the 2025 Web Almanac) and it’s usually the one dragging small-business sites under.
- Your own phone, on mobile data. Not the office wi-fi — real mobile data, like a real customer. Open your homepage and count the seconds honestly. That number is your customer’s actual first impression.
If either result makes you wince, that wince is currently being felt by every impatient visitor you’re paying to attract — and unlike most business problems, this one has a known, finite fix list.
Where we come in
Performance is baked into how we build at Bitstream Media, because we’re engineers, not plugin-installers — a fast site isn’t an upgrade we sell, it’s the baseline we start from. If your site feels sluggish and you’d like to know why rather than guess, we’ll run a free speed diagnosis: plain English, the three things actually dragging it down, and what we’d do about each. No 40-page PDF of red warnings. Just the answer.
Figures quoted as published by Google/SOASTA (2017), Google + Deloitte (2020), the HTTP Archive Web Almanac (2025) and Statcounter (2026), with years stated and sources linked inline.