Why your website needs to work on a dock
Most people find a local business on their phone, often on a weak signal. What makes a page slow on one bar, and how I build sites that load anyway.

By Drew Palframan, Ucluelet · · 2 min read
Photo: Ucluelet, my own.
The short version
- Most local searches are on a phone, and on this coast often on one bar.
- Oversized photos, unused code and extra widgets are what make a page slow.
- Your phone number and what you do should load first, before the decoration.
Most people looking for a local business are on their phone. On this coast, a lot of them are on one bar of signal: on a dock, at a trailhead, on the highway between towns. If your website takes a long time to show up there, they don’t wait. They go back and tap the next one.
I live in Ucluelet, so I know this one first hand. Drive Highway 4 over to Port Alberni and there are long stretches where the phone shows one bar or none. Stand at the end of a dock in the harbour and it’s much the same. That’s exactly where somebody pulls out their phone to find a charter, a place to eat or a mechanic, and it’s why I test every site I build as if it’s being loaded from there.
What makes a page slow on a weak signal?
- Photos that are too big. A photo straight off a phone can be several times larger than a phone screen needs. Sized properly, it looks the same and arrives far sooner.
- Code the page doesn’t use. A page that loads tools for features it never shows still makes the phone download them first.
- Too many things from too many places. Every extra font, chat widget, tracker or embedded feed is another trip across that one bar of signal.
- The important part coming last. If your phone number and what you do only appear once everything else has loaded, the visitor waits for the decoration before they get the answer.
How do I build for one bar?
I hand code every site, so a page only carries what it uses. Photos are sized for the screen they’re shown on, the words and the phone number come first, and anything that isn’t needed to read the page waits until after it’s there. I check every site with Google’s Lighthouse test, which runs a deliberately slow phone on purpose. If you want to know what those scores mean, I wrote about what the four numbers say.
If it’s slow, send me the address and I’ll tell you what’s weighing it down. How a site is hosted matters too, and that’s on my hosting page.
