Skip to main content
.com domains from $2.99 — free WHOIS privacy on every name

Blog · WordPress

WordPress speed in 2026: the fixes that actually delivered

By the HostingFast team Published 27 July 2026 8 min read

"My WordPress site is slow" opens more support conversations than almost anything else, and after enough of them a pattern emerges. A handful of changes do nearly all the work, most of them structural and none of them glamorous, while enormous amounts of owner energy vanish into tuning that moves nothing. Below is that pattern, drawn straight from the tickets and ranked by what each change actually returned.

First, a definition. Fast in 2026 means Google's Core Web Vitals, above all LCP under 2.5 seconds on a mid-range phone. A lab run on your desktop is trivia. Phones on mobile networks are where your traffic really lives.

The four fixes that pulled real weight

1. Server-level page caching. Nothing else is in the same league. A cached page skips PHP and MySQL entirely and is out of the server in a millisecond or two. On a LiteSpeed host, install the free LiteSpeed Cache plugin and turn page caching on. That single switch regularly outperforms every other tip in this article combined. Our setup guide takes roughly ten minutes.

2. Getting images under control. Overweight images are the most frequent cause of failed LCP we come across. Convert to WebP, export each image at the size it actually renders, and let anything below the fold lazy-load, which WordPress now does on its own. The image optimisation guide covers the full workflow.

3. Auditing plugins by weight, not count. Twenty lean utilities cost less than one page builder dragging 400 assets onto every load. Query Monitor is free and will name the culprits inside an afternoon. The usual suspects: page builders, related-posts engines, and anything phoning home on every request.

4. The PHP version. Each major release since 8.0 has posted a genuine speed gain, so a site parked on 8.1 is giving performance away for nothing. Upgrading is a dropdown in the control panel plus a five-minute compatibility check.

The tuning that burns weekends and returns nothing

Hand-minifying CSS and JavaScript. Modern themes ship minified already, and bolting a second minifier on top breaks more sites than it speeds up. On a good day the gain is a rounding error.

A CDN for a one-country audience. When every customer lives in the same place and the host caches properly, a CDN mostly adds a network hop for nothing. It earns its fee once analytics show real international traffic, and not a day sooner.

Running two cache plugins. They do not cache twice, they fight. Keep the one built for your server, LiteSpeed Cache on a LiteSpeed box, and remove the rest.

Polishing desktop Lighthouse scores. A 100 on a gaming laptop coexists comfortably with a 55 on a phone. Always test mobile, always throttled. That is the figure Google grades and the page your visitors actually receive.

When the platform is the bottleneck

Some tickets point back at the hosting industry rather than the plugin stack. The signs: TTFB above roughly 600ms on a page that is already cached, healthy scores that collapse under light concurrency, and unexplained mid-afternoon slowdowns, which almost always mean a noisy neighbour on an oversold box. No plugin patches any of that.

The fix there is the layer underneath. NVMe storage answers database queries in microseconds where SATA needed milliseconds, and LiteSpeed keeps its pace under concurrent load in a way stock Apache never manages. That is the entire case for our WordPress hosting: we keep the platform quick, leaving only the four fixes above on your list.

Hosted elsewhere and suspicious? Time TTFB on a cached page once at a quiet hour and once at peak. A wide spread means too many accounts fighting over too little server, and no image compressor outruns that. Moving to us costs nothing, so the experiment is cheap to run.

Quick answers

What one change speeds WordPress up the most?

Server-level page caching, every time. On a LiteSpeed host that is the LiteSpeed Cache plugin with page caching enabled. A cached page never touches PHP or the database, and that saving dwarfs every asset-level tweak put together.

Does a WordPress site need a CDN?

Only if your readers are genuinely spread across countries. With a single-country audience on a properly cached host, a CDN tends to add latency and moving parts for nothing you can measure. Check the geography report in your analytics before paying for one.

How can I tell whether the hosting is what's slowing WordPress?

Time TTFB on a cached page. If it sits above roughly 600ms, or flies at 7am and crawls at 4pm, the drag is contention on the platform rather than anything on your site. No plugin fixes that pattern.

Up next

More from the blog

The platform these posts come from

Flat renewals, limits stated up front, free migration and support that actually writes back — all of it bundled into a plan.

Browse Hosting Plans