Loading
Most Kenyan businesses check how their website looks. Very few check how fast it loads. The research says speed is where the money leaks: more than half of mobile visitors leave a page that takes over three seconds.
By Hanova Editorial
A website that takes five seconds to load does not feel broken. Nothing crashes. No error appears. The visitor simply gets tired of waiting, presses back, and buys from someone else. Because nobody sees it happen, slow speed is the easiest problem to ignore and one of the most expensive to have.
The numbers here come from large studies, not guesses. Google's research on mobile behaviour found that 53% of visitors abandon a mobile page that takes longer than three seconds to load. Behaviour data collected across industries shows the same pattern: pages that load in about two seconds see bounce rates near 9%, while pages that take five seconds see bounce rates climb toward 38%.
Speed also changes what people do after they stay. The often-cited Aberdeen Group finding puts it simply: every extra second of load time cuts conversions by about 7%. Google and Deloitte measured it even more tightly in their "Milliseconds Make Millions" study: improving mobile load time by just 0.1 seconds lifted retail conversions by 8.4% and average order value by 9.2%.
If your website brings you ten enquiries a week, a slow site does not announce that it removed three of them. It just never shows them to you.
Most of your visitors are on phones. Mobile devices account for roughly two thirds of web traffic globally, and in Kenya the skew is stronger because the phone is the primary computer for most people. Mobile connections in matatus, estates and rural towns are also less forgiving than office wifi: a site that feels acceptable on your laptop in the CBD can be painful on a 4G connection in Kitengela.
Google also uses speed as a ranking input through Core Web Vitals, its set of user-experience measurements. Industry crawls in 2025 found that only around 42% of mobile sites pass all three Core Web Vitals. That is bad news for the slow majority and an opportunity for you: passing is a real, measurable advantage that most of your competitors do not have.
Core Web Vitals sounds technical but it is only three measurements:
You can test any page free at PageSpeed Insights. Type your address, and you get a scored report in under a minute. Test the mobile tab first, because that is where your customers are.
In our audit work the same culprits appear again and again: oversized images uploaded straight from a phone camera, themes and page builders loading dozens of scripts, no caching so every visitor rebuilds the page from scratch, and hosting located far from the audience. None of these are exotic problems. They are engineering hygiene.
The fixes are equally unglamorous and equally effective: compress and resize images, cache pages and data so repeat work is not repeated, cut scripts you do not use, and measure again. We recently applied exactly this to our own site: caching the database reads behind our pages took the homepage from about six seconds to about one second, a five times improvement, without changing anything a visitor sees.
Speed is not a technical vanity metric. It is the front door of your business. If the door takes five seconds to open, half the people walking in give up before they see what you sell. Test your site today, and if the mobile score is red, treat it with the same urgency you would treat a shop that customers cannot enter.
WordPress is fine for a weekend blog. For a business that depends on its website, custom engineering wins where it counts: speed, security, ownership and what it costs you over the years, not just at launch.
The exact dependency list we add to every greenfield project, the rationale behind each choice and the libraries we deliberately keep out of every stack, and why.
Feature-phone constraints forced Kenya's most successful API into a shape Silicon Valley still hasn't reproduced, a study in operational pragmatism over architectural elegance.
