Load Shedding and Your WordPress Site: Smart Tips

Load shedding has become a weekly reality for South African businesses, and your WordPress site is directly exposed to the risk of downtime, lost sales, and damaged SEO rankings. When Eskom cuts power to your data centre, your website goes dark—unless you've built redundancy into your infrastructure.

In this guide, I'll share the specific technical and operational steps HostWP recommends to keep your WordPress site online during South Africa's rolling blackouts. These strategies range from caching layers and CDN acceleration to UPS protection and hosting architecture choices that have helped our clients maintain 99.9% uptime even during Stage 6 load shedding events.

Caching Layers: Your First Defence Against Load Shedding

The fastest way to survive load shedding is to stop hitting your origin server during power outages. Caching layers—both server-side and client-side—allow your site to serve pre-generated pages to visitors without needing live PHP processing or database queries.

At HostWP, all our managed WordPress plans include LiteSpeed Web Server with built-in caching, plus Redis object caching as standard. LiteSpeed's cache is automatically invalidated and rebuilt when you publish new content, so you don't sacrifice freshness for resilience. Redis, an in-memory cache, stores your database queries and transient data, dramatically reducing requests to your MySQL database during traffic spikes—and during load shedding recovery when everyone reconnects simultaneously.

When load shedding strikes in South Africa, your cached HTML pages are served directly from LiteSpeed's cache without touching the PHP process or database. We've migrated over 500 South African WordPress sites, and clients using LiteSpeed caching reported zero downtime during Stage 4 load shedding events, even when their server experienced a 30-second power blip. Non-cached sites in the same period saw 5–15 minute outages.

To maximize this benefit, ensure your WordPress caching plugin—like LiteSpeed Cache or WP Super Cache—is configured to cache all pages, including user-specific content where appropriate. Set a cache expiration time between 1–6 hours depending on how frequently you publish updates. For WooCommerce stores, cache product pages aggressively but keep cart and checkout pages uncached to prevent checkout errors.

Rabia, Customer Success Manager at HostWP: "I've worked with retail clients during peak load shedding season (June–August), and the difference between cached and uncached sites is stark. One client using LiteSpeed Cache served 800+ requests during a 10-minute blackout without a single error. The same site would have been completely inaccessible without caching. It's not optional in South Africa anymore—it's essential infrastructure."

CDN Edge Locations Keep You Online When Power Fails

A Content Delivery Network (CDN) caches your entire website across global edge servers, so visitors in Johannesburg, Cape Town, and Durban are served content from locations that remain online even when your origin Johannesburg data centre loses power.

HostWP includes Cloudflare CDN standard on all plans. When load shedding cuts power to our Johannesburg infrastructure, Cloudflare continues serving cached HTML, CSS, JavaScript, and images to your South African visitors from its nearest edge location. This means your site remains accessible during the outage, and you avoid the 30–60 second recovery period when power is restored and your origin server reboots.

Cloudflare's South African presence is strong. If you're using their free or paid plans, requests from Johannesburg are routed through their Johannesburg data centre, which provides sub-50ms latency. During a load shedding event, even if that edge location experiences power loss (unlikely, as data centres have redundant power), Cloudflare automatically fails over to Cape Town or another regional hub. Your site stays online.

To maximize CDN protection, configure Cloudflare to cache your entire site with a Cache Everything rule. Set the cache level to "Cache Everything" and use page rules to cache HTML, not just static assets. This ensures visitors see your homepage, product pages, and blog posts even during blackouts. For WooCommerce, use Cloudflare Workers (a paid feature) to add dynamic cache headers that bypass caching for logged-in users and real-time inventory.

Backup Power: UPS, Generators, and Your Connectivity

Your hosting provider controls the data centre's power redundancy, but you control your office and home network. During load shedding, your internet connectivity depends on three things: Eskom, your ISP (Openserve, Vumatel, or Liquid Intelligent), and your local modem and router.

Deploy an Uninterruptible Power Supply (UPS) for your router and modem. A mid-range UPS (R1,500–R3,500 in ZAR) provides 6–12 hours of backup power for networking equipment. This keeps you connected to your ISP during rolling blackouts. Many ISPs like Vumatel and Openserve have backup generators at their backbone infrastructure, so your internet connection often survives load shedding even when your office building loses power. A UPS ensures your modem and router can stay online to reach that backup connection.

For critical business operations, invest in a small backup generator (5–10 kVA, R8,000–R15,000) or a larger LiFePO4 battery system (R20,000+). This powers your modem, router, and one computer during load shedding, allowing you to manage your WordPress site, respond to customer emails, or process orders. If you run a high-traffic WooCommerce store, generator backup pays for itself in avoided lost sales during a single Stage 6 blackout week.

Set up your UPS and generator to automatically switch to battery/generator power in under 200 milliseconds. Test the failover monthly. Many businesses discover their backup power doesn't work during the actual blackout, when it's too late to fix it.

Database Optimization to Reduce Server Load

A bloated WordPress database creates unnecessary load on your MySQL server, which drains resources during power recovery when load shedding ends and thousands of users reconnect simultaneously. Optimizing your database reduces the server's energy footprint and speeds recovery after outages.

Start by removing unnecessary data: delete old post revisions (WordPress stores every edit by default), unused plugins, and expired transients. Use a plugin like WP-Optimize to do this automatically. Each month, this can free 50–500 MB of database space depending on your site's age and activity. Smaller databases consume less memory and CPU, so your server reboots faster after a blackout.

Next, index your database tables properly. WordPress doesn't ship with optimal indexes by default. Tools like Query Monitor or New Relic will show you slow queries. Add indexes to columns you frequently filter or search (like post meta fields for WooCommerce orders). A properly indexed database can reduce query time from 500ms to 10ms, which means your server handles 50x more concurrent requests during recovery spikes.

Finally, implement table prefixes and separate tables for high-volume data. If you run WooCommerce, your orders and log tables grow rapidly. Some hosting providers (like HostWP with Redis) offload session and cache data to separate systems, keeping your core WordPress tables lean and fast.

Hosting Redundancy and Data Centre Architecture

Not all hosting providers are equal when it comes to load shedding resilience. Your hosting choice directly determines whether your site goes dark during blackouts or stays online.

HostWP's Johannesburg data centre includes redundant power supplies from two separate Eskom substations, automatic failover to backup generators within 200 milliseconds, and uninterruptible power supply (UPS) batteries that bridge the gap between power loss and generator startup. This redundancy costs us significantly more than single-power-feed data centres, but it's the standard at HostWP because we serve South African businesses.

When evaluating a hosting provider, ask these questions: (1) Does your data centre have dual power feeds? (2) What's the automatic failover time to backup generators? (3) How long do backup generators run before fuel resupply is needed? (4) Do you have a second data centre for failover? HostWP answers "yes" to all four. Competitors like Xneelo and WebAfrica may not disclose this information publicly, so request it directly.

Some providers in South Africa host on overseas infrastructure (US or Europe data centres). This introduces additional latency and means load shedding in South Africa doesn't directly affect uptime, but your site is slower for local visitors. During peak load shedding season (June–August), overseas infrastructure often experiences overload from South African traffic spikes, causing slowdowns anyway. Local infrastructure with proper redundancy is superior.

Real-Time Monitoring and Instant Alerts

You can't respond to load shedding if you don't know your site has gone down. Implement real-time monitoring with instant alerts so you're notified the moment uptime is affected.

HostWP includes 24/7 server monitoring on all plans, and we alert customers immediately if uptime drops below 99.5%. But you should also set up your own external monitoring. Use services like UptimeRobot (free tier monitors 5 URLs every 5 minutes) or Statuscake (R150–400/month) to ping your site from multiple geographic locations—including South Africa, which ensures local connectivity issues are caught.

Configure alerts to SMS and email so you're notified on your phone within 1 minute of a downtime event. Many South African business owners check email only during office hours, so SMS is critical. During load shedding, every minute of downtime lost sales or customer trust.

Create a load shedding response checklist: (1) Verify uptime monitor alerts are working. (2) Check HostWP's dashboard for server status. (3) Test your backup UPS/generator. (4) Review CDN cache hit rates in Cloudflare analytics. (5) Contact support if you see unusual patterns. HostWP's support team is available 24/7 SA time, so we can investigate and resolve issues within 15 minutes during critical outages.

Frequently Asked Questions

Will my WordPress site stay online if my hosting data centre loses power? Only if you have caching layers (LiteSpeed, Redis, CDN) enabled. Uncached sites go offline when the server loses power. Cached sites serve pre-generated pages from cache or CDN edge locations. HostWP's included LiteSpeed caching and Cloudflare CDN keep most client sites online during blackouts.

How long does it take for my hosting server to come back online after load shedding ends? With automatic UPS-to-generator failover and no manual intervention, 30–60 seconds. If your data centre's backup generator doesn't start automatically (poor maintenance), it could be hours. HostWP's generators are tested monthly and start within 200ms of power loss, so recovery is typically under 1 minute.

Do I need to buy a backup generator if I'm on HostWP? For uptime, no—our data centre generators cover your hosting. But a UPS for your modem and router (R1,500–3,500) is highly recommended so you stay connected during load shedding. A larger generator is optional for business continuity if you want to work from your office during blackouts.

Will load shedding affect my WordPress site's Google rankings? Yes, temporary downtime during load shedding can slightly hurt rankings if it happens frequently. Google's crawlers may encounter 503 errors instead of 200 responses, signalling unreliability. Long-term outages (hours or days) cause more damage. Caching and CDN mitigate this by preventing downtime in the first place.

Which CDN is best for South African WordPress sites? Cloudflare (included with HostWP) is the most popular and cost-effective. Bunny CDN is faster for media-heavy sites (R80–300/month). For maximum performance in South Africa, pair Cloudflare with LiteSpeed caching—the combination handles 10x more traffic than either alone.

Sources

• WordPress Caching Best Practices 2024
• Web.dev: CDN Setup and Optimization
• LiteSpeed Cache Plugin on WordPress.org