Mobile Website Mistakes That Cost Local Businesses

Your customers are on a phone, and your site was designed on a laptop.

The Gap Between How It Is Built And How It Is Used

Local intent searches skew heavily to mobile. Someone looking for a plumber, a dentist, a barber or a garage is usually on a phone, often outdoors, often in a hurry, frequently on a patchy connection.

That website was almost certainly designed on a large monitor, on fast internet, by someone sitting down with time to look around. The two experiences have little in common, and the gap is where the lost calls live.

None of what follows is exotic. These are the failures we find on most local sites, in roughly the order they cost money.

The Phone Number Is Not Tappable

This is the most expensive mistake on the list and the cheapest to fix. If your number is set as an image, or as plain text without a tel link, a mobile visitor has to memorise it, leave your site, open the dialler and type it in. A meaningful share of them will not.

The fix is a link using the tel protocol wrapped around the number. Format the number for humans, keep the digits in the link clean with the country code. Then put it somewhere thumb reachable, which on a phone means the top of the screen or a fixed bar at the bottom; the footer is too far away.

While you are there, make sure a tap on that number registers as a conversion in your analytics. Calls are the main outcome for most brick and mortar businesses and most of them are not tracked at all, which means every report about what is working is missing the largest column.

Tap Targets Are Too Small And Too Close

A finger is not a mouse pointer. Anything a visitor needs to tap wants to be around 44px on its shortest side with real space around it. Menu items stacked at 30px with no gap produce mis-taps, and a mis-tap on a phone feels like the site is broken rather than like the user missed.

The usual offenders are footer link lists, closely stacked navigation items, and the close button on a popup. That last one matters more than it sounds. If someone cannot dismiss your newsletter overlay in one try, they close the tab instead.

Images Are Doing The Damage

Most slow local sites are slow for one reason. Someone uploaded photos straight off a phone or a camera, at full resolution, and the page is now pulling several megabytes of image to render a header.

Three fixes cover almost all of it. Resize images to the largest size they are displayed at. Serve them in a modern format such as WebP. Add lazy loading so images below the fold do not block the first view.

That is usually the difference between a four second load and a one second load, and it costs nothing but an afternoon. It also helps rankings, because page experience is a real if modest ranking input, and because a fast page gets crawled more thoroughly.

Text That Cannot Be Read And Layouts That Move

Body text below 16px forces pinch zooming. Once someone has to zoom, horizontal scrolling starts, and horizontal scrolling on a phone is where visitors give up.

The other half of this is layout shift. Ads, fonts and images that load late push the content down after the page appears. The visitor goes to tap a link, the page jumps, and they tap something else. Reserve space for images and embeds with explicit dimensions and this stops.

Both of these are measured by Google as part of page experience, so the fix helps twice. But the real reason to do it is that a page which moves under someone's thumb reads as untrustworthy, and trust is most of what a local business is selling.

Forms Built For A Keyboard

A form that is merely tedious on a desktop becomes hostile on a phone. Cut it to the fields you need to reply, which for most local businesses is a name, one contact method and a short description of the job.

Set the input types correctly so the phone shows the right keyboard. An email field should bring up the keyboard with the at symbol. A phone field should bring up the number pad. This is a one word change per field and it noticeably improves completion.

Avoid dropdowns with long lists, avoid date pickers where a text field would do, and never make someone re-enter everything because one validation failed. Preserve what they typed.

How To Test This Properly

Do not test on your own phone on your own wifi. You know the site, you know where everything is, and your connection is good, so you will pass every time.

Use a real device on mobile data, ideally throttled. Chrome DevTools has a network throttle that simulates a slower connection reasonably well. Then hand your phone to someone who has never seen the site and ask them to book an appointment while you watch and say nothing. Ten minutes of that will tell you more than any audit tool.

The pattern worth watching for is hesitation. Anywhere they pause, squint or scroll back up is a place the page failed to answer a question it should have answered already.

At askotter this is the loop the site runs on its own after launch. It reads how real visitors move through the pages, finds where they are dropping out, and writes the fix for a person to approve. From $99/mo if you drive it yourself, $600/mo managed.