Why Your Website Fails on Mobile Data (And What to Do About It)

Most South African small business owners know their website is slow. They just do not know why, or what it is costing them.

Mobile data in South Africa is expensive relative to most of the world, and most people browsing the web here are doing so on a phone, often on mobile data rather than WiFi. Load-shedding compounds this: when the power is out, WiFi routers go down, and mobile data becomes the only option.

A website that takes six seconds to load on a decent UK broadband connection might take fifteen seconds on mobile data in Johannesburg. Most people will not wait. Research consistently shows that a significant proportion of users abandon a page after three seconds. On slow connections, that window closes even faster.

Why most small business websites are slow

The root cause is almost always the same: too much being sent to the browser, with no thought given to how it will be received.

Images that were never optimised. The photo your designer uploaded from their camera is probably several megabytes. Uncompressed, unresized, delivered in full to every visitor regardless of whether they are on a desktop or a phone. A single hero image can easily account for 80% of a page’s total file size.

WordPress plugin bloat. Each plugin your site uses loads its own JavaScript and CSS, often on every page even when it is not needed. A contact form plugin loading its scripts on your homepage serves no one. By the time you have ten plugins, your page might be loading dozens of separate files that the browser has to fetch one by one.

Shared hosting. Most budget hosting plans put thousands of websites on the same server. When your site gets a visitor, the server has to spin up PHP, query the database, assemble the page, and send it. Under load, this takes time. On a slow connection, that server response time is added directly to the user’s wait.

No caching. WordPress builds pages dynamically by default. Without a caching plugin correctly configured, every single visitor triggers the full database-and-PHP cycle. Even with caching, you are still working around a fundamental architectural problem.

What a fast site looks like

A static site built on a modern framework like Astro works differently. The page is built once at deploy time and stored as a ready-to-serve HTML file. When a visitor arrives, the server does nothing except hand over a file that already exists. No database, no PHP, no plugin overhead.

The result is a page that starts loading in a fraction of the time. On mobile data, this difference is the difference between a customer staying and a customer leaving.

Static hosting is also often free or very cheap, which means a faster site can actually cost less to run than a slow one.

What you can do right now

If you are not ready to rebuild the site yet, a few immediate improvements will help:

Run your site through Google PageSpeed Insights (free, just search for it and paste your URL). It will tell you exactly what is slowing things down, with specific recommendations. The most common findings are oversized images and render-blocking scripts.

Compress every image on your site. Tools like Squoosh (free, browser-based) can reduce image file sizes by 80% or more with no visible quality loss. This single change often has the biggest impact.

Check whether your WordPress site has a caching plugin installed and configured. WP Super Cache is free and straightforward.

The longer-term fix

These are patches. They help, but they are working around the underlying problem rather than solving it.

A site built for performance from the ground up — lean code, optimised images, static HTML — will outperform a patched WordPress install on every connection type. On mobile data in South Africa, where every megabyte and every second counts, the gap is especially significant.

If you are thinking about a new site or a rebuild, I work with South African small businesses specifically. Pricing is in Rands, and the sites I build are built for the conditions your customers are actually browsing in.

Find out more at rjp.digital/za.