Why Websites Feel Slow in Nigeria, and How to Fix Core Web Vitals on Nigerian Networks

A site that scores well in a speed test run from Frankfurt can take six seconds to become usable in Ikeja. The gap is not mysterious. It comes from four things: distance, mobile networks, page weight and the phones people actually use. Google measures your site from real visitors, so those four things decide your Core Web Vitals and, with them, part of your ranking.

1. Distance and latency

Most Nigerian sites are hosted in Europe or the United States. Every request makes a round trip of 100 to 250 milliseconds before a single byte arrives, and a typical page makes dozens of requests. Fix: put a CDN with African edge locations in front of the site, cache everything cacheable, and cut the number of requests. A page that needs 20 files instead of 200 feels twice as fast before any other change.

2. Mobile networks

4G in Lagos is fast on a good day and 3G-like in a crowded area or in traffic. Data is also paid for by the megabyte. Fix: budget page weight. Under 1 MB for a landing page is a good target, under 500 KB is excellent. Compress images to WebP, lazy-load everything below the fold and remove scripts you do not use.

3. Page weight and third parties

The average business site we audit in Nigeria loads two to four megabytes, half of it images that were uploaded straight from a camera and a quarter of it plugins, chat widgets, fonts and trackers. Fix: one font family in two or three weights, self-hosted; one analytics tag; chat loaded after the visitor interacts; every image sized to the space it fills.

4. The phone

The mid-range Android phones most people use have a fraction of the processing power of the laptop the site was built on. Heavy JavaScript that runs instantly for the developer takes seconds for the visitor. Fix: render pages on the server, ship less JavaScript, and test on a real ₦60,000 phone with the network throttled, not only in a desktop browser.

The checklist we use

• Largest Contentful Paint under 2.5 seconds on mobile: preload the hero image, compress it, serve it from the CDN.
• Interaction to Next Paint under 200 milliseconds: less JavaScript, no long tasks on load, defer widgets.
• Cumulative Layout Shift under 0.1: set width and height on images and reserve space for embeds and fonts.
• Fewer than 30 requests and under 1 MB on the pages that matter for conversion.
• Measured with real-user data (Search Console, or first-party analytics), not just lab tests.

These fixes are cheap compared with the traffic they protect. They are also what separates a website that ranks in Nigeria from one that only ranks in the test tool.