Slow WordPress site: when to fix it — and when to rebuild

Start here

The 20-minute triage

Before you spend a penny — on a plugin, a retainer or a rebuild quote — run five checks. They take about 20 minutes and they tell you which kind of slow you have.

1. Run a speed test. Put your address into our free website speed test and look at the mobile result, because that is how most of your visitors arrive. Note the score down.
2. Read the TTFB (time to first byte). This is how long your server takes to start responding, before your design even matters. Google’s own guidance on web.dev calls 0.8 seconds or less good and anything over 1.8 seconds poor. A high TTFB points at your hosting or a bloated database — no image tweak will rescue it.
3. Count your active plugins. Log in to WordPress and count them honestly. Every one adds code, and struggling small-business sites routinely carry 30 or more, half of them forgotten.
4. Check your hosting tier. If you are on the cheapest shared plan a host offers, your site shares a server with hundreds of strangers. That is often the whole story.
5. Weigh your images. Photos uploaded straight from a phone can be 4–8 MB each. A handful of those on the homepage will sink any theme.

Now read the results together. Bad score but healthy TTFB and huge images? That is a cheap fix — start with the next section. Poor TTFB on decent hosting with a modest plugin list? The problem is structural, and the later sections matter more.

The pattern to watch

The WordPress tax: paying forever to keep a slow thing slow

Here is the pattern we see again and again when a business brings us a tired WordPress site. There is a monthly maintenance fee. There are annual renewals for a premium theme, a page builder, a security plugin, a backup plugin. Every so often something breaks after an update and there is an invoice for putting it right. And after all of that… the site is still slow.

That happens because the weight is structural. A heavyweight theme, a page builder layered on top, a stack of plugins and a database round-trip for every visit add up to a site that no caching plugin can fully rescue — especially on shared hosting. You are not paying to make the site fast; you are paying to stop the complexity falling over.

At that point the question quietly changes. It stops being “how do I speed this up?” and becomes “why am I maintaining complexity I never use?” If your site is really ten pages that change twice a year, a great deal of what you are paying to patch, update and monitor exists only to support an editing system you rarely open.

If the slowness arrived suddenly rather than gradually — strange pages, spam links, a warning in Google — that is a different problem entirely: start with our website hacked checklist. And if you cannot even get into your own site to try the fixes above, see what to do when your web designer disappears or when access is being withheld.

First-party proof

We faced this exact decision with our own website

This is not theory to us. Our own site ran on WordPress for years. We did the optimisation properly — caching, image work, plugin pruning, decent hosting — and it helped, but only so far. The weight was structural, exactly as described above.

So in June 2026 we rebuilt it as a hand-built static site: no page builder, no plugin stack, no database between the visitor and the page. In our own Lighthouse and PageSpeed measurements, our mobile performance score went from roughly 65 to the high 80s. Scores vary a little run to run and every site is different, so we state that only as what happened to ours — but the direction of travel was unmistakable, and nothing has needed patching since. And it is no longer just our site: we have since done the same swap for a client and measured it the day before switchover — time to first byte fell from 1,320ms to 97ms and page requests from 111 to 15. Every number is in what a website rebuild actually changes.

We wrote the whole thing up honestly — what we kept, what broke along the way and what it did not fix — in how we rebuilt our own website. The process we used, including keeping Google rankings intact through the move, is the same one we now offer clients: see our website rebuild service for how an SEO-safe migration actually works.

Two doors

Where to go from here

You should now know which kind of slow you have. There are two honest ways forward, and only one of them involves us.

Door one: fix it yourself. Work through the triage and the cheap fixes above — images, plugins, caching, PHP, database, hosting tier — and re-test with the free speed test after each change so you can see what actually moved the needle. Our website checker will flag anything else amiss while you are at it, and the rest of our free tools are there whenever you need them. No sign-up, no catch.

Door two: get a rebuild quoted. If your site fits the rebuild profile — slow for structural reasons, rarely edited, costing you money to stand still — read how an SEO-safe rebuild works, then ask us for a quote. Every job is priced individually against what your site actually needs; there are no set tiers and no obligation. If a rebuild is the wrong answer for you, we will say so and point you back at door one.

And if what you really need is ongoing help with the site rather than a one-off decision, our broader web design & hosting service covers the lot — site, hosting and email under one roof.

// RELATED

• Website rebuilds without losing your rankings — how an SEO-safe migration works, step by step
• How we rebuilt our own website — the full warts-and-all write-up behind our before-and-after numbers
• Website hacked? A calm first-hour checklist — if the slowness arrived suddenly with strange pages or warnings
• Your web designer has disappeared — how to get your website back, step by step
• Is your website being held hostage? — your escalation path when access is withheld
• Free website speed test — measure your site before and after every fix