A slow website quietly leaks revenue.
A slow website loses visitors, rankings, and ad money. What actually makes sites slow, how to measure it properly, when optimisation is enough, and when to rebuild.
Speed is not a technical vanity metric. Every extra second of load time bounces a measurable share of visitors, drags Google rankings through Core Web Vitals, and inflates the cost of every ad click you send to the site. In East Africa the stakes are higher still: your customers are mostly on mid-range Android phones over 3G/4G connections that punish heavy pages mercilessly.
The good news: slowness always has specific causes, and they are diagnosable. Here is how we approach it.
Test money pages on mobile settings — office WiFi lies
Images cause most slowness; scripts and hosting come next
Optimisation halves load times cheaply — but structural bloat needs a rebuild
Target seconds and conversions, not perfect scores
Measure like your customers, not like your office WiFi
A site that feels fine on office fibre can be unusable on mobile data. Test with PageSpeed Insights or Lighthouse on the mobile profile, and test your real money pages — service pages and landing pages — not just the homepage. Pay attention to three numbers: LCP (when the main content appears — should be under 2.5s), INP (how fast the page responds to taps), and CLS (whether the layout jumps around while loading).
These three are Google's Core Web Vitals, and they are a ranking input. But before rankings, they are a bounce-rate input — visitors don't wait to find out how good your content is.
The usual suspects, in order of likelihood
In the sites we audit, the same culprits appear again and again. Images top the list — full-resolution photos uploaded straight from a camera or phone, served at megabytes each when 100KB would look identical. Then script bloat: page builders, sliders, chat widgets, multiple analytics tags, and plugin JavaScript loading on every page whether used or not. Then hosting — $3/month shared servers that take a full second to even begin responding. Then render-blocking themes and fonts.
- Unoptimised images (the cause of most slow sites — fix with compression, modern formats, lazy loading)
- Plugin and page-builder JavaScript loading sitewide
- Cheap shared hosting with slow server response times
- No caching or CDN, so every visitor hits the origin server
- Heavy themes, custom fonts, and third-party embeds (maps, videos, chat)
Optimise or rebuild? An honest threshold
If the platform is fundamentally sound, optimisation — compressing images, pruning plugins, adding caching and a CDN, upgrading hosting — can often cut load times in half within days. That is the right first move, and any competent developer can do it.
But there is a floor. A page-builder site hauling 4MB of JavaScript cannot be optimised into a fast site; the weight is structural. If optimisation has been attempted and pages still take 4+ seconds on mobile, the honest answer is usually a rebuild on a lighter architecture — which is also the moment to fix conversion, content structure, and SEO in the same project rather than paying for them separately later.
Speed as a business case, not a score
Chasing a 100/100 score is a waste of money; the last ten points cost more than they return. Chasing sub-3-second mobile loads on your revenue pages is a business investment: lower bounce, higher ad Quality Scores (cheaper clicks), better rankings, and a first impression of competence. Set the target in seconds and conversions, not in scores, and re-test after every major site change so the gains don't silently erode.
Frequently asked questions
How fast should my website load in East Africa?
Aim for main content visible (LCP) within 2.5–3 seconds on a mobile connection. Your analytics will show most visitors on mobile devices, and networks in Uganda, Kenya, and Tanzania make every kilobyte count — a page that is 'fine' in Europe can take 8+ seconds locally if it's heavy.
Does website speed really affect Google rankings?
Yes — Core Web Vitals are a confirmed ranking input, though content relevance still matters more. The bigger effect is indirect: slow pages bounce visitors, and pages that bounce hard struggle to rank and convert regardless of the algorithm. Speed also directly lowers Google Ads costs through Quality Score.
Can my WordPress site be made fast without rebuilding?
Usually, yes — image optimisation, a caching plugin, a CDN, better hosting, and removing unused plugins routinely cut load times by half or more. The exception is sites built on heavy page builders with dozens of active plugins; past a point, the weight is structural and a rebuild is more economical than fighting it.
Why is my website fast on my computer but slow on phones?
Desktop machines on WiFi hide problems: they have fast processors to chew through JavaScript and bandwidth to swallow big images. Mid-range phones on mobile data have neither. Since most of your visitors are on those phones, the mobile experience is the real one — test there first.