A slow website rarely announces itself. Nobody sends a message to say your homepage took six seconds to load — they just close the tab, and you never hear from them. The inquiry, the booking, the sale: gone before it ever reached your inbox.
And here's the part that's easy to miss when you're testing on your own laptop at home: most of your customers aren't on wifi. They're on mobile data, on a jeepney, in a mall where the signal drops to one bar. A site that feels fine on a fast connection can be painful in the conditions your visitors are actually in.
The good news is that what makes a site slow is usually a short list. Most of it is fixable without a rebuild — you just have to know where to look.
What Actually Slows a Website Down
Oversized images
This is the number one cause, by a wide margin. A photo straight off a phone camera is four to six megabytes. Put a few of those on a page — a product gallery, a team section, a hero banner — and a visitor on mobile data is now downloading 20MB just to see your homepage. Resized and compressed properly, those same images can look identical at a fraction of the weight.
Too many scripts and plugins
Every chat widget, popup, review badge, and tracking pixel adds its own code that has to load before the page settles. It adds up fast. It's common to find a site running three separate analytics tools, two of which nobody has opened in a year, all slowing down every single visit.
Cheap or overloaded hosting
On the lowest hosting tiers, hundreds of sites share one server. When the others are busy, yours waits. If your page takes two seconds just to start responding — before a single image loads — hosting is usually where to look first.
No caching
Without caching, the server rebuilds your entire page from scratch on every visit. With it, visitors get a pre-made copy that loads almost instantly. It's one of the highest-impact changes and it's usually free to switch on.
What Speed Fixes Can't Do
A fast site still can't outrun a bad connection — if your customer is standing in a mall basement with one bar of signal, physics wins. Optimisation buys you margin in bad conditions; it doesn't remove the conditions.
Speed scores aren't the goal either. Tools like PageSpeed and GTmetrix are useful for spotting problems, but a perfect green score on a page with a confusing layout still loses the sale. Chasing 100/100 has real diminishing returns once the basics are handled.
And some fixes cost money. Moving off the cheapest hosting, or adding a CDN so your images load from a server closer to the visitor, are real expenses. Small, but worth being honest about — the bottom hosting tier has a ceiling you can't optimise your way past.
Speed is a feature people only notice when it's missing. Like the padlock in the address bar, the goal is for nobody to ever have to think about it.
What Optimising a Site Actually Comes Down To
Underneath the specifics, speed is two questions: how much work the server does for each visitor, and how much the browser has to download before the page is usable.
On the server side, slow almost always traces back to resources — not enough processing power or memory — or to software doing more work than it needs to on every request. That's why caching helps so much: the server stops rebuilding the whole page from scratch each time. It's also why the cheapest shared hosting has a ceiling. And the application itself is often the real weight — a heavy framework, or a CMS carrying a dozen plugins, makes the server work hard for every single load.
On the browser side, images are the usual offender — but the fix has a limit. Resizing an image to the size it's actually displayed at and compressing it is free and invisible; a 4000-pixel photo in an 800-pixel slot is pure waste. Dropping resolution below what the screen needs isn't optimisation, though — it's just a blurrier site. Past a point you're trading how it looks for a better score.
The standard checklist isn't exotic: right-sized compressed images, caching on, unused scripts removed, a CDN if your visitors are spread out, and hosting that matches your traffic. Most slow sites are missing three or four of them.
The Quick Way to Check Your Own Site
Open your site on mobile data, not your home wifi. Count the seconds until you can actually read something and tap it. Three seconds or under is fine. Past five, you're losing people who will never tell you why.
If your site feels sluggish and you're not sure what's causing it, that's the part I can help with — usually it's a handful of targeted fixes rather than starting over.
Further reading
- Small Things That Make Your Website Easier to Use on a Phone — czerwin.net
- 3 Quiet Habits Behind Every Reliable Website — czerwin.net