Moducraft
Technical 28 August 2026 · 6 min read

Why your website feels slow on South African mobile networks - and what to fix

Your website loads instantly on your office wifi - and takes eight seconds on a customer's phone outside town. Here's why South African mobile conditions punish heavy websites, what slowness costs you, and the fixes in priority order.

Your website is faster for you than for your customers

Here's an uncomfortable experiment. Take your phone, switch off wifi, drive ten minutes out of town, and open your own website on mobile data. Time it.

For a lot of small business websites, the result is sobering. The site that snaps open on the office fibre takes five, eight, twelve seconds on the connection your actual customers are using. And most of those customers are on phones: for the small businesses we work with, mobile is the majority of traffic, often by a wide margin.

Slow doesn't just feel bad. People give up - more than half of mobile visitors abandon a page that takes more than a few seconds to appear, and every extra second costs conversions. Google uses page speed as a ranking signal, so slow sites also get found less. You pay twice.

Why South African conditions punish heavy websites

Speed advice written for American or European audiences assumes fast networks and expensive phones. South African reality is different in four ways:

Coverage is uneven. Signal is good in metro centres and patchy everywhere else - and the Western Cape's small towns, farm roads, and mountain passes have plenty of "everywhere else". A heavy page that survives 5G in Cape Town dies on two bars of LTE outside Riebeek-Kasteel.

Data costs real money. Many of your customers are on prepaid data. A 10MB homepage isn't just slow - it's using someone's airtime. Lean pages are a courtesy that visitors feel, even if they never articulate it.

The average phone isn't a flagship. Mid-range Android phones dominate the market. Sites drowning in JavaScript don't just download slowly on those devices - they take seconds to process after downloading, which is why a page can be "loaded" and still frozen.

Distance adds delay. If your site is hosted in Amsterdam or Dallas, every request makes an intercontinental round trip before anything appears. It's a constant tax on every visitor.

The usual suspects, in order of likelihood

1. Oversized images

The single most common cause of a slow small business website, by far. A photographer delivers beautiful 8MB images, they get uploaded straight into the website, and now the homepage is 40MB of photography being squeezed down a mobile connection.

The fix is straightforward: images sized to the dimensions they're actually displayed at, compressed, served in a modern format like WebP, and lazy-loaded so images further down the page don't hold up what's on screen. A properly built site does this automatically at upload; on other platforms, plugins and image tools can get you most of the way.

2. Page builder and plugin bloat

Every plugin, every page builder section, every "just one more" feature loads its own scripts and styles - on every page, whether that page uses them or not. Site speed erodes one small addition at a time, until a page that displays three paragraphs and a photo is loading two megabytes of code. We've written about why page builders hold your site back; speed is a big part of that story. If your site has accumulated years of plugins, an audit that removes the unused ones is often the cheapest speed win available.

3. Too much JavaScript

Chat widgets, pop-ups, sliders, animation libraries, three different analytics tools, a social feed embed - each one seems harmless. Together they're the reason the page freezes while a mid-range phone chews through them. Be ruthless: every third-party widget must justify its cost. If the live chat nobody answers is costing you two seconds of load time, it's not free.

4. Hosting that's wrong for your audience

Cheap shared hosting means your site queues behind hundreds of others on an overloaded server - the delay before the page even starts arriving. Hosting overseas adds the round-trip tax on top. For a South African audience you want either hosting in South Africa or a content delivery network (CDN) that caches your site at a Johannesburg or Cape Town edge, so it's served from nearby regardless of where the server lives. Proper caching - so pages are served pre-built instead of being reassembled for every visitor - belongs in the same conversation.

5. Fonts and everything else

Custom fonts loaded from third-party services, autoplaying background videos, uncompressed logos, tracking pixels from campaigns long finished. Individually small, collectively meaningful. A once-a-year clear-out is worth an hour of anyone's time.

How to actually measure it

Two tools, both free:

PageSpeed Insights (pagespeed.web.dev) - enter your address, look at the mobile score first, and read the "Opportunities" list; it names your specific problems in plain terms. Scores comfortably above 80 on mobile are good territory for a small business site; below 50 means you're losing customers to it.

Your own phone, on data, away from town. No lab metric replaces feeling what your customer feels. Test the homepage and, more importantly, the pages where money changes hands - your contact page, your menu, your checkout.

When we rebuilt the Doughboys e-commerce platform, the previous site scored around 40; the rebuild scores 89+. That's the difference between a shop that leaks mobile customers and one that doesn't - on the same products, for the same audience.

Where to start, in priority order

  1. Compress and resize your images. Biggest win, least effort, no developer required on most platforms.
  2. Remove plugins and widgets you don't use. Deactivate, test, delete.
  3. Check your hosting location and add caching or a CDN. If your audience is South African and your server isn't, fix that.
  4. Retest on PageSpeed Insights and your own phone. Measure again after each change so you know what actually helped.
  5. If the platform itself is the problem, weigh a rebuild. There's a point where optimising a bloated build costs more than doing it properly - a lean site is fast because of how it's made, not because of what was bolted on afterwards.

Speed isn't a technical vanity metric. It's whether the customer standing on a farm road with two bars of signal gets your menu, your prices, your phone number - or gives up and tries the next place. If you'd like to know where your site stands, get in touch and we'll run an honest speed check and tell you which of these culprits is yours, and what it would take to fix.

JP

Johan Pretorius

Johan Pretorius is the founder and lead developer of Moducraft, a Cape Town web studio working with small businesses across the Western Cape. 18 years building for the web.

Want to talk about your project?

Book a 20-minute call. No obligation, no sales pitch.

Book a 20-minute call