WooCommerce Hosting in South Africa: What to Look For

A cheap WordPress plan runs a brochure site happily. A store is a different workload. Choosing WooCommerce hosting in South Africa comes down to a short list: a current PHP version and enough memory, enough capacity for several people checking out at once, caching that speeds up the shop without breaking the cart, automatic backups you have tested, and ideally a server close to your customers. Below is that list in plain terms, plus the honest point at which shared hosting stops being enough.

If you are still at the planning stage, start with how to start an online store in South Africa.

What a WooCommerce store needs that a brochure site does not

One developer's guide puts it well: WooCommerce is WordPress with a heavy commerce layer added, and the cart and checkout cannot be cached the easy way ^[3]. Catalogue pages can be cached, but every cart, checkout and account page has to be built fresh for that shopper. A brochure page looks the same for everyone, so a host can save a copy and serve it instantly. A cart is different for every shopper, and every checkout writes to the database, sends emails and talks to your payment gateway.

That is why a plan that handles cached browsing comfortably can still struggle when several shoppers check out at the same time, because each of those requests needs the server to do real work.

The specs that actually matter, and what to ask a host

WooCommerce's own server recommendations, checked on 4 October 2026, ask for PHP 8.3 or greater, MySQL 8.0 or greater or MariaDB 10.6 or greater, HTTPS support, and a WordPress memory limit of 256 MB or more ^[1]. WooCommerce notes that it also works with PHP 7.4 and MySQL 5.6, but that these versions have reached their official end of life and may expose your site to security vulnerabilities ^[1]. Choose a currently supported PHP version that meets WooCommerce's recommendation.

Beyond those minimums, WooCommerce's hosting guide lists what to ask a host for ^[2]:

• PHP workers: each customer visit or checkout uses one PHP worker, a process that handles one request at a time. WooCommerce suggests a good starting point is a host offering 5 to 10 dedicated workers ^[2].
• Object caching, which stores the results of database queries so they are not repeated on every page.
• A built-in CDN, a network that serves images and files from locations close to the visitor.
• Scaling for spikes: WooCommerce notes that email campaigns, ads or influencer mentions can suddenly triple or quintuple your usual traffic ^[2].
• Support staff who understand WooCommerce, not just WordPress.

Caching that speeds up the shop without breaking the cart

Caching is where many store owners get caught out. The pages that matter most for revenue, cart, checkout and my-account, are different for every shopper, and a normal full-page cache cannot serve them, because showing one shopper's checkout to the next would be a data leak ^[3].

• Use page caching for product and category pages, which is where it helps most.
• Make sure cart, checkout and my-account are excluded. Most serious caching plugins do this, but confirm the exclusion exists rather than assuming it ^[3].
• Add a persistent object cache, such as Redis, so the pages that cannot be page-cached stop re-running the same database queries ^[3].

“Cache the catalogue, never the checkout.”

Why a checkout slows down when it matters most

In my experience, stores rarely slow down on a quiet Tuesday. They slow down on payday weekend or during a promotion, when several shoppers check out at once and the server runs out of workers or memory. Orders stall, and payment notifications from your gateway can time out, leaving orders in an uncertain state. I go through the common causes in why affordable WooCommerce sites break at checkout.

My own store runs WordPress and WooCommerce on Amazon Lightsail, chosen for bundled compute, storage and networking at a predictable cost, with CloudFront in front, as described on the store project page. My published lesson from that build is that the CloudFront cache strategy directly affects how fast the storefront loads.

Local hosting, Rand pricing and load-shedding

Where the server sits matters. One South African host explains that the further data has to travel, the more latency slows your store, so it makes sense to choose a provider with servers in South Africa ^[5]. A CDN narrows the gap for images, but the cart and checkout still talk to the main server.

Local WooCommerce-ready plans are billed in Rand. Checked on 4 October 2026, Hyper Layer lists WordPress plans from R99 to R499 a month with LiteSpeed web servers, Redis caching and daily off-site backups ^[6], and HostAfrica lists a starter plan from R99 a month with daily backups ^[4]. In one review's test, HostAfrica recorded a 272 ms time to first byte ^[4]. Confirm current prices and whether they include VAT with each provider.

Load-shedding is a question for your host, not your office. A store hosted in a data centre does not go down when your premises lose power. I compare shared and cloud hosting in plain terms in AWS vs shared hosting.

When shared hosting stops being enough

Shared hosting is not automatically wrong. WooCommerce's own guide says that at under US$10,000 a month in sales, you do not need dedicated servers or real-time backups, but you do need WooCommerce pre-installed, SSL, automatic backups and a reliable uptime guarantee ^[2]. Many South African stores sit comfortably in that range on a good shared or managed WordPress plan.

Signs you have outgrown it:

• Checkouts time out or slow down during promotions.
• Your host cannot tell you how many PHP workers you have, or will not raise the memory limit.
• There is no staging copy, so every update is tested on the live store.
• Backups exist but nobody has ever restored one.

What to do next

• Check your current PHP version and memory limit in WooCommerce, Status.
• Ask your host how many PHP workers you have, whether object caching is available, and where the server is.
• Confirm cart, checkout and my-account are excluded from your page cache.
• Restore a backup to a staging copy once, to prove it works.
• If checkout struggles under load, get the hosting reviewed before your next promotion.

If your store slows down when it gets busy, get in touch and I will look at whether it is the hosting, the caching or the code.