Before a Gambian customer ever walks into your shop, calls your office, or messages you on WhatsApp, there's a good chance they meet your business on a website first — on a phone, over mobile data, often on a modest handset with a smaller data bundle than you'd assume. If that page takes too long to appear, they don't wait to judge your product or your prices. They leave before they see either.
That's the part of "having a website" that gets skipped over most often. A business gets a site built, checks that it looks right, and moves on. Whether it actually loads quickly on a real phone, on real Gambian mobile data, rarely gets checked at all.
What "slow" actually means, and why Google cares
Google doesn't leave page speed to guesswork. It measures it through a set of metrics called Core Web Vitals, and publishes exactly what "fast enough" looks like:
- Largest Contentful Paint (LCP) — how long it takes for the main content of a page to become visible. Google's guidance: aim for this to happen within 2.5 seconds.
- Interaction to Next Paint (INP) — how quickly the page responds once a visitor actually taps or clicks something. Google's target: under 200 milliseconds.
- Cumulative Layout Shift (CLS) — whether elements jump around as the page finishes loading (a button that moves right as someone tries to tap it). Google's target: a score under 0.1.
These aren't arbitrary numbers. They're Google's own published thresholds for what counts as a good experience — and they're measured separately for mobile and desktop, because mobile performance is consistently the harder bar to clear.
The stakes here aren't just about search rankings, either, though Core Web Vitals do factor into how Google evaluates a page. They're about whether a real visitor waits. Google's own research into mobile page speed — published as "The Need for Mobile Speed" — found that a majority of mobile visitors abandon a page that takes more than a few seconds to load. Whatever the exact figure on any given day, the pattern behind it hasn't changed: the longer a mobile page takes to appear, the more people leave before they see it.
Why this matters more in The Gambia, not less
It's tempting to treat page speed as a concern for large e-commerce sites with global traffic, not a local business in Banjul or Serekunda. The opposite is closer to the truth.
Mobile data in The Gambia costs real money, and until recently it cost even more. The Public Utilities Regulatory Authority (PURA) set a new price ceiling of D75 per gigabyte, effective 1 January 2026 — and reporting from Askanwi found that Africell and QCell were still charging D130 per gigabyte after that deadline had passed, only cutting prices to D65 once the overcharging was publicly exposed. Gamcel reportedly remained above the ceiling. Whichever operator a customer uses, loading a bloated, image-heavy homepage still consumes a visible slice of a data bundle that customer paid real dalasis for. A heavy website doesn't just cost you their patience — it costs them money, every single visit.
It's also worth remembering who's on the other end of that connection. GSMA — the global industry body for mobile network operators — has reported that handset affordability remains the single biggest barrier to mobile internet use across Africa, with an entry-level internet-enabled phone costing the poorest fifth of people in Sub-Saharan Africa the equivalent of the majority of a month's income. That translates directly into what's actually in Gambian pockets: a large share of your mobile visitors are on modest, older, or budget Android devices, not the latest flagship phone. A page built and tested only on a fast office laptop with fibre internet can look completely different — and load far more slowly — on the phone your actual customer is using.
Put together: Gambian visitors are disproportionately mobile-first, price-sensitive about data, and often on less powerful hardware. That's exactly the profile Core Web Vitals was designed to protect, and exactly the profile a slow, heavy website punishes hardest.
What actually makes a website slow
In practice, a handful of common culprits account for most of the problem:
- Oversized images. A photo taken straight from a phone camera or a stock library, uploaded without resizing or compressing, can be several megabytes — for a single image on a single page. This is, by far, the most common cause of a slow site.
- Heavy homepage sliders and autoplay video. A rotating image carousel or a background video looks impressive on a laptop and is often the slowest, heaviest element on the entire page for a mobile visitor.
- Too many third-party scripts. Chat widgets, multiple analytics tools, social media embeds, and ad scripts each add their own loading time, and they often load in a way that delays everything else on the page.
- Unoptimized website builders and themes. Some page-builder templates load large amounts of design code the visitor never actually uses, just to render a simple page.
- No compression or caching configured on the hosting side, so the same files get sent in full on every single visit instead of being served efficiently.
None of these are exotic problems. They're also, almost all of them, fixable without rebuilding a site from scratch.
What to actually do about it
- Test it first. Run your website through Google's free PageSpeed Insights tool and look specifically at the mobile score, not just desktop — they're frequently very different.
- Resize and compress every image before it goes on the site. A product photo rarely needs to be wider than the space it displays in, and modern image formats (like WebP) hold visual quality at a fraction of the file size of an unoptimized JPEG or PNG.
- Cut anything decorative that isn't earning its cost. A single well-chosen hero image usually serves a customer better than an auto-rotating slider they have to wait for and never asked for.
- Audit third-party embeds. Keep the chat widget or booking tool that actually drives business, and remove the analytics tool nobody looks at or the social widget nobody clicks.
- Choose hosting and a platform built for performance, with compression and caching enabled, rather than the cheapest available option with no attention paid to how it's configured.
- Re-test after every change, on an actual phone over mobile data where possible, not just in a browser on a fast office connection.
A fast website isn't a vanity metric or a developer's pet concern. For a Gambian business, it's often the difference between a customer seeing what you offer and a customer never finding out — because they were gone before the page ever appeared.
