Why Your WordPress Site Is Slow (And 7 Fixes That Actually Work)
A slow website isn’t just annoying — it’s costing you customers and rankings. Google uses Core Web Vitals as a ranking factor, and research consistently shows that every second of additional load time reduces conversions. I’ve fixed hundreds of slow WordPress sites over the years, and the culprits are nearly always the same. Here are the seven fixes that actually make a difference.
Why Speed Matters More Than Ever
Google’s Core Web Vitals — Largest Contentful Paint, Cumulative Layout Shift, Interaction to Next Paint — are baked into search rankings. A site that scores poorly will, all else being equal, rank lower than a comparable site that scores well. Beyond rankings: if your site takes more than three seconds to load on mobile, a significant chunk of visitors will leave before they see a thing. That’s traffic you’ve paid for or earned through SEO, gone.
Before you touch anything, run your site through Google PageSpeed Insights (free, at pagespeed.web.dev) and GTmetrix. These will tell you where you stand and what’s causing the slowdown. Then work through this list.
Fix 1: Get Off Cheap Shared Hosting
This is the most common cause of a slow WordPress site, and the one people are least willing to hear. Cheap shared hosting means your site is sharing server resources with hundreds or thousands of other sites. When they’re busy, you’re slow. When they get hacked, you’re at risk.
Quality managed WordPress hosting costs more — typically £15–£40/month from providers like Kinsta, WP Engine, or SiteGround’s GoGeek plan — but the performance difference is dramatic. In my experience, moving from budget shared hosting to decent managed hosting can cut load times by 50% or more before you change a single thing on the site itself. If you’re paying £3/month for hosting and wondering why your site is slow, you’ve found your answer.
Fix 2: Install a Caching Plugin
WordPress builds pages dynamically — every time someone visits, it queries the database and assembles the page from scratch. Caching stores a ready-made version of each page so it can be served instantly without that process.
Recommended tools: WP Rocket (paid, £49/year, worth every penny — it works brilliantly without needing to understand what it’s doing), W3 Total Cache (free, more complex), or LiteSpeed Cache if your host supports it (also free and excellent). If you’re on a managed host like Kinsta or WP Engine, they have built-in caching — don’t add a separate caching plugin on top.
Expected improvement: significant, especially for returning visitors and anyone not already in cache. Pages that took 3+ seconds can often drop to under 1 second.
Fix 3: Optimise and Compress Your Images
Images are almost always the single biggest cause of slow page loads. A homepage hero image that’s been uploaded straight from a camera at 4MB will drag your site down regardless of everything else.
Every image should be compressed before uploading, and served at the right dimensions. You shouldn’t be serving a 2000px-wide image in a 400px column.
Recommended tools: ShortPixel or Imagify (both compress your existing images in bulk and handle new uploads automatically). Enable WebP conversion — it produces significantly smaller files that modern browsers understand. Set images to lazy load (WordPress does this by default since version 5.5, but check your page builder isn’t overriding it).
Expected improvement: often the single biggest win. A poorly-optimised image-heavy site can go from 8MB page weight to under 2MB.
Fix 4: Cut Down Your Plugins
Every plugin you install adds code that runs on every page load. Thirty plugins running simultaneously is not unusual on sites I’ve been asked to look at, and many of them are doing things that could be handled more efficiently another way.
Audit your plugin list. Ask yourself: is this actually being used? Does it duplicate something another plugin already does? Could a lightweight snippet achieve the same thing? Deactivate and delete anything that isn’t earning its place. Unused plugins are also a security risk.
Expected improvement: varies, but reducing from 30 plugins to 15 well-chosen ones typically makes a noticeable difference, especially in admin and Time to First Byte.
Fix 5: Use a CDN
A Content Delivery Network serves your static files (images, CSS, JavaScript) from servers geographically close to each visitor. If your site is hosted in London and a visitor comes from Manchester, that’s fine. But if your host is US-based, a CDN makes a real difference.
Recommended tools: Cloudflare (free tier is perfectly capable for most SMEs and adds security benefits too). Many managed hosts include a CDN. Bunny.net is another solid option.
Expected improvement: faster load times globally, reduced load on your server, and often improved Time to First Byte.
Fix 6: Minify and Combine CSS and JavaScript
Every time a browser loads your site, it downloads CSS and JavaScript files. If those files are bloated with whitespace and comments, or if there are dozens of separate requests, that’s unnecessary load time.
Minification removes whitespace and compresses the files. Combining reduces the number of separate HTTP requests. Most caching plugins (especially WP Rocket) handle this automatically. Enable it, test your site still works correctly, and you’re done.
Important: combining scripts can sometimes break things. Test thoroughly on a staging environment first.
Expected improvement: reduces page weight and number of requests, improving load times especially on slower mobile connections.
Fix 7: Fix Your Page Builder Output
Divi, Elementor, and other visual page builders are brilliant for building sites without writing code — but they have a cost. They output additional CSS and JavaScript, and if you’re not careful about how you use them, that output gets heavy.
For Divi specifically: avoid enabling every global setting you don’t need, use the Performance options within Divi settings to disable scripts on pages where they’re not used, and enable dynamic CSS. For Elementor: use the “Improved Asset Loading” experiment in settings. Both builders have improved significantly with recent versions, but they still require active management to stay lean.
The myth that expensive themes equal fast sites: premium themes are not automatically fast. I’ve seen £80 themes that were slower than a bare-bones twenty-twenty-four install. Theme weight is about how it’s coded, not what it costs.
The Bottom Line
Fixing a slow WordPress site is almost always achievable without rebuilding everything from scratch. Start with hosting — it’s the foundation everything else sits on. Add caching, sort your images, trim your plugins, and then work through the finer points. Run PageSpeed Insights before and after each change so you can see what’s actually making a difference. Most sites I work on can get to a solid score with a few focused hours of work, not a complete rebuild.
If your WordPress site is slow and you’re not sure where to start, I can run a full performance audit and give you a clear action plan. Get in touch at christaplinassociates.co.uk/#contact
