Why your website is slow, and what actually fixes it

Nearly everyone I speak to about a slow website has already been told the reason. Usually it is "you need better hosting", occasionally it is "the code is bloated". Both are sometimes true. Neither is where I would look first.

I spend my working week in enterprise infrastructure, moving data between systems where slowness is measured and noticed. That perspective is unglamorous but useful here, because it means I have watched what actually causes delay rather than what people assume causes it.

Here is the honest order.

1. Images. It is almost always images.

If your site feels slow, open it on your phone on mobile data and watch what appears last. Nine times out of ten it is a photo.

The usual cause is straightforward: someone uploaded a picture straight off a camera or phone, 4000 pixels wide and several megabytes, into a slot that displays it 600 pixels wide. The browser downloads the whole thing and then shrinks it. Your visitor pays for every one of those unnecessary pixels in load time.

The fix is not clever. Resize images to roughly the size they are displayed, export them in a modern format, and let the platform serve smaller versions to smaller screens. On a typical small business site this alone can halve load time, and it costs nothing.

2. Third-party scripts you forgot about

Every chat widget, booking embed, review carousel, analytics tag, heatmap tool and pixel is a request to somebody else's server. Your page cannot finish until they have all responded, and you have no control over how fast they do.

I have seen sites where the actual content weighed less than a tenth of the page, and everything else was tools nobody had looked at in two years. If you are not using it, remove it. If you are, ask whether it needs to load immediately or whether it can wait until someone scrolls.

3. Fonts

Custom fonts are worth having. Four weights of three different families is not. Each one is a separate download that blocks text from rendering, which produces that jarring moment where a page appears and then all the type shifts.

Two families and the weights you genuinely use is almost always enough.

4. Hosting, eventually

Hosting matters, but it is further down this list than people expect. Moving from slow hosting to fast hosting might save a few hundred milliseconds. Fixing the images might save several seconds.

Where hosting does matter is consistency and distance. If your server is far from your customers, every request pays that travel time. A content delivery network solves this by keeping copies closer to people, and most decent platforms include one.

5. Doing too much before showing anything

Some sites wait until everything is ready before displaying anything, so the visitor stares at white space while work happens invisibly. Others show content immediately and fill in the rest as it arrives. The second feels dramatically faster even when the total time is identical.

Perceived speed is real speed as far as your visitor is concerned. They are not timing you. They are deciding whether to wait.

How to check without guessing

Run your site through Google PageSpeed Insights and read the opportunities section, not the score. The score is a number to feel bad about; the opportunities list tells you what to fix and roughly what each is costing you.

Then do the more honest test: load your site on your own phone, off wifi, and count. If you are still waiting at three seconds, so is everybody else, and most of them have already gone.

Why it matters beyond impatience

Speed affects two things. Whether people stay, and how search engines rank you. Google has been explicit that page experience is a ranking factor, and slow pages lose visitors before they ever see what you offer. A beautiful site that takes six seconds to appear is, in practice, a site nobody sees.

The good news is that the biggest wins are usually the least technical ones. Resize your images. Delete the widgets you stopped using. You can do both this afternoon.