Blog · WordPress

What actually makes WordPress faster in 2026

By the HostingAlly team Published 27 July 2026 8 min read

"My WordPress site is slow" ranks among the conversations we have most often at the support desk. Sit through enough of them and a pattern surfaces. The fixes that work are few in number, dull, and mostly structural, while a huge amount of owner energy pours into optimizations that shift nothing at all. What follows is that pattern, written up: the things that genuinely changed people's Core Web Vitals, ranked from biggest impact downwards.

A framing note before we start. In 2026, 'fast' means Google's Core Web Vitals, and chiefly it means LCP under 2.5 seconds on a mid-range phone. Lab scores taken on your desktop are vanity. Your visitors are sitting on phones, on mobile data.

Four changes that genuinely shift a site's numbers

1. Server-level page caching. Nothing else is in the same league. Serve a cached page and you bypass PHP and MySQL completely, leaving the server inside a millisecond or two. Running on a host with LiteSpeed? Install the free LiteSpeed Cache plugin and switch page caching on. That one toggle routinely beats everything else in this article put together. Our walkthrough takes ten minutes.

2. Image discipline. Oversized images cause more slow LCP than anything else crossing our desk. Serve WebP. Size each file to the box it will display in. Lazy-load whatever sits below the fold, which WordPress now handles on its own. Our image optimization guide walks through the whole workflow.

3. Plugin triage. Count is not the issue; weight is. A single page builder dragging 400 assets behind it outweighs twenty well-built utilities. Query Monitor is free, and it will name the slow ones for you inside an afternoon. Usual suspects: page builders, 'related posts' engines, and anything phoning home on every request.

4. PHP version. Every major PHP release since 8.0 has landed measurably quicker than the last, so a site parked on 8.1 is leaving real speed on the table. The upgrade is a dropdown in the control panel plus a five-minute compatibility check.

The popular advice that mostly wastes weekends

Hand-minifying CSS and JavaScript: current themes already ship minified, and double-minification plugins break more sites than they ever accelerate. Marginal gains at the very best.

CDNs aimed at a single-region audience: where your customers all sit in one country and the host's platform caches properly, a CDN tends to insert an extra hop and give nothing back. Wait until analytics show a genuinely international audience. Then add one.

Stacking cache plugins forever: run two of them and you don't get double caching, you get a fight. Choose the one built for your server, LiteSpeed Cache on LiteSpeed servers, then delete the others.

Chasing desktop Lighthouse scores: a 100 on your gaming laptop sits quite happily alongside a 55 on somebody's phone. Test on mobile, throttled, every single time. That is the number Google reads, and the experience your visitors actually live with.

When it's genuinely the hosting

Now and then the ticket pattern points back at us, meaning the industry rather than anyone's plugin stack. Tells that hosting is the bottleneck: TTFB above roughly 600ms on a page that is already cached, decent scores that fall apart under modest concurrency, and unexplained afternoon slowdowns, which usually mean a noisy neighbour on an oversold server. No plugin touches any of that.

Structurally, the answer lives in the stack underneath. NVMe storage returns database queries in microseconds where SATA took milliseconds, and LiteSpeed's architecture stays upright under concurrency in a way stock Apache never does. That is the entire pitch behind our WordPress hosting: platform layer dealt with, leaving you only the four fixes listed above.

Hosted somewhere else and suspicious of the platform? Run a TTFB test against a cached page during a quiet hour, then repeat it during a busy one. Where those two numbers pull apart badly, you are sharing an undersized server with too many sites, and no quantity of image compression will out-optimize that. Migration is free here, so the experiment costs you nothing.

Quick answers

Which single change speeds WordPress up the most?

Page caching at server level. On LiteSpeed hosts that means the LiteSpeed Cache plugin, with page caching switched on. A cached page bypasses PHP and the database altogether, which matters more than every asset-level tweak put together.

Do I need a CDN for my WordPress site?

Only where your audience is genuinely international. If everyone lands from one country and the host caches well, a CDN tends to add latency and complexity while returning nothing visible. Open the geography report in your analytics before you pay for one.

Is my hosting the thing dragging WordPress down, and how would I tell?

Measure TTFB against a cached page. If it sits above roughly 600ms every time, or runs quick at 7am and drags at 4pm, that points at platform contention rather than anything on your site. It is a hosting problem, and no plugin will touch it.