The real cost of a slow website in East Africa

Slow pages lose visitors, and the effect is sharper in East Africa, where much of the web traffic comes from mobile devices on 3G or 4G connections with variable latency.

These aren't technical curiosities. They're revenue problems. Every second your page takes to load, you're losing visitors who won't come back. In a market where mobile data costs real money, you're also asking your customers to pay for the privilege of waiting.

The fix isn't complicated, but it requires discipline. Start with the basics: optimise images (WebP format, responsive sizes, lazy loading), eliminate render-blocking resources, and defer non-critical JavaScript. These three changes alone often make the biggest difference.

Then look at your architecture. If you're serving a single-page application to users who just want to read about your services, you're shipping a JavaScript framework to do the job of HTML. Server-side rendering with selective hydration gives you the best of both worlds — fast initial loads with interactive features where they matter.

Consider your hosting. A website served from a European or American data centre adds a round trip of a few hundred milliseconds for East African users before any content arrives. A CDN with points of presence close to your users removes most of that delay.

Finally, test on real devices and real networks. Your website loading in 1.5 seconds on your office fibre connection tells you nothing about the experience of a potential customer in Nakuru on Safaricom 3G. Chrome DevTools throttling is useful but imperfect — invest in a testing device running on an actual mobile connection.

Performance is not a feature you add after launch. It's a constraint you design for from the start. In East Africa, it might be the single most important design decision you make.