Building for expensive data and unreliable networks

There is a version of web performance that is about scoring well in a testing tool. Then there is the version that matters when your customer is on mobile data they paid for, on a network that drops to 3G without warning, on a phone that is three years old.

In Nigeria the second version is the one that decides whether you get the enquiry.

Page weight is money, and your customer is paying it

A five megabyte homepage is not just slow. It is a cost the visitor absorbs directly out of a data bundle. Someone who has learned that a particular site eats their data does not come back, and they will not tell you why.

This reframes the usual conversation. The autoplaying background video is not merely a performance choice. It is you spending your customer's money to show them something they did not ask for.

A well built page for a service business should land comfortably under a megabyte on first load. Most sites we look at are three to eight times that, and almost none of the excess is doing useful work.

Where the weight actually is

Images, nearly always. A hero photograph exported straight from a camera or a stock site at 4000 pixels wide, displayed at 800. Resize to roughly what is shown, serve WebP, and set width and height so the layout does not jump while it loads. This alone often halves total page weight.

Fonts. Four weights of two families is eight files before any text appears. Two weights of one family covers almost every design honestly. Subset to the characters you use and preload the one that renders first.

Scripts you forgot about. Chat widgets, analytics, a heatmap tool from a campaign that ended last year, three social pixels. Each is a download and an execution cost. Audit them and be ruthless.

Video. An autoplaying background video is the single most expensive thing you can put on a homepage. If you need one, use a poster image and let people press play.

Design for the connection dropping

Networks here do not fail cleanly. They degrade, stall, and recover. A site that assumes a stable connection behaves badly under those conditions in ways that are avoidable.

• Show text before images. If the layout depends on an image loading, a slow image means a blank screen. If the text renders first, someone can start reading while the rest arrives.
• Do not block on third parties. A script from an external server that fails to load should not prevent your page appearing. Load them asynchronously so a slow third party stays their problem rather than yours.
• Make forms survive a failure. Someone filling in an enquiry when the connection drops should not lose what they typed. Keep the values, show a clear error, let them retry.
• Say when something failed. A button that appears to do nothing is worse than one that says the connection is unavailable. Silence makes people tap repeatedly and then leave.

Test the way your customers browse

Testing on office wifi on a laptop tells you almost nothing. Two checks are worth building into your routine.

Open your browser's developer tools, throttle the network to slow 3G, and load your homepage. Time how long until you can read something and until you can tap the phone number. If that is more than a few seconds, you have found real work.

Then open it on an actual mid range phone on mobile data. Emulators are useful and they are not the same as a real device with a real network and a real battery.

What this buys you beyond speed

A lighter site ranks better, because page experience is a genuine ranking factor and mobile performance is what gets measured. It converts better, because fewer people abandon while waiting. And it costs less to host, because you are shipping fewer bytes.

Mostly though, it signals something. A site that loads instantly on a bad connection reads as a business that knows what it is doing. That impression is formed in the first two seconds, long before anyone reads a word about your services.

We go deeper on measurement in performance and Core Web Vitals.

See how we work with Nigerian businesses, or send us your URL and we will tell you what it weighs.