Why your WordPress site is slow — and the five fixes that matter
A slow site is not a mystery. When a client tells us their WordPress site "feels heavy," we can almost always name the cause before we open the code — it is nearly always the same short list. Here is that list, in the order we check it, and what each fix is actually worth.
First, measure — do not guess
Before touching anything, we pull a real number: Largest Contentful Paint (LCP) on a mid-range phone over a normal connection. Not the developer's laptop on office wifi. The phone in a customer's hand.
Most of the "slow" WordPress sites we inherit sit at 4–6 seconds LCP on mobile. Google wants under 2.5. That gap is where the lost customers are, and it is very fixable.
1. Images nobody optimised
This is the biggest one, every time. A hero image exported straight from a designer's file at 4000px wide, 3MB, served at full size to a phone that will show it at 400px.
The fix: correctly sized, modern-format (WebP/AVIF) images with real lazy-loading below the fold. On a media-heavy site this alone can take 2 seconds off LCP. It is boring and it works.
2. Plugin sprawl
The average site we audit runs 30+ plugins. Each one loads its own CSS and JavaScript on every page — including the ones that never use it. A contact-form script loading on your blog. A slider library on pages with no slider.
We do not just delete plugins (that breaks things). We audit what each one loads, dequeue assets on pages that do not need them, and replace three overlapping plugins with one that does the job. Fewer requests, less code, faster paint.
3. No caching, or the wrong caching
WordPress rebuilds each page from PHP and the database on every request unless you tell it not to. Page caching serves a pre-built copy instead — the difference between cooking a meal to order and handing over one that is ready.
Add a proper page cache plus a CDN so a visitor in Sydney is not waiting on a server in London. Time to first byte drops from ~800ms to under 200ms. Nearly free, huge impact.
4. A bloated theme
Many premium themes ship every feature you might ever use, loaded on every page whether you use it or not — giant CSS files, page-builder overhead, web fonts you never chose. Sometimes the fastest fix is the hardest sell: a lean theme that loads only what the page needs.
5. Render-blocking everything
The browser stops drawing the page while it downloads CSS and JavaScript in the <head>. Defer what is not needed for the first paint, inline the critical bits, and load fonts so text shows immediately instead of hanging on a blank screen. This is the difference between a page that appears fast and one that technically loads fast but feels frozen.
What the numbers turn into
Speed is not vanity. On one recent WooCommerce rebuild, cutting LCP from 4.2s to 1.1s moved mobile conversion up 41% — same traffic, same products, same ads. The store simply stopped losing the people who were already trying to buy.
That is the point worth remembering: a slow site is not a technical footnote. It is a leak in the bucket, and it is almost always one of these five holes.
The order that matters
If you only do one thing, fix the images. If you do three, add caching and kill plugin sprawl. Those three cover most of the gap on most sites — and none of them require rebuilding anything. You are not making the site do less; you are stopping it from doing work no one asked for.
Need help with something like this?
Tell us what you are building. We reply within 24 hours — no sales team, no follow-up sequence.