Skip to main content

Blog · WordPress

WordPress speed in 2026: the changes that paid off

By the Hosting & Domains team Published 27 July 2026 8 min read

"My WordPress site is slow" opens more support conversations here than any other sentence, and sit with enough of them and a pattern surfaces. A handful of changes carry almost all the weight. They tend to be structural, and not one of them is interesting to talk about, while enormous amounts of owner time drain away into tuning that moves nothing at all. What follows is that pattern, lifted from the tickets and ranked by what each change gave back.

A definition first. Fast in 2026 means Google's Core Web Vitals, and mainly it means LCP under 2.5 seconds on a mid-range phone. Run the test on your own desktop and you have collected trivia. The traffic is on phones, over mobile networks.

The four fixes that pulled real weight

1. Page caching at server level. Nothing else is in the same league. A page served from cache skips PHP and MySQL entirely and leaves the machine within a millisecond or two. If you are on a LiteSpeed host, install the free LiteSpeed Cache plugin and turn page caching on. That single setting regularly outperforms everything else in this article combined. Our setup guide takes about ten minutes.

2. Bringing images to heel. Heavy images cause more failed LCP scores than anything else crossing our desk. Convert them to WebP, export each one at the size it is displayed rather than larger, and leave everything below the fold to lazy-load, which WordPress handles on its own now. Our image optimisation guide covers the workflow end to end.

3. Judge plugins by weight, not by how many you have. Twenty small utilities cost you less than one page builder dragging 400 assets into every page load. Query Monitor is free, and an afternoon with it will name the culprits. Expect page builders, related-posts engines, and anything that phones home on each request.

4. Which PHP version you run. Each major release since 8.0 has delivered a genuine speed gain, so a site still sitting on 8.1 hands back performance for no reason. Upgrading is a dropdown in the control panel plus a five-minute compatibility check.

Tuning that swallows a weekend and gives nothing back

Hand-minifying CSS and JavaScript. Themes now ship minified already, and stacking a second minifier on top breaks more sites than it speeds up. On a good day the gain rounds down to zero.

Buying a CDN when your audience sits in one country. If every customer is in the same place and the host caches as it should, the CDN mainly contributes an extra network hop. It begins to earn its fee the moment analytics show genuine international traffic, and not one day before.

Two cache plugins running side by side. The second one does not double the caching. It argues with the first. Keep the plugin built for your server, LiteSpeed Cache where the server runs LiteSpeed, and delete the rest.

Buffing up desktop Lighthouse scores. A 100 on a gaming laptop coexists happily with a 55 on somebody's phone. Test on mobile. Test throttled. That is the number Google marks, and the page your readers are handed.

When the platform is the bottleneck

A share of tickets point at the hosting instead of the plugin stack. Look for a TTFB over roughly 600ms on a page that is already cached, decent scores that collapse the moment a little concurrency arrives, and slowdowns in the middle of the afternoon with no explanation, which almost always mean a noisy neighbour on an oversold box. Nothing you install fixes that.

What fixes that is the layer beneath you. NVMe storage returns database queries in microseconds where SATA needed milliseconds, and LiteSpeed keeps its footing under concurrent load in a way stock Apache never manages. That is the entire argument for our WordPress hosting. We look after the platform, so your own list comes down to the four fixes above.

Hosted somewhere else and suspicious about it? Time the TTFB on a cached page twice, once during a quiet hour and once at peak. A wide gap between the two means too many accounts squabbling over too little server, and no image compressor ever outruns that. Moving to us costs nothing, so the experiment only costs you an afternoon.

Quick answers

Which single change gives WordPress the biggest lift?

Page caching at server level, without exception. Where the server runs LiteSpeed, that means the LiteSpeed Cache plugin with page caching enabled. A cached page never touches PHP or the database at all, and that one saving is larger than every asset-level tweak added together.

Does a WordPress site need a CDN?

Only when your readers genuinely sit in several countries. Keep an audience inside one country on a host that caches as it should and a CDN adds latency and moving parts without producing a number you can measure. Check the geography report in your analytics before you pay for one.

How can I work out whether the hosting itself is dragging WordPress down?

Put a timer on the TTFB of a cached page. Should it sit above roughly 600ms, or fly at 7am and crawl by 4pm, the drag is contention on the platform and not anything living on your site. No plugin repairs that pattern.

Up next

More from the blog

The hosting these notes are written on

Renewals that stay flat, limits printed before you buy, migration at no charge and a support desk that writes back, all wrapped into one plan.

Browse Hosting Plans