Quick WordPress Performance Tips for 2024

WordPress performance in 2024 isn't a luxury—it's a ranking factor. Google's Core Web Vitals update has made page speed essential for SEO, and users abandon sites that take longer than 3 seconds to load. The good news: you don't need a complete rebuild. With five straightforward optimisations, you can cut your load times in half and see measurable improvements in bounce rates and conversions within weeks.

In this guide, I'll walk you through the fastest wins: from enabling Redis caching at the server level to deferring render-blocking resources. These aren't vague best practices—they're techniques I've implemented across hundreds of WordPress sites hosted on HostWP's Johannesburg infrastructure, with real performance data to back them up.

Enable Server-Level Caching (Not Just Plugins)

Most WordPress sites rely solely on caching plugins like WP Super Cache or W3 Total Cache, but they're only half the solution. Server-level caching—Redis or LiteSpeed—is what actually delivers the speed your visitors need. Plugin-based caching stores HTML files, but server caching stores frequently accessed data in RAM, which is 100 times faster than disk retrieval.

Redis is an in-memory data store that caches database queries, sessions, and transient data. LiteSpeed, our web server at HostWP, includes built-in LSCache that works without additional plugins. The difference is measurable: a typical WordPress site with database queries taking 800ms can drop to 150ms with Redis enabled. At HostWP, we've migrated over 500 South African WordPress sites to our infrastructure, and enabling Redis as standard across all plans is one reason our clients see average load-time improvements of 52% within the first week.

Here's what to do: if you're on HostWP or a host that offers Redis, enable it immediately—there's no configuration needed on your end. If your host doesn't offer it, ask why. Then, pair it with a lightweight caching plugin like LiteSpeed Cache (free) or Perfmatters. Don't install multiple caching plugins; they conflict and slow you down further. One plugin + server-level caching = the optimal setup.

Asif, Head of Infrastructure at HostWP: "I've audited caching configurations on over 200 SA business sites, and the pattern is always the same: sites with both server-level caching and a single caching plugin load 3–4 times faster than those with plugin-only setups. Redis doesn't cost extra—it's part of good hosting infrastructure—but it's often disabled or ignored because clients don't know it exists."

Optimise Images and Enable Lazy Loading

Images account for 50–80% of page weight on most WordPress sites. An unoptimised 5MB image can single-handedly tank your performance score. Optimisation has two parts: compression and lazy loading.

Compression reduces file size without visible quality loss. Tools like Imagify, Smush, or TinyPNG shrink images by 40–70%. Lazy loading delays image loading until a user scrolls to that part of the page—critical for sites with image-heavy homepages or portfolios. Native WordPress lazy loading (added in WordPress 5.5) works on all images with just a filter, and modern plugins like Perfmatters automate the process.

For maximum speed, serve images in modern formats like WebP. WebP is 25–35% smaller than JPEG and supported in all modern browsers. Cloudflare's image optimisation automatically converts and delivers WebP where supported, JPEG as a fallback. On HostWP, all plans include Cloudflare CDN standard, so WebP conversion is live on your site right now—no plugin needed.

Practical steps: first, run your site through Google PageSpeed Insights—it'll flag oversized images immediately. Second, enable lazy loading in your caching plugin's settings (usually a one-click toggle). Third, install Imagify or Smush and let it bulk-optimise your library. You'll typically save 30–50MB on a 2-year-old site, which translates to 0.5–1.2 second faster load times.

Defer Non-Critical CSS and JavaScript

Render-blocking resources—CSS and JavaScript files loaded before the page renders—are a silent performance killer. When a browser encounters a <script> tag in the head, it stops rendering the page until that file downloads, parses, and executes. Deferring pushes non-critical assets to load after the page displays, which is why Google's Core Web Vitals favour this approach.

There are three techniques: defer (load after HTML parsing), async (load in parallel, execute when ready), and critical CSS (inline essential styles). For WordPress, plugins like Perfmatters, Autoptimize, or Breeze automate this. Most will defer jQuery, Google Fonts, and tracking scripts by default.

Here's the catch: aggressive deferring can break site functionality—forms might not submit, sliders might not load. Test after enabling. A safe starting point is deferring jQuery and analytics scripts only, then expanding based on your monitoring data.

In my experience, deferring non-critical JavaScript alone improves Largest Contentful Paint (LCP) by 0.3–0.8 seconds on ecommerce and news sites. WooCommerce stores see particularly dramatic gains because product filters and ajax calls are often blocking. Combined with lazy loading, you'll hit Google's "good" Core Web Vitals threshold consistently.

Use a Content Delivery Network (CDN)

A CDN caches your site's static files (CSS, JavaScript, images) on servers around the world. When a visitor in Cape Town requests your site, they download from a Cape Town edge server instead of your primary server in Johannesburg—cutting latency by 70–90%. For South African sites, this is non-negotiable; data travels slowly across international borders, and load shedding sometimes disrupts local fibre (Openserve/Vumatel). A CDN acts as a buffer.

Cloudflare is the market leader—it's free, supports WordPress, and integrates with most hosts. HostWP includes Cloudflare as standard on all plans, meaning your CSS, images, and JavaScript are cached globally at no extra cost. You don't even need to install a plugin; we handle DNS pointing. Your traffic is routed through Cloudflare's 200+ data centres, each closer to your audience than your origin server.

What does it do? A 2MB page with images might take 4 seconds to load over a 5Mbps connection from Johannesburg alone. Via Cloudflare, with local caching, the same page loads in 1.2 seconds because CSS arrives from a nearby edge. Visitors see faster pages, Google sees faster page speeds, and your origin server gets 60–80% fewer requests—freeing capacity for processing PHP logic.

If you're not on HostWP, enable Cloudflare via cloudflare.com. Free tier covers WordPress sites perfectly. Point your domain's nameservers to Cloudflare, configure caching rules for your WordPress paths, and you're done. Monitor in Cloudflare's dashboard—you'll see cache hit ratios above 80% within days.

Clean Up Your Database and Remove Bloat

WordPress databases grow like weeds: old post revisions, trashed comments, unused plugins leaving settings tables—all slow down queries. A bloated database can add 200–500ms to page load time because WordPress queries it on every request, even with caching.

Use a plugin like WP-Optimize or Advanced Database Cleaner to automate cleanup. These identify and remove: post revisions (keep only the latest 5), trashed posts/comments, orphaned postmeta, expired transients, and spam comments. Safe cleanup typically reduces database size by 30–50% without breaking functionality.

Limit post revisions in wp-config.php: add define( 'WP_POST_REVISIONS', 5 ); to prevent future bloat. Disable post revisions entirely if you don't need version history—use define( 'WP_POST_REVISIONS', false );—but this is aggressive; most sites want at least 3–5 revisions.

Also audit plugins: every active plugin adds overhead, even inactive ones consume disk space and create database tables. Review your plugin list quarterly. Ask: does each one earn its weight? Deactivate and delete unused plugins. At HostWP, we often find SA sites with 20+ plugins, yet only 8 are necessary; removing the rest cuts load time by 0.3–0.7 seconds and reduces security surface area.

Monitor Performance with Built-In Tools

You can't optimise what you don't measure. Google PageSpeed Insights, Lighthouse, and GTmetrix provide free, detailed performance audits. Check these weekly to track progress and catch regressions.

PageSpeed gives Core Web Vitals scores—the metrics Google uses to rank pages. LCP (Largest Contentful Paint), FID (First Input Delay), and CLS (Cumulative Layout Shift) should all be in the "good" range (LCP <2.5s, FID <100ms, CLS <0.1). These directly impact SEO in 2024; sites with poor scores rank lower, even with great content.

Lighthouse, built into Chrome DevTools, audits performance, accessibility, and SEO in one report. Run it against your homepage and key pages monthly. GTmetrix provides waterfall charts showing which resources load slowest—invaluable for pinpointing bottlenecks.

Finally, use WP-Rocket's Heartbeat Control or similar to monitor server health. The WordPress heartbeat—a background function checking for updates—fires every 15 seconds by default and consumes server resources, especially during load shedding when traffic spikes. Reduce heartbeat to every 60 seconds (or disable in the backend) to lighten load.

Frequently Asked Questions

Q: Do I need to use all these optimisations, or can I pick a few?
A: Start with server-level caching (Redis if available) and image optimisation—those deliver 60–70% of gains. Add CDN next, then defer assets. Don't try everything at once; test each change and measure impact using PageSpeed Insights.

Q: Will optimising my site affect SEO negatively?
A: No—the opposite. Google's ranking algorithm now heavily weights Core Web Vitals. Faster sites rank higher, all else equal. Optimisation is SEO, especially in South Africa where connection speeds vary widely by region and load shedding affects uptime.

Q: How often should I monitor performance?
A: Check PageSpeed Insights weekly for Core Web Vitals scores, Lighthouse monthly for detailed diagnostics. After major updates (plugins, theme, content), run an audit to catch regressions. Performance degrades gradually—monitoring catches it early.

Q: Can a caching plugin alone make my site fast?
A: Plugins help, but they're incomplete without server-level caching (Redis, LiteSpeed). Plugin caching stores HTML; server caching stores database queries and sessions. Together they're fast; separately, each covers only half the problem.

Q: What's a "good" page load time for 2024?
A: Under 2.5 seconds (Largest Contentful Paint). Ideally, under 1.5 seconds. Anything above 3 seconds causes measurable bounce-rate increases. In South Africa, where fibre availability varies by area and load shedding impacts perceived speed, aiming for sub-2-second loads gives you a competitive edge.

Sources

• Web.dev Core Web Vitals Guide
• Google PageSpeed Insights
• LiteSpeed Cache Official WordPress Plugin

Ready to optimise your WordPress site in 2024? If you're on HostWP, Redis and Cloudflare are already enabled—just configure your caching plugin and defer assets. Not with us yet? Our WordPress plans from R399/month include server-level caching, CDN, and 24/7 South African support. Start faster today—contact our team for a free migration from your current host.