Why is my website slow? A plain-English guide for business owners

We’ve covered what a slow site costs you: visitors who leave before the page shows up, and rankings lost to faster competitors. This post is the other half. Your site is slow, and you want to know why, without needing a developer to translate.

You can diagnose most of it yourself in twenty minutes. Here’s how.

First, measure it properly

Don’t judge speed from your own office computer. Your browser has the site cached, your connection is good, and you’ll conclude everything’s fine while your customers wait.

Do two things instead:

1. Open your site on your phone, off wifi, ideally somewhere with mediocre signal. Count the seconds until you can use the page. Past three and you have a problem worth fixing.
2. Run it through PageSpeed Insights (pagespeed.web.dev). It’s Google’s own free tool, and it scores your site the way Google’s rankings see it. Ignore most of the report for now. Look at the score for mobile, not desktop, and the list titled “Diagnostics”.

The mobile score is the one that matters, because that’s where most of your visitors are, and it’s always the worse of the two.

The usual suspects

Nearly every slow small-business site has some mix of the following. For each one: how to spot it, and what fixing it involves.

Huge images. The most common cause by a mile. A photo straight off a phone is 3 to 5 megabytes. It only needs to be a tenth of that on a web page, often less. Spot it: PageSpeed will say “properly size images” or “serve images in next-gen formats”, or just scroll your site on mobile data and watch photos load in stripes. Fix: resize and compress the images, or have your developer set the site up to do it automatically. This is usually the cheapest fix with the biggest result.

Too many plugins and scripts. Chat widgets, popups, social feeds, tracking pixels, that thing someone installed in 2022. Each one is code the browser has to fetch and run before your page settles. Spot it: PageSpeed says “reduce unused JavaScript” or “reduce third-party code”. Fix: remove what you don’t use. Be ruthless. If nobody can say what a plugin is for, it’s for slowing your site down.

A heavy theme or page builder. Off-the-shelf themes ship every feature any buyer might want, and your visitors download all of it whether you use it or not. Page builders layered on top make it worse. Spot it: the site is slow even on simple pages with no images. Fix: this one’s structural. You can trim around the edges, but a heavy theme stays heavy. It’s one of the reasons we don’t use them.

Cheap or overloaded hosting. On £3-a-month shared hosting, your site shares a server with hundreds of others, and it shows. Spot it: PageSpeed says “reduce initial server response time”. The page hangs blank before anything at all appears. Fix: move to better hosting. £10 to £30 a month buys a real difference for a WordPress site.

The page is built from scratch for every visitor. WordPress and platforms like it assemble each page from a database on demand. With no caching set up, every visitor waits for that assembly. Spot it: same symptom as bad hosting, a long blank pause. Fix: a caching plugin helps a lot and takes an hour to set up. A site built as static files, the way we build, removes the problem entirely, because the page was assembled before the visitor ever arrived.

Fonts and videos doing too much. Six font weights loaded from Google’s servers block your text from appearing. An autoplaying background video is a huge download nobody asked for. Spot it: text flashes invisible then appears late, or the homepage hero stutters. Fix: fewer fonts, hosted with the site. Replace the video with a good photo unless it’s genuinely selling something.

Quick wins vs rebuild territory

Compressing images, deleting dead plugins, adding caching, and upgrading hosting are all cheap and quick, and worth doing whatever else is true. Done together they often halve a load time.

But if the diagnosis is the theme itself, or a page builder, or a stack of plugins the site depends on, you’re tuning something that’s slow by design. There’s a point where another round of optimisation costs more than building the site properly, and a rebuilt site starts fast instead of being coaxed toward it.

If you’ve run the test and the report reads like a foreign language, send us the link. We’ll tell you in plain English what’s slowing it down, which fixes are cheap, and whether it’s worth rebuilding. No charge for the diagnosis, and no hard feelings if you take the fix list elsewhere.