A slow WordPress site loses customers before they've even seen what you do. The good news: most speed problems come from a short list of fixable causes, and working through them in the right order makes a dramatic difference without rebuilding anything.
According to HTTP Archive data through 2025, only 44% of WordPress sites pass all three Core Web Vitals on mobile, compared to 65% for Shopify. That's not a WordPress flaw. It's what happens when the people running the sites don't know which levers to pull. Pull the right ones and WordPress is as fast as anything else. Our recent Lockerfella build hit a clean 100/100/100/100 mobile PageSpeed score with the techniques in this guide; the case study shows the metrics on a real site.
Why Speed Matters
Google's research documents case study after case study of sites that sped up and watched conversions climb. Rakuten 24 improved their Core Web Vitals and saw revenue per visitor jump 53%. Vodafone improved LCP by 31% and sales rose 8%. These aren't cherry-picked outliers; they're what happens when a slow site becomes a fast one.
"As an example, the BBC found they lost an additional 10% of users for every additional second their site took to load."
Google, Why Speed Matters (web.dev)
That BBC number is the one I keep coming back to. A site that loads in 4 seconds still "works" in the sense that it renders, but if you're losing 30% of visitors before they see your homepage, "works" is doing a lot of hidden labour in that sentence.
1. Quality Managed Hosting
Hosting sets the ceiling for every other optimisation. You can minify every byte of CSS and still be limited if your server takes 900ms to return the first byte of HTML. HTTP Archive data shows only 32% of WordPress sites have good TTFB, and that's almost entirely a hosting story.
What to look for: NVMe SSD storage, PHP 8.2 or higher (older PHP runs WordPress 20 to 30% slower), server-level caching included as standard, a UK or European data centre for UK audiences, and dedicated resources rather than thousands of accounts on one box. 365i's WordPress hosting ticks all of those by default. The same hosting choice affects security, which we cover in our WordPress security checklist for small businesses.
2. Proper Caching
Caching stores a ready-to-serve copy of each page so WordPress doesn't have to rebuild it from scratch on every visit. Three layers work together: page caching stores rendered HTML (the biggest win), object caching via Redis stores database query results, and browser caching keeps static files locally on visitor machines.
For page caching, WP Rocket is the easiest paid option and LiteSpeed Cache is the best free option if you're on a LiteSpeed server. If your host doesn't support Redis for object caching, that's a signal the hosting isn't quite right for performance work. Sites built on structured content via WordPress 7's Block Bindings cache more predictably too, because the markup stays consistent across pages that share a data source.
3. Optimise Images and Serve WebP
Images are usually the heaviest thing on a WordPress page. A 2MB hero image becomes 180KB in WebP at sensible quality. Multiply that across ten images and you've cut over 15MB from the page. On mobile, that's the difference between instant and broken.
- Convert to WebP. Imagify, ShortPixel, or EWWW Image Optimizer do it automatically.
- Compress at 80% quality. Indistinguishable from 100% and roughly half the file size.
- Lazy-load below the fold. WordPress has had native lazy loading since 5.5; just make sure no plugin is overriding it.
The detail most sites miss: serve images at the size they're actually displayed. If your theme renders a 400px thumbnail but WordPress sends the 2400px master, you're wasting bandwidth. A decent optimisation plugin handles this through srcset automatically. There's also help on the way: WordPress 7 introduces client-side media processing that pushes image resizing into the browser before upload, taking that work off the server entirely.
4. Minify CSS and JavaScript
Minification strips whitespace and comments from code without changing what it does. Every caching plugin worth installing handles it with a single tick-box. Test carefully after enabling: occasionally a badly-written script breaks when minified, and you want to know within minutes.
5. Eliminate Render-Blocking Resources
Browsers can't render anything until they've loaded the CSS and synchronous JavaScript referenced in the head. Critical CSS is the trick: extract the styles needed for above-the-fold content, inline them, and defer the rest. WP Rocket and FlyingPress generate it automatically. For JavaScript, add defer or async to anything non-essential. Analytics, chat widgets, and third-party embeds can almost always be deferred.
6. Audit and Remove Unused Plugins
The most common performance killer isn't the plugin count, it's a single badly-written plugin loading its assets on every page when it's only used on one. Page builders, heavy contact form plugins, and social sharing plugins are the usual suspects. We've seen sites lose 40% of their page weight just by removing a page builder that was used on a single landing page but loading its runtime everywhere.
List every active plugin, note what it does, delete anything unused, and use Query Monitor to find plugins loading assets where they shouldn't. Replace one-trick plugins with a few lines of theme code where possible.
7. Clean Up Your Database
Post revisions, auto-drafts, trashed comments, expired transients, and orphaned metadata accumulate over time. None of it is harmful, but it makes queries slower and backups larger. WP-Optimize or Advanced Database Cleaner handle this. Back up first (always, before any database operation), then run the cleanup. You'll typically reclaim 10 to 30% of database size.
8. Add a CDN
A CDN serves your static files from edge locations close to each visitor. For a UK-only audience on UK hosting the speed gain is modest, but a CDN also offloads traffic from your origin server, gives you on-the-fly image optimisation, and adds bot protection as a side effect. Cloudflare's free tier covers most small businesses; 365i runs a managed CDN for sites that need more.
9. Measure and Improve Core Web Vitals
Google uses three Core Web Vitals as ranking signals: LCP (loading), INP (responsiveness), and CLS (visual stability). You need to pass all three on mobile and desktop.
"Optimizing for quality of user experience is key to the long-term success of any site on the web."
Google, Web Vitals (web.dev)
The word doing the work in that sentence is "long-term". Algorithms change, channels rise and fall, but whether people enjoy being on your site stays constant. Core Web Vitals are Google's attempt to measure that quantitatively.
Use PageSpeed Insights (pagespeed.web.dev) for the field data Google actually uses for rankings, Chrome DevTools Lighthouse for debugging individual pages, and Google Search Console for a site-wide view of which URLs are failing. Start with your highest-traffic pages: fixing a homepage that gets 10,000 visits a month does more than fixing a blog post nobody reads.
10. Use a Lightweight Theme
Bloated themes are the other major source of slow WordPress sites. If your theme ships with dozens of demos, multiple slider libraries, and a page builder bundled in, it's going to be slow no matter what else you do. GeneratePress, Astra, Kadence, and Blocksy all load less than 20KB of CSS by default. If you're on a heavy multipurpose theme and your Core Web Vitals are poor, switching themes is sometimes the fastest path to green.
Quick Audit Order
If you want to run through this yourself, work in this order:
- PageSpeed Insights test on your homepage and top three pages. Note the scores.
- Update PHP to 8.2 or higher if it isn't already.
- Install a caching plugin and enable page caching.
- Install an image optimiser and convert existing images to WebP.
- Audit plugins. Delete anything unused.
- Re-test. Most sites see measurable improvement at this point.
- Work through any remaining Lighthouse recommendations one at a time.
Done methodically, this gets most WordPress sites from poor to good Core Web Vitals in an afternoon.
Frequently Asked Questions
How fast should a WordPress website load?
Your Largest Contentful Paint should be under 2.5 seconds on mobile to pass Google's Core Web Vitals. A good target for the full page load is under 3 seconds. Anything over 4 seconds starts losing visitors measurably.
What are Core Web Vitals?
Core Web Vitals are Google's three key performance metrics: Largest Contentful Paint (loading speed, target under 2.5s), Interaction to Next Paint (responsiveness, target under 200ms), and Cumulative Layout Shift (visual stability, target under 0.1). Google uses them as a ranking signal for search results.
Which is the best WordPress caching plugin in 2026?
WP Rocket is the easiest to set up and gives excellent results across most hosting environments. LiteSpeed Cache is the best free option but only on LiteSpeed servers. Autoptimize plus Cache Enabler is a solid free combination if you're on shared hosting. The right choice depends on your host.
Is there a maximum number of plugins a WordPress site should have?
No hard limit. A well-built site can run 40 plugins without performance problems; a badly-built site can crawl with 10. What matters is quality, not quantity. Each plugin should do something useful, be kept updated, and be removed the moment it stops earning its place.
Is WebP worth switching to from JPEG and PNG?
Yes. WebP files are typically 25 to 35% smaller than equivalent-quality JPEGs and more than 50% smaller than PNGs. Browser support is universal now. For a typical image-heavy page, switching to WebP can cut total page weight in half with no visible quality loss.
Do I need a CDN for a small UK business website?
If all your customers are in the UK and you're on a UK host, the speed gains are modest. But Cloudflare's free tier also gives you bot protection, basic DDoS mitigation, and free SSL, which are worth having on their own. There's very little reason not to use a CDN on a WordPress site in 2026.
How do I measure my WordPress site's speed?
PageSpeed Insights (pagespeed.web.dev) is the most important tool because it uses the same data Google uses for ranking. Test your top five pages on both mobile and desktop. For debugging, use Chrome DevTools Lighthouse. For ongoing monitoring, Google Search Console's Core Web Vitals report shows you site-wide trends.
Want a Faster WordPress Site Without the Hassle?
Our WordPress Speed Optimisation service takes your site through every item in this guide, tests the results, and delivers measurable Core Web Vitals improvements. We handle the technical work so you can get back to running your business.
See Speed OptimisationPublished: 28 February 2026 · Last reviewed: 14 April 2026 · Written by: Mark McNeece, Founder & Lead Developer, Press Forge
Editorially reviewed by: Mark McNeece on 14 April 2026 · Our editorial standards