Your Website Is Slow on Mobile Data. Here's What It Costs You

In Douala, Nairobi, or Lagos, most of your visitors pay for the internet by the megabyte. A website that weighs 8 megabytes does not just load slowly for them; it charges them money to look at your homepage. A heavy site in this market is a paywall you built against your own customers.

This post shows you how to find out what your site really weighs, which four offenders cause almost all of it, and the fixes ranked by return on effort. Speed is a specialty of ours for exactly this reason, our sites are built for 3G first, so the numbers below come from practice, not theory. Start with the two-minute diagnosis.

Test your real-world speed in two minutes

Lab tests on office wifi lie to you. Two tests that do not:

1. PageSpeed Insights, mobile tab. Enter your homepage URL, wait, read the mobile score. Above 80 is healthy. Between 50 and 80, you are losing measurable visitors. Below 50, your site is effectively broken for anyone not on wifi. Note the "page weight" hiding in the details too: over 3 MB is heavy for a business site.
2. The throttle test. In Chrome on a computer: open developer tools, choose the network tab, set throttling to "Slow 3G", then load your site and count the seconds until you could actually use the page. That number is what a customer on a weak connection experiences, and it is routinely five times worse than the owner believes.

Do both now; the rest of the post will tell you what the numbers mean.

The four offenders that cause almost everything

Nearly every slow business site is slow for the same four reasons, in descending order of guilt:

• Uncompressed images. The champion, by far. A phone photo uploaded straight to a site is 3 to 8 MB; the same image, resized and converted to WebP format, is 100 to 200 KB with no visible difference. Fifteen such images make a site forty times heavier than it needs to be.
• Autoplay video. A background video in the header can outweigh the entire rest of the website. On mobile data it is the single most expensive design decision you can make.
• Font overload. Every font weight is a download. Sites routinely ship eight variants and use three. Two font families with two or three weights covers almost any design.
• Third-party scripts. Chat widgets, tracking pixels, embedded maps, share buttons: each is code from someone else's server that your visitor pays to download before your content appears. Keep what earns its place; a map can be a link, and three analytics tools can be one.

The fixes, ranked by return on effort

In order of impact per hour of work:

1. Convert and compress every image to WebP at sensible dimensions. Highest return of any fix on this list; often cuts total page weight by 70 to 90 percent alone.
2. Lazy-load below-the-fold media, so the first screen loads instantly and the rest arrives while the visitor reads. Standard in modern builds, absent in old ones.
3. Replace autoplay video with a compressed poster image and a play button. The visitor chooses whether to spend those megabytes.
4. Audit scripts quarterly: list every third-party script, ask what each earns, delete the freeloaders.
5. Cache and modern hosting, so repeat visits cost almost nothing and files travel from servers near your users.

If your site fails the tests and this list looks like a foreign language, this is exactly the gap our website retouching service closes: same site, same content, rebuilt to load in a fraction of the weight.

One honest boundary: if the slowness comes from the platform itself, an old theme, a bloated page builder, then compression is a bandage, and the patch-or-rebuild question is the real one. Five signs your website needs a rebuild, not a patch covers exactly that decision.

Speed is a trust signal in every market, not just Africa

The mobile-data argument makes speed urgent in African markets, but do not file this under "local optimization." Visitors in Berlin and Toronto do not pay per megabyte; they pay in patience, and they have less of it. Search engines fold speed into rankings everywhere. The same fix serves both audiences, which is the quiet advantage of building for the harder market first: a site fast enough for 3G in Douala feels instant on fiber in Frankfurt. Build for the constraint and the comfort comes free.

Quick checklist

Before you accept your site's speed, confirm that:

• your PageSpeed Insights mobile score is above 80
• your total page weight is under 3 MB
• on Slow 3G throttling, the page is usable in a few seconds, not tens
• every image is compressed WebP at sensible dimensions, not a raw phone photo
• there is no autoplay background video on mobile
• below-the-fold media lazy-loads instead of loading upfront
• you use two font families with a few weights, not eight variants
• every third-party script earns its place; the rest are removed

Want your real numbers without doing the tests yourself? Send us your URL and book a free 20-minute call. No pitch, just your speed scores, your page weight, and the ranked list of what would fix them.

Too busy for a call right now? Send us your project through the contact form. It is already prefilled for this topic, so it takes two minutes. Or message us directly on WhatsApp. Either way, you get a concrete answer within 24 hours.