A WordPress site slow to load is a WordPress site that costs you money. Google Search Console will quietly downrank you. Mobile visitors will bounce before they see your offer. Cart abandonment will creep up. And worst of all, when your WordPress site slow problem hides behind a hundred plausible causes, you will not know which one is actually hurting you.
This guide walks through the seven fixes that actually work on real-world WordPress sites — in priority order, with the diagnostics to confirm each one is needed. Most slow WordPress sites need three of these; almost none need all seven.
Why your WordPress site slow problem needs a diagnosis first
Before you change anything, run your homepage through PageSpeed Insights on the mobile tab. Note the LCP, INP, CLS, and the top three opportunities Google lists. Then run it through GTmetrix with Cape Town selected as the test location for a real SA visitor view.
Together these tell you what is slow (which metric) and why (which resources). If your TTFB is high, the problem is your host or your database. If your LCP is high but TTFB is fine, the problem is the page itself — images, render-blocking CSS, fonts. If only your INP is high, the problem is JavaScript and page builder bloat. Different problems, different fixes.
Fix 1 — Hosting upgrade
The most common reason a WordPress site slow problem persists is shared hosting under-spec’d for the load. If your TTFB is above 600 ms consistently, no plugin will fix that — it is the server. We move clients onto AWS-backed LiteSpeed infrastructure because our managed WordPress hosting consistently delivers sub-200 ms TTFB.
Cheap hosting is the false economy of the SA WordPress market. R49/month sounds great until the R49/month server has 800 sites on it.
Fix 2 — A real caching plugin
LiteSpeed Cache is free, server-aware, and best-in-class if your host uses LiteSpeed. WP Rocket is the paid alternative that works regardless of server. W3 Total Cache and WP Super Cache are the free fallbacks. Pick one — never two; they conflict.
Configure: enable page cache, browser cache, CSS minification, JS minification, and lazy load images. Test after each change with a private incognito window.
Fix 3 — Image optimisation
Most WordPress site slow complaints trace back to one cause: the homepage hero is a 3 MB PNG. Convert to WebP, resize to actual display dimensions, and lazy-load below-the-fold images. ShortPixel and Imagify both do this automatically on upload. The hero image should be under 200 KB. Inline post images should be under 80 KB.
Fix 4 — Plugin audit
Every active plugin runs PHP on every page request. A typical WordPress site has 4–6 plugins it doesn’t need. Open Plugins → Installed, sort by Last Activity, and ask: have I used this in the last 90 days? Deactivate, test, then delete.
The plugins most commonly worth removing: old contact form plugins from a previous theme, abandoned slider plugins, social-share plugins (replace with theme-native), unused SEO migrations from Yoast→Rank Math switches.
Fix 5 — Replace the page builder for templates
Page builders are great for one-off landing pages and bad for blog templates that load on every post view. Move blog templates and recurring layouts to native Gutenberg or a block theme; keep the builder for the marketing pages where its drag-and-drop saves real time.
Fix 6 — Defer non-critical JavaScript
Analytics, chat widgets, A/B testing pixels, social embeds — defer them. LiteSpeed Cache and WP Rocket both have a one-click “Delay JS” or “Defer JS” setting. Test in incognito after switching it on to confirm nothing essential broke.
Fix 7 — Put Cloudflare in front
Cloudflare‘s free tier caches static files at the edge (yes, including Cape Town and Johannesburg). Enable it, point your DNS at Cloudflare, and turn on Auto Minify and Brotli compression. The TTFB drop for repeat visitors is dramatic.
Re-test and document
After each change, re-run PageSpeed Insights and write down the LCP, INP, and CLS. You want a paper trail so you know which change moved which metric. Most WordPress sites can go from a 40 mobile score to an 85 with the first three fixes — hosting, caching, and image optimisation.
When to call for help
If you have done all seven and your WordPress site’s slow problem is still there, the cause is usually in the theme code or a specific custom plugin. That is when a performance audit pays for itself — we audit, fix, and document the changes so they stick.
Read more deep dives on our blog, or get in touch for a performance audit on your WordPress site.
