Why is my website so slow? The real causes — and what actually fixes them

You click your own website, wait, and there’s that pause. A blank screen, then the logo, then the images sliding in one after another. It feels sluggish, and you have a nagging suspicion your customers feel it too. You’re right to worry, and you’re right that it matters. The good news is that “slow” is rarely a mystery. It almost always comes down to a handful of causes, most of which you can check today without touching a line of code.

I rebuild small-business sites for a living, and slowness is the single most common complaint I hear. So let me walk you through what’s actually going on, how to test your own site honestly in five minutes, and which fixes you can do yourself before spending money on anyone.

What does a slow website actually cost you?

Two things, and both are easy to understand.

First, people leave. When a page takes too long to appear, visitors don’t sit patiently — they hit the back button and try the next result. That’s true whether you sell products, take bookings, or just want someone to pick up the phone. Every extra second of waiting is another moment for someone to give up. If you want to see how much a slow, fiddly experience can cost at the crucial moment, my piece on why customers abandon your checkout covers the point of sale in detail.

Second, Google is watching. Google has said for years that page speed is one of the signals it uses to decide who ranks where. It wants to send people to pages that load quickly and feel stable, because that’s what its users prefer. A slow site can therefore rank lower than a faster competitor selling much the same thing. So speed isn’t vanity — it quietly affects how many people find you in the first place.

I’m deliberately not throwing statistics at you here. You’ll find plenty of confident-sounding percentages online, and a lot of them are made up. The honest version is simpler: slow sites lose visitors, and slow sites can rank worse. That’s enough reason to care.

The five real causes of a slow website

In my experience, almost every slow small-business site is slow for one or more of these five reasons.

1. Huge images straight off a phone or camera

This is the big one, and it’s the one owners cause most often without realising. A modern phone photo can be four, five, six thousand pixels wide and several megabytes in size. Your website might only ever display that image at a few hundred pixels. When you upload the full-size original, every visitor’s browser has to download the enormous file and then shrink it down on the spot. It’s like posting someone a wardrobe when they asked for a jumper.

A page with eight or ten of these oversized images can be many times heavier than it needs to be. This is the most common cause I find, and happily it’s also the easiest to fix yourself.

2. Cheap, overloaded shared hosting

Hosting is the computer that stores your website and hands it out to visitors. On budget “shared” hosting — which is what most small sites start on — your site sits on one machine alongside hundreds or even thousands of other websites, all sharing the same resources. When the machine is busy, everyone on it slows down. There’s nothing wrong with shared hosting in principle, but the very cheapest plans are often overcrowded, and you feel it as a site that’s sluggish for no obvious reason, especially at busy times.

3. Too many plugins and third-party scripts

Plugins are the add-ons that bolt extra features onto your site: a chat widget, a cookie banner, a booking form, an image slider, analytics and tracking tags, a social-media feed. Each one is a little program that has to load. A “third-party script” just means code that runs on your site but is served from someone else’s system — a chat bubble in the corner, for example, is usually loading from the chat company’s servers.

Individually they seem harmless. Stacked up, they’re a real weight, and worse, if one of those outside services is having a slow day, your site waits for it. I regularly find sites carrying half a dozen plugins the owner has completely forgotten about.

4. No caching

Caching (pronounced “cashing”) means storing a ready-made copy of your page so it doesn’t have to be rebuilt from scratch every single time someone visits. Without it, many sites reassemble the whole page from the database on every request — the equivalent of cooking every meal from raw ingredients rather than reheating something you prepared earlier. Good caching is one of the biggest speed wins available, and its absence is a very common reason a site feels slow under any real traffic.

5. An ageing or heavy theme, or a bloated page builder

Your “theme” is the design template your site is built on. A “page builder” is a drag-and-drop tool that lets non-technical people design pages visually. Both are useful, but many of them achieve their flexibility by loading a great deal of code and styling on every page, whether that page uses it or not. An old, abandoned theme, or a page builder piling extra weight onto every screen, can make even a simple page heavy. This one usually needs a professional eye, because it lives under the bonnet.

The 5-minute test you can run right now

Before you spend a penny, do this. It costs nothing and tells you a great deal.

Load your own site on your phone, on mobile data. Turn the wi-fi off first. Your office or home wi-fi is faster than what many customers use out in the real world, so testing on wi-fi flatters your site. Time it honestly from the moment you tap to the moment the page is genuinely usable. Anything over three or four seconds is worth taking seriously.
Run Google PageSpeed Insights. Go to pagespeed.web.dev, type in your web address, and press Analyze. It’s free, it’s from Google, and it takes under a minute.
Read only two things. Ignore the wall of technical detail for now. Look at (a) the top-line score out of 100 — under 50 is poor, 50 to 89 is middling, 90-plus is good — and (b) the list of suggestions, specifically any that mention images.
Watch for these exact phrases. “Properly size images” means you’ve uploaded pictures far bigger than they’re displayed — cause number one above. “Serve images in next-gen formats” means your images could be saved in a more efficient modern file type and shrunk considerably. “Reduce unused JavaScript” or “reduce unused CSS” is the tool politely telling you there’s a lot of plugin and theme code loading that the page doesn’t actually need.

That’s it. In five minutes you’ll know whether your problem is mainly images, mainly bloat, or both. If you’d like a broader once-over of your whole site while you’re at it, I’ve written a companion 10-minute website self-audit you can run through afterwards.

Which fixes can you do yourself — and which need an engineer?

Here’s the honest dividing line.

You can genuinely do these yourself:

Resize and compress images before uploading. Shrink photos to a sensible width (around 1,600 pixels wide is plenty for most full-width images, far less for small ones) and run them through a free compression tool such as Squoosh or TinyPNG before they go anywhere near your site. This alone often makes a page feel dramatically lighter.
Remove plugins and widgets you don’t use. Go through your list and be ruthless. That slider you added in 2021, the second analytics tool, the chat widget nobody answers — if you’re not using it, deactivate and delete it. Fewer moving parts, faster site.

These genuinely need someone who knows what they’re doing:

Setting up proper caching. Done well it’s transformative; done carelessly it can serve stale pages or break your shop. It’s worth getting right.
Moving to better hosting. Choosing the right host and migrating without downtime or lost email is fiddly, and mistakes here are painful.
Code-level and theme work. Trimming a heavy theme, replacing a bloated page builder, or cleaning up the underlying code is skilled work. This is the core of what I do under speed and performance, and it’s not a job for trial and error on a live site.

When speed is a symptom of something deeper

Sometimes you compress the images, clear out the dead plugins, and the site is still slow. That’s actually useful information. It usually means the slowness isn’t a surface problem at all — it’s the visible edge of a site that’s been patched and added to for years until it’s carrying far more weight than it needs to. Layers of old plugins, a theme that’s been half-replaced, code left behind by three different people who worked on it before you. Speed is just the symptom you happen to notice; the real issue is accumulated clutter under the bonnet.

There’s no shame in that. It’s simply what happens to a website that’s been kept alive and useful for a long time. But it does mean there’s a limit to what tidying the surface will achieve.

When to get help — a simple decision rule

Here’s the rule I’d give a friend:

If you’ve properly sorted your images and removed the plugins you don’t use, and your site is still slow, the problem is under the bonnet — and it’s time to have someone look properly.

At that point you’ve done everything a non-technical owner reasonably can, and you’ve done it for free. Anything beyond it is diagnosis and repair work: caching, hosting, and code. That’s the line where DIY stops paying off and a professional starts saving you far more time and lost custom than they cost. If you’re not sure which side of the line you’re on, that’s exactly what a free site check is for — a straight answer on whether it’s a quick tidy-up or something deeper.

Start with the five-minute test today. Whatever you find, you’ll be making decisions from facts instead of that nagging feeling — and that’s already a better position than most site owners ever reach.