colb.dev

Writing · Performance

Why your site is slow on a phone but fine on your laptop

You are testing it in the best possible conditions. Your customers are not.

When you check your own site you are sitting near your router, on wifi, on a machine with a fast processor, loading a page your browser has already cached. That is the best case, and it is not what your customers get.

They are on cellular, often on a phone that is three or four years old, usually somewhere with one or two bars, and they have never loaded your site before. Nothing is cached. Everything downloads.

Test it honestly

Turn wifi off on your phone. Open a private or incognito tab so nothing is cached. Load your site. That is the number that matters, and most people have never seen it.

What is usually wrong

Photographs at full camera size. This is the big one and it is nearly universal. A photo straight off a phone is around 4000 pixels wide and several megabytes. Displayed in a 700 pixel slot it looks identical to a properly sized copy, so nobody notices. The visitor downloads the whole thing anyway. One page with six of these on it can be 20 megabytes. Resized and converted to WebP, the same page can be under one.

Fonts loading in a chain. The page downloads a stylesheet, which asks for a font file, which the browser then waits on before it will paint text. On a slow connection that is several seconds of blank screen. Self-hosting the font and preloading it removes an entire round trip.

Plugins and scripts nobody uses anymore. The chat widget you turned off, the popup builder from a campaign two years ago, three analytics tools when one would do. Each one is a separate download before the page is usable, and they do not remove themselves.

A slider on the home page. A slider loads every slide, not the one on screen, plus the library that moves them. Most visitors see only the first slide and scroll past.

Why it is worth fixing

Someone on a phone who taps your site from a Google result is deciding whether you are worth the wait. If the page is blank for five seconds they go back and tap the next business. You never see it happen, and it does not show up in your analytics as anything other than a visit that bounced.

The repair is usually not a rebuild. Images, fonts and dead scripts cover most of it, and all three can be fixed on the site you already have.

Related

Start a project

Tell me what you need built

A few sentences is enough: what the site or tool has to do, and roughly when you need it. You'll get a reply from me, the person who writes the code, usually the same business day, with a couple of questions and a rough range.

What do you need help with?

So I can reply. Nothing else goes to it.

The business, the problem, and anything that already exists: a current site, a deadline, a budget range.