Guide
Slow WordPress site — what is actually causing it
A slow WordPress site is rarely one plugin. It is usually the theme, the page builder, uncached database work and a front end that cannot get out of its own way.
The homepage is slow. The rest is worse.
You have tried a cache plugin. You have tried a CDN. Pages still take seconds to become usable, especially on mobile. Paid traffic lands on a page that is still loading. Editors wait on the admin. The site feels older than it is.
What is usually behind it
The page is assembled on every request
Page builders, heavy themes and unbounded queries mean WordPress is doing too much work before a visitor sees anything. Caching hides it until someone logs in or a form is submitted.
Images, scripts and third parties pile up
Each plugin adds CSS, JavaScript and tracking. None of them were chosen as a set. The result is a page that is heavy before your content even starts.
The host is not the real problem
Moving to a more expensive host can shave time off a badly built page. It does not fix a front end that has to bootstrap a page builder to render a heading.
What a fix involves
Sometimes the right work is a diagnosis and a short list of fixes on the current stack. Sometimes the platform itself is the constraint, and a migration is cheaper than another year of plugin theatre.
- Measure the live pages that matter — not a lab score on a blank template
- Separate what is theme, what is plugin, and what is hosting
- Fix what is cheap and durable: images, unused scripts, cache, database work
- Be honest when the remaining gap only closes by changing the front end
What it costs to find out
The Headless Assessment includes a performance diagnosis of the current platform and a costed route — stay, fix, or migrate. £1,500, no obligation to build with us.
How we do this work
Modernise the presentation layer and core functionalities without ripping out commerce, CRM, or content systems that still work.
Platform migrationsRelated guides
- Core Web Vitals dropped — diagnosis and fixesA Core Web Vitals drop is a symptom. The cause is usually a release, a plugin, a tag or a template that made the important pages slower for real visitors.
- WordPress to Next.js migrationMove off a slow, plugin-heavy WordPress site without losing the content, rankings and integrations you already paid for.
Common questions
Can you just make this WordPress site faster?
Often, yes, for a first stretch. If the remaining problem is the architecture, we will say so rather than sell another round of plugin work that will not hold.
Is this a Core Web Vitals problem?
Core Web Vitals are how Google describes the same issue visitors already feel. The assessment looks at LCP, interactivity and layout shift on the pages that actually receive traffic — not a generic scan.
Will a new theme fix it?
A cleaner theme can help. If content, plugins and integrations still have to travel through WordPress on every request, you will meet the same ceiling again.
Find out what you are actually dealing with.
The Headless Assessment includes a performance diagnosis of the current platform and a costed route — stay, fix, or migrate. £1,500, no obligation to build with us.
No lock-in. No obligation.