Most Ugandan businesses we talk to know their website is slow. What they don't know is why, or where to start. 'Make it faster' is too vague to action. Speed is the result of a chain of decisions: server setup, rendering strategy, images, scripts, and hosting. Here's where the time actually goes and what to fix first.
Why speed matters more in Uganda than in Europe
Your customers are not loading your website on fibre from a Kampala office. Many are on 3G or patchy 4G connections on mid-range Android phones. What loads in 1.5 seconds on your office WiFi might take 6 seconds for someone in Ntinda or Entebbe.
The numbers that matter:
- 53% of mobile users abandon a page that takes more than 3 seconds to load
- Every second of additional load time reduces conversions by roughly 7 to 10%
- Google factors speed into rankings, so a slow site costs you both visitors and positions
Building fast for Uganda means testing on real mobile conditions, not just your office connection.
1. Rendering strategy: where the work happens
The single biggest decision affecting your site's speed is where the HTML is generated: on the server, in the browser, or a mix of both.
- Server-side rendering and static generation are the fastest option for most websites. The HTML is ready before the browser asks for it. This is what Next.js does well.
- Client-side rendering, where the browser has to download JavaScript and then build the page, is slow on lower-spec phones. It's fine for dashboards behind a login, not for public-facing marketing pages.
If your homepage loads a large JavaScript bundle before showing any content, your rendering strategy is wrong.
2. Images: usually the single biggest problem
Images account for more of your page weight than any other asset type on most content sites. The defaults are almost always wrong.
What to fix:
- Use modern formats: WebP instead of JPG or PNG saves 25 to 35% file size with no visible quality difference
- Size images correctly: don't load a 2000px wide image for a 400px container. Serve the right size for the screen.
- Lazy-load below-the-fold images: only images the user actually sees should load immediately
- Compress everything: a 4MB hero image is a choice, not a necessity. Most hero images should be under 200KB.
If you do nothing else, run your site images through Squoosh (squoosh.app) and re-upload them. You'll likely cut your page weight in half.
3. Hosting and server location
Where your server is physically located affects how long every request takes. Most affordable shared hosting is in the US or Europe. A user in Kampala making a request to a server in Frankfurt is waiting for data to travel across thousands of kilometres.
What to look for:
- A CDN (Content Delivery Network): services like Cloudflare cache your site's assets closer to your visitors, cutting load times significantly across Africa
- Modern hosting with edge locations: platforms like Vercel, Netlify, and Cloudflare Pages serve Uganda faster than shared hosting in the US
- Fast Time to First Byte (TTFB): your server should respond in under 600ms. If it's over 1 second, fix hosting before anything else.
We host most of our client sites on Vercel or VPS providers with Cloudflare in front. The performance difference versus shared cPanel hosting is not subtle.
4. Third-party scripts
Every plugin, widget, and tracking script you add costs performance. A live chat widget, a Facebook Pixel, a Google Tag Manager container with 15 tags: each adds parse time, network requests, and main-thread work.
What to do:
- Audit quarterly: list every third-party script loading on your site and ask what each one is doing
- Defer non-critical scripts: scripts that don't affect the initial render should load after the page is interactive
- Cut the ones you don't need: dead pixels and unused plugins accumulate. If you're not using it, remove it.
5. How to measure what you've got
Don't guess. Measure first, then fix in order of impact.
- PageSpeed Insights (pagespeed.web.dev): run your homepage and your most important page on mobile view and read the diagnostics
- GTmetrix: gives a waterfall view of every request, useful for spotting which file is slowest
- WebPageTest.org: lets you test from different locations including African nodes
- Google Search Console > Core Web Vitals: shows your real-world scores from actual users
Fix the issues with the largest potential savings first. Usually that's images, then rendering strategy, then hosting.
If you want us to audit your site and tell you exactly what's slowing it down, get in touch. We'll run a proper diagnostic and give you a prioritised fix list.
