Website Speed and Core Web Vitals for East African Mobile Visitors: A Practical Checklist

Why does speed matter for East African visitors?

Many visitors in Rwanda, Kenya, Uganda and Tanzania browse on mid-range phones over mobile data that varies from street to street. A page that feels quick on an office laptop and fibre can crawl on that kind of connection. Visitors do not wait: they leave, and they take their enquiries with them.

Speed is also part of how Google judges page experience. Its Core Web Vitals are three measurements of real-world experience, and Google publishes the targets.

What are the three Core Web Vitals and their targets?

Metric	What it measures	Good result
Largest Contentful Paint (LCP)	How quickly the main content appears	2.5 seconds or less
Interaction to Next Paint (INP)	How quickly the page reacts to taps and clicks	200 milliseconds or less
Cumulative Layout Shift (CLS)	How much the layout jumps while loading	0.1 or less

Google measures these on real visits and judges them at the 75th percentile, meaning that three out of four visits should meet the target.

How do you test your site?

• PageSpeed Insights shows a lab score on a simulated phone and, if your site has enough traffic, real-user data from Chrome. Test your home page, your main service page and a typical article.
• Search Console’s Core Web Vitals report groups your pages by status using real-user data.
• Test on a real phone over mobile data, not only on office wifi.

Remember that the lab score and real-user data answer different questions. The lab score helps you find problems. The real-user data tells you whether visitors feel them.

Fix 1: Are your images the right size and format?

Large images are the most common cause of slow pages. Resize each image to the size it is displayed at, compress it, and serve a modern format such as WebP. Give every image width and height so the layout does not jump when it loads.

One trap: lazy-loading defers an image until it is near the screen, which is good for pictures further down the page but bad for the main image at the top. Load that one immediately and mark it high priority.

Fix 2: How many third-party scripts are you loading?

Analytics, chat widgets, pixels, fonts and sliders each add network requests and processing on the phone. Keep only the ones you really use, and load the rest after the page is usable.

Fix 3: Does the main content wait for JavaScript?

Some sites send a basic page and then rebuild the top of it with JavaScript. On a slow phone, visitors may wait and then watch the headline get replaced. Where possible, send the final content in the HTML. If a script must update the page, change only what differs rather than replacing the whole block.

Fix 4: Is your layout stable?

• Set width and height on images, videos and ad slots.
• Reserve space for banners and cookie notices so they do not push content down.
• Use font-display: swap or preload your main font so text does not jump when the font arrives.

Fix 5: Is your hosting and caching set up well?

A slow server response delays everything. Use page caching, a content delivery network (CDN) with an edge close to your visitors and a current PHP version. After large changes, clear caches carefully, because a full clear can briefly slow the site while it rebuilds.

Fix 6: Do taps feel instant?

Interaction to Next Paint reflects how quickly the page responds. Break up long-running scripts, avoid heavy animations on scroll, and test menus, filters and forms on a mid-range phone, not only on a new flagship.

What are the targets?

Metric	What it measures	Good threshold
Largest Contentful Paint (LCP)	Loading performance	Within 2.5 seconds of when the page starts loading
Interaction to Next Paint (INP)	Responsiveness	200 milliseconds or less
Cumulative Layout Shift (CLS)	Visual stability	0.1 or less

Google’s web.dev: Web Vitals guidance says to assess these at the 75th percentile of page loads, segmented across mobile and desktop.

Lab data and field data are different

• Lab data comes from a simulated test, such as Lighthouse in PageSpeed Insights. It is repeatable and good for debugging, but it is not what real users experience.
• Field data comes from real visitors, shown in Search Console’s Core Web Vitals report when your site has enough traffic.
• Use lab tests to find problems and field data to confirm that real visitors benefit.

WordPress-specific fixes

• Choose a lightweight theme and avoid heavy page builders on key pages.
• Remove plugins you do not use, and watch for plugins that load scripts on every page.
• Use a caching setup suited to your host, and test after changes.
• Serve images in modern formats at the right size.
• Load fonts efficiently and limit the number of font files.
• Delay or remove third-party scripts you do not need, such as extra chat widgets or trackers.

Image rules that protect your LCP

1. Do not lazy-load the main image at the top of the page, because it is often the largest element, and loading it late hurts LCP.
2. Give every image width and height so the layout does not jump.
3. Resize images to the size they are shown, not the size of the camera original.
4. Use modern formats such as WebP or AVIF where supported.
5. Compress without visible loss, and test on a real phone.

Third-party scripts: a quick audit

Script	Ask	Action
Analytics	Do we use every tag?	Keep one, remove duplicates
Chat widgets	Does it help customers or slow the page?	Load it after interaction or remove it
Social embeds	Do we need them on key pages?	Use a link or a static image
Ad and tracking pixels	Is the campaign still running?	Remove old pixels
Fonts and icons	Can we self-host or reduce them?	Limit to what you use

A real example

In our Lens & Co by Tiara case study, a Lagos eyewear store’s home page mobile PageSpeed score rose from 74 to 99 after a rebuild. That is a lab score for one page, not a field result for every visitor, and it came with other changes, but it shows what disciplined image, script and layout work can do.

Common questions

Is speed a ranking factor?

Google says page experience is one part of what its systems consider, but great content still matters most. Speed also affects whether visitors stay and act, so it is worth fixing whatever the ranking effect.

Which page should I test first?

Your home page, your most visited service or product page and your contact or booking page. Test on mobile first.

How often should I test?

After every significant change, and at least monthly. A new plugin or banner can undo your gains.

What is a sensible order of work?

1. Measure your key pages and write down the scores.
2. Fix images and top-of-page loading first.
3. Remove unused scripts and plugins.
4. Stabilise the layout.
5. Improve hosting and caching.
6. Re-test, then repeat monthly.

How can Vatam help?

Speed work is part of our technical SEO and site speed service. We measure before and after and report honestly, including which numbers are lab scores and which come from real visitors. You can see how we report results in our Lens & Co case study.

Sources and further reading

• web.dev: Web Vitals
• PageSpeed Insights
• Google: SEO starter guide
• Google Search Central: AI features and your website