Why Site Speed Matters Even More in Kenya, and How to Fix It in 2026

Almost everyone who visits a Kenyan business website does it on a phone, and a lot of them are paying for every megabyte. A page that feels fine on office Wi-Fi can take ten seconds on a weak signal, and most people will not wait that long. Speed is not a technical nicety here; it is the difference between a customer and a closed tab.

Why Kenya is different

Communications Authority of Kenya statistics consistently show that almost all internet subscriptions in the country are mobile. Coverage in Nairobi is good, but your visitors are on shared cell towers at rush hour, on bundles that are running low, and on budget phones with slower processors. Heavy pages cost them money and patience twice: once to download, and again while the phone struggles to run all the JavaScript.

What Google measures: Core Web Vitals

Google uses three measurements, taken from real Chrome users, to judge how a page feels:

• LCP (Largest Contentful Paint) — how long until the main content shows. Good is 2.5 seconds or less.
• INP (Interaction to Next Paint) — how quickly the page responds when someone taps a button or opens a menu. Good is 200 milliseconds or less. INP replaced the older FID measurement in March 2024, and it is stricter: it catches pages that look loaded but freeze when touched.
• CLS (Cumulative Layout Shift) — how much things jump around while loading. Good is 0.1 or less.

A page passes when at least 75% of real visits meet all three. These are a small ranking signal, but the bigger reason to care is that slow, jumpy pages lose customers.

How to test your site

1. Open PageSpeed Insights and enter your address. The top section ("Discover what your real users are experiencing") is real-visitor data, if your site has enough traffic. The lower score is a lab test on a simulated slow phone.
2. Test your most important pages, not only the home page: your services, prices and contact pages.
3. Look at the list of opportunities. It tells you exactly which images, scripts and fonts are costing you the most.

The fixes that matter most

Images (usually the biggest win)

• Resize photos to the size they are shown at. A 4,000-pixel photo from a phone, shown at 800 pixels, is mostly wasted data.
• Use modern formats such as WebP or AVIF, which are usually much smaller than JPEG at the same quality.
• Add loading="lazy" to images further down the page, but not to the main image at the top, which should load first.
• Always set width and height on images so the page doesn't jump when they arrive. That fixes most CLS problems.

JavaScript (the usual cause of poor INP)

• Remove scripts you don't need: old chat widgets, unused sliders, several tracking tools doing the same job.
• Load the rest with defer so it doesn't block the page from showing.
• Be careful with page builders and heavy themes. They often load large amounts of JavaScript on every page whether it is used or not.

Fonts

• Use one or two font families, and only the weights you really use.
• Add font-display: swap so text shows immediately in a fallback font.
• For the fastest result, host the font files on your own server instead of loading them from a third party.

Hosting and caching

• Choose hosting with good response times to Kenya, and turn on compression (gzip or Brotli).
• Let browsers cache images, CSS and JavaScript so repeat visits are almost instant.
• A CDN such as Cloudflare's free plan can help, especially if your server is far away.

A realistic target

A small business site should aim for all three Core Web Vitals in the green on mobile, and a total page weight of around 1 MB or less for the first screen. It is very achievable without fancy technology: sensible images, little JavaScript, and a clear page.