Blog · WordPress
WordPress speed in 2026: what actually moved the needle
By the Hosting Seller team Published 27 July 2026 8 min read
"My WordPress site is slow" is among the most frequent conversations at our support desk, and after enough of them the shape is clear. The changes that work are few, dull and mostly structural, while a great deal of owner effort goes into tuning that shifts nothing at all. What follows is the pattern from those tickets, ordered by how much each change actually did.
One thing to set straight first. Fast in 2026 means Google's Core Web Vitals, and chiefly LCP under 2.5 seconds on a mid-range phone. A lab score on your desktop is decoration. Phones on mobile data are where your visitors actually are.
The four changes that did the work
1. Server-level page caching. Nothing else is close. A cached page never touches PHP or MySQL and leaves the server in a millisecond or two. If your host runs 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 runs about ten minutes.
2. Image discipline. Oversized images are the most common cause of poor LCP we see. Serve WebP, size each image to the box it displays in, and lazy-load anything below the fold, which WordPress now handles by itself. The image optimisation guide walks the workflow.
3. Plugin triage. The number of plugins is not the problem; their weight is. A single page builder loading 400 assets outweighs twenty tidy little utilities. Query Monitor is free and will name the offenders in an afternoon. The regulars are page builders, related-posts engines, and anything that calls home on every request.
4. PHP version. Every major release since 8.0 has been meaningfully quicker, so a site still sitting on 8.1 is leaving real speed unclaimed. Moving up is a dropdown in the control panel plus a five-minute compatibility check.
The advice that eats weekends for nothing
Minifying CSS and JavaScript by hand. Modern themes already ship minified, and double-minification plugins break more sites than they accelerate. Marginal on a good day.
CDNs for a single-country audience. If your customers are all in one place and your host caches properly, a CDN often adds a hop and returns nothing. Buy one when analytics show a genuinely international readership, and not a day earlier.
Stacking cache plugins. Two caching plugins do not cache twice, they argue. Keep the one that matches your server, which is LiteSpeed Cache on LiteSpeed, and delete the others.
Chasing desktop Lighthouse scores. A 100 on your gaming laptop sits happily beside a 55 on a phone. Test on mobile, throttled, every time. That is the number Google uses and the experience your visitors get.
When the hosting really is the problem
Sometimes the tickets point at our industry rather than at the plugin list. The tells: TTFB above roughly 600ms on a page that is already cached, decent scores that fall apart under modest concurrency, and unexplained afternoon sluggishness, which usually means a loud neighbour on an oversold machine. No plugin repairs any of that.
The answer there is structural, and it is the stack underneath. NVMe storage returns database queries in microseconds where SATA took milliseconds, and LiteSpeed's architecture holds its shape under concurrency in a way stock Apache does not. That is the whole argument for our WordPress hosting: the platform layer is handled, leaving you the four fixes above.
If you are hosted elsewhere and suspect the platform, run a TTFB test on a cached page at a quiet hour and again at a busy one. A wide gap means too many sites on too small a server, and no amount of image compression will out-run that. Migration here costs nothing, which makes the experiment cheap.
Short answers
What is the single biggest WordPress speed improvement?
Server-level page caching. On a LiteSpeed host that means the LiteSpeed Cache plugin with page caching turned on. A cached page bypasses PHP and the database completely, which outweighs every asset-level tweak combined.
Do I need a CDN for my WordPress site?
Only when your audience is genuinely spread across countries. For a single-country readership on a well-cached host, a CDN usually adds latency and moving parts for no visible return. Read the geography report in your analytics before you pay for one.
How do I know if my hosting is what's slowing WordPress down?
Measure TTFB on a cached page. Consistently above roughly 600ms, or quick at 7am and sluggish at 4pm, points at contention on the platform rather than anything on your site. Plugins cannot fix that pattern.
Also on the blog
Web hosting costs in 2026: the whole bill
The tag on the shelf is advertising. The renewal is the product. Here is the three-year arithmetic, worked out in the open.
“Unlimited” web hosting: where the limits really sit
Disks have sizes. 'Unlimited' translates to 'limited by units you haven't met yet': inodes, CPU seconds and a fair-use paragraph.
Free domain with hosting: four things to check before you claim one
The free year is genuine. Year two is where the questions live: renewal rate, whose name is on the record, and what leaving costs.
The product behind the posts
Flat renewals, limits printed on the tin, free migration and a help desk that replies — everything above, in plan form.
Browse Hosting Plans