What it costs when a website is not mobile friendly

A website not mobile friendly rarely looks broken to the person who owns it. A roofer in Preston built his site on a laptop five years ago, checked it looked fine on that laptop, and has not opened it on his own phone since. Most of his customers only ever will. A site that renders as a fixed-width desktop layout, forces someone to pinch and zoom to read a phone number, or hides the booking button off the edge of the screen is not a minor cosmetic issue on mobile. For a huge share of local business traffic, it is the entire experience of the business.

What “not mobile friendly” actually looks like

It is worth being specific, because the phrase gets used loosely. The concrete faults are usually one of a handful of things: a fixed page width that forces horizontal scrolling on a phone screen, text small enough that a visitor has to zoom in to read a sentence, tappable buttons and links packed close enough together that the wrong one gets hit, a navigation menu that never collapses into anything usable on a small screen, or a pop-up that covers the whole screen with no obvious way to close it. Individually, each of these sounds minor. Together, on a five-page site for a tradesperson or salon, they add up to a visitor giving up before they find the phone number or the booking link at all.

Why this matters more than it used to

Most searches for a local tradesperson, a hairdresser, a driving instructor or a takeaway now happen on a phone, standing in a kitchen or sitting in a car, not at a desk. Google has also indexed the mobile version of a site as the primary version for years now, which means how a site behaves on a phone affects how it is found as well as what happens once someone lands on it. A site that reads fine on a laptop but breaks down on mobile is not failing a small slice of visitors. For a lot of local businesses, it is failing the majority.

How to actually test it, not just glance at it

The most reliable test is the simplest one: open the site on an actual phone, on ordinary mobile data rather than office wifi, and try to do the thing a customer would come to do. Find the opening hours. Tap the phone number and see if it dials. Fill in the first two fields of the contact form. Try to book an appointment if there is a booking system. Resizing a browser window on a laptop tells you something, but it misses touch targets that are too small or too close together, which only becomes obvious with a thumb rather than a cursor. If you want a repeatable check to run across a list of prospects rather than one at a time, the wider process in a website audit checklist for local business sites covers where a mobile check sits alongside speed, SSL and the rest of a proper audit.

A quick manual test is enough to know whether a site has a problem. It will not tell you why, and the why is usually one of two things: the site has no responsive design at all, meaning it was built with a single fixed layout and never adapted, or it has a responsive theme that was switched on but never actually checked afterwards, so a menu or a form still misbehaves at certain screen widths. The second case is more common than people expect on older WordPress sites where a theme update changed the mobile behaviour and nobody noticed, because nobody was looking at it on a phone.

What it costs the business, concretely

The cost is not abstract. A visitor who cannot read the price list without endless zooming, or who taps the wrong menu item three times in a row, does not persevere out of loyalty to a business they have never used before. They go back to the search results and try the next one. For a business that depends on a steady trickle of new enquiries rather than a handful of big contracts, a broken mobile experience is a leak in the exact part of the funnel that brings in new customers, not existing ones who already know to call. That makes it a different kind of problem to, say, a slow-loading site, where a determined visitor might still wait it out. A site that is simply unusable on the device someone is holding does not give them that chance.

Pitching the fix without overselling it

When you raise this with a prospect, showing it does more work than describing it. Screenshotting their own site on a phone, next to a competitor's that behaves properly, makes the gap obvious in a way that the phrase “not mobile friendly” on its own does not. It is also worth being honest about scope before quoting: a site on a modern, well-supported theme might need a few days of targeted fixes to touch targets, menu behaviour and form layout. A site on an old fixed-width template, or one built years ago on a platform nobody maintains any more, usually needs a rebuild rather than a patch, and it is worth saying that plainly rather than promising a quick fix that will not hold. Either way, framing it around what the business is currently losing, real enquiries from people who never get as far as the contact form, tends to land better than framing it as a technical shortfall the owner is expected to feel bad about.

Finding these sites before you pitch them

Manually opening every local competitor's site on your phone does not scale much past a handful of prospects a week. Patchscout runs a mobile check as part of the audit it does automatically when you search a trade and a town, alongside speed, SSL and which site builder a business is running, so a genuine mobile problem shows up as a flagged finding rather than something you have to notice yourself. The three free searches on Patchscout are enough to see whether that audit turns up anything worth pitching in your own town.