Menu
A few months back I sat in a client's office in Westlands while her sales rep tried to place a test order on her own brand-new website. Office WiFi was down that morning, so we were on ordinary 4G data. It took her four attempts to even find the "Request a Quote" button, because it was buried under a full-screen image slider that took close to nine seconds to load. That, in one scene, is what UI/UX design in Nairobi actually means. Not whether the homepage looks sharp on a 27 inch monitor during a design review, but whether a real person on a real phone, on real Kenyan network conditions, can do the thing your business needs them to do.
I bring this up because a lot of web agencies here treat "UX" as a fancy line item you add after the "design" part is finished. That's backwards, and it costs businesses money. UI, the user interface, is what a site looks like: the colours, the layout, the fonts. UX, the user experience, is whether people can actually use it without getting lost, annoyed, or giving up halfway through. When I'm briefing a project through our web design work, UX decisions come before a single pixel of "look" gets decided, because a beautiful site nobody can navigate is just an expensive brochure nobody reads.
The businesses that come to us after a bad experience with a previous agency almost always describe the same symptom: "the site looks good but nothing happens." Traffic arrives, sometimes decent traffic, and enquiries don't follow. Nine times out of ten, when I actually watch someone use the site rather than just looking at it myself, the cause isn't mysterious. It's a menu that makes sense to the person who built it and nobody else, a phone number that's an image instead of tappable text, or a contact form that silently fails on a slower connection with no error message at all. None of that shows up in a screenshot. All of it shows up the moment you hand the phone to a stranger and watch.
Kenya's smartphone penetration hit 92.9% by the end of 2025, meaning almost every phone connected to a Kenyan network is now a smartphone, according to Communications Authority of Kenya data reported by Techweez. For most businesses I work with, this isn't an abstract number, it's 70 to 85% of their actual website traffic depending on the sector. And yet I still get sent "finished" designs by other agencies that were clearly built on a desktop screen first, with mobile squeezed in as an afterthought. You can usually tell within ten seconds: buttons too small to tap accurately, text that needs pinch-zooming, forms that force you to scroll sideways.
Designing mobile-first isn't a style preference, it's a sequencing decision. You design the smallest screen first, decide what's essential enough to earn space there, then expand outward for tablet and desktop. Whatever doesn't survive that first cut probably didn't need to be on the page at all.
Here's a number that should worry more Kenyan business owners than it does: Google's own mobile research found that 53% of visitors abandon a mobile site if it takes longer than three seconds to load. Three seconds. Most Kenyan business websites I audit for the first time load in somewhere between six and twelve.
Mobile internet here has genuinely improved. Average mobile speeds climbed from around 21 Mbps in 2024 to roughly 45 Mbps by the end of 2025, enough to push Kenya ahead of Nigeria in continental speed rankings, according to reporting on Ookla data by TechTrends Kenya. But averages hide a lot. Speeds drop outside Nairobi and Mombasa, during evening peak hours, and on the cheaper data bundles a large share of your customers are actually buying. Data still isn't cheap relative to income here either: the World Bank's November 2025 Kenya Economic Update flagged that data prices remain high relative to income levels, slowing digital inclusion, which means every unnecessary megabyte your homepage loads is a small tax on someone deciding whether to bother with you at all.
This is why I push back on clients who want five rotating hero images, autoplaying video, and every font on Google Fonts loaded "just in case." A fast, plain, well-structured page beats a slow, beautiful one every time it's tested against real users. I go deeper into that exact tradeoff in why fast, simple websites still win in 2026, and it's the first thing I check on any UX review.
Good UX in Nairobi isn't about following a generic best-practices checklist copied from a US design blog. It's about matching the interface to how Kenyans actually buy. A few patterns I see change outcomes consistently:
When I audit a site that's getting decent traffic but few enquiries, the gap almost always lives in these small frictions rather than anything dramatic. I've broken down a fuller version of that diagnostic process in this piece on traffic that isn't converting into leads, worth a read if your analytics look fine but your phone still isn't ringing.
Trust signals matter more here than a lot of design guides admit. A visitor who's never bought from you before, on a small screen, with limited data to burn testing whether you're legitimate, is looking for quick reassurance: a physical Nairobi address, a real phone number, logos of businesses you've worked with, maybe a mention of how long you've been operating. I'll often move these above the fold on a Kenyan service business site even when a "cleaner" design would push them further down, because the cost of a hesitant visitor leaving to double-check you on Google is higher here than the cost of a slightly busier first screen.
Western UX research leans heavily on eye-tracking studies done on desktop screens in markets with fast, cheap broadband. Some of it transfers here, most of it needs adjusting. On a small screen, people scan in short vertical bursts rather than sweeping patterns, they read headlines and skip body copy unless something specific catches them, and they'll abandon a page that takes more than two or three scrolls to answer "what do you do and how do I reach you."
What I've found works consistently for Kenyan service and retail businesses: lead with what you do and who it's for in the first screen, follow immediately with proof (client logos, project numbers, years in business), then make contact effortless from that point onward, not just at the bottom of the page. A visitor shouldn't have to scroll to the footer to find a phone number. If they're three screens deep and interested, a floating WhatsApp or call button should already be sitting there waiting, not requiring a scroll back up to the header.
UX used to be treated as separate from SEO, one team worrying about rankings, another about "the experience." That line has mostly disappeared. Google explicitly folds page experience signals, called Core Web Vitals, into how it evaluates search results, measuring things like how fast your main content loads and how stable the page stays while it loads (nobody enjoys a button shifting right just as they're about to tap it). A slow, cluttered, hard-to-use site isn't just losing you visitors directly, it's working against the SEO work you might be paying for elsewhere. I've watched clients spend real budget on content and backlinks while their own site quietly undermined all of it with a four-second load time.
There's also a slower, less visible cost worth naming: a confusing or slow site doesn't just lose the sale in front of you, it shapes how someone talks about your business afterward. "Their site is a pain to use" travels through a WhatsApp group or a referral conversation just as easily as "their work is excellent" does, and in a market that still runs heavily on word of mouth and referrals, that's not a small thing to leave to chance.
If you want an honest read on where your own site stands, try the test I opened with: hand your phone to someone who's never seen the site, switch off the WiFi, and watch how long it takes them to find your phone number or fill in a quote form. If you're not happy with the answer, that's usually a UX conversation before it's a redesign conversation, and it's exactly the audit we run before touching a single design file. Get in touch if you'd like a second pair of eyes on it.

