Website Speed Optimisation for Kenyan Businesses

A fast website is not a score chased once before launch. It is an experience that changes as teams add images, tracking scripts, plugins, content and third-party features.

Customers use different phones, browsers and networks, so one test on an office laptop cannot represent everyone. Good performance work combines controlled tests with field data, then focuses on the pages and customer journeys that matter most.

Understand the Core Web Vitals

Google’s current Core Web Vitals measure loading, responsiveness and visual stability:

• Largest Contentful Paint (LCP): when the main visible content finishes rendering. Google recommends 2.5 seconds or less for a good experience.
• Interaction to Next Paint (INP): how quickly the page responds to user interaction. Google recommends less than 200 milliseconds.
• Cumulative Layout Shift (CLS): how much content unexpectedly moves while loading. Google recommends a score below 0.1.

These thresholds are assessed at the 75th percentile in Google’s guidance. Core Web Vitals are useful, but they are not the whole experience: a customer also needs accurate content, working forms and a clear path to the next action.

Measure before changing the site

Lab tests

Tools such as Lighthouse and PageSpeed Insights can reproduce conditions and identify likely causes. Lab results are useful for debugging and comparing changes, but they remain simulations.

Field data

Real-user data reflects actual devices, connections and behaviour over time. Search Console’s Core Web Vitals report can help identify groups of pages with poor field performance when enough data is available. Google recommends using both lab and field measurement because they answer different questions.

Common causes of slow pages

• Large, poorly sized hero images or product photos
• Too many font files, weights or external stylesheets
• Heavy JavaScript that blocks interaction
• Plugins or widgets loaded on pages that do not need them
• Slow server response or uncached database work
• Third-party advertising, chat or analytics scripts
• Layout shifts caused by images and embeds without reserved dimensions

A practical improvement sequence

1. Record a baseline for representative mobile and desktop pages.
2. Identify whether the main problem is server response, media, code execution or layout.
3. Fix the largest bottleneck first instead of making many tiny changes.
4. Test that the improvement did not break accessibility, analytics or functionality.
5. Deploy, observe field data and keep monitoring for regression.

Avoid speed claims without evidence

There is no honest promise that one optimisation will produce a specific ranking or conversion result for every business. Google says page experience is considered by ranking systems, while also making clear that good Core Web Vitals do not guarantee top rankings. Treat speed as a measurable user and operational quality—not a shortcut to guaranteed SEO results.

Sources: Google Search Central: Core Web Vitals and web.dev: user-centric performance measurement.