How to plan a website for load shedding and slow data

Building a website in South Africa means building for two things most overseas guides ignore: the power going off, and a lot of your visitors being on mobile data that comes and goes. If your site only feels good on fibre with full battery, you are quietly losing the people who are browsing on a phone during an outage.

Assume the connection is slow and the battery is low

Design for the worst reasonable case, not the best. Someone is on their phone, on patchy signal, maybe tethering during load shedding, and they are not going to wait ten seconds for your homepage. If the important information loads quickly on that connection, it will feel instant on a good one.

The goal is simple. The things a customer needs, what you do, where you are, how to reach you, should appear almost immediately, even if a big photo further down is still loading.

Cut the weight

Most slow South African sites are slow for the same reasons:

• Huge, uncompressed images straight off a phone camera
• Video backgrounds that autoplay on the homepage
• Heavy sliders and animation libraries
• A pile of tracking scripts and chat widgets loading at once

Compress every image and serve it in a modern format. Drop the autoplay video, or make it an optional tap. Be ruthless about scripts. Each one you add is a little more that has to download before the page settles.

Put the essentials in text

Text loads before anything else and costs almost nothing. Your phone number, address, opening hours and main services should be real text near the top, not baked into an image or hidden inside a slider. If someone is on a bad connection and only the text loads, they should still be able to phone you or find your shop.

That is also why a visible WhatsApp or call button matters so much here. When the browsing experience is fragile, give people a fast way to jump straight to contact.

Let content load in order of importance

A page should make sense before the media arrives. Set sizes for images so the layout does not jump around as things load, and let the top of the page appear first while heavier bits fill in below. Someone should be able to read and act while the rest catches up.

Test it the honest way

Do not judge your site on your office wifi. Test it on a mid-range Android phone, on mobile data, with the browser cache cleared. Better still, throttle the connection in your browser tools to something slow and watch how long the useful parts take. That is closer to what a real customer is experiencing than anything you will see on fibre.

Also think about your own admin. If you update the site during the day, a lightweight setup you can edit quickly from a phone during an outage is worth more than a heavy system that needs a desktop and a stable connection.

When a site needs this treatment

If your current site is slow, heavy and painful on a phone, you do not always need to start again. Trimming images, removing bloated scripts and fixing the load order is usually a Fix & Upgrade. A full rebuild only makes sense if the whole thing is built on something heavy and awkward to maintain.

If you are planning a new site, build for load shedding and slow data from day one rather than bolting on speed fixes later. It is far easier to keep a site light than to slim down a bloated one. Happy to help you plan that, get in touch and we can work out where the weight is.

The short version

A South African site earns its keep by being fast and light. Compress the images, cut the scripts, keep the essentials in text near the top, and test on a real phone on real data. When the power is off and signal is weak, a lean site is the one that still gets you the call.