Customers say it
will not open on a phone.

Why this is worth being fussy about

The overwhelming majority of people searching for local businesses are on a phone. So "awkward on mobile" is not a minor defect — it is roughly equivalent to the site being broken for most of your customers.

Worse, it raises no error and sounds no alarm. The page still opens; it is just a bit slow, the type a bit small, the buttons a bit fiddly. Customers do not complain, they simply leave. Which is why problems like this sit unnoticed for years.

Five checks you can run

Borrow a phone that is not yours (yours has your cache), turn off Wi-Fi and use mobile data, then work through these five.

1. Count how long until content appears

   From tap to readable text, count in your head. Past five seconds, most people have already left. Watch particularly for a long blank screen followed by everything appearing at once — that usually means content waits for scripts to finish, which also damages search ranking.

2. Can you read it without zooming

   Hold it normally, do not pinch, and see whether body text is directly readable. Squinting or pinching means the type is too small. Many sites fail this because it looked fine on a desktop — the designer was on a large screen throughout.

3. Hit every main button with your thumb

   Phone, address, menu, submit. Use your thumb, not a fingertip — customers hold the phone one-handed. Missing the target, or two links close enough to hit the wrong one, both count as failures.

4. Turn it sideways

   Rotate to landscape and see whether the layout breaks or a horizontal scrollbar appears. Horizontal scrolling is an obvious fault; it means something is wider than the screen.

5. Walk the path a customer walks

   Pretend to be one: find the phone number and dial it, find the address and open directions, fill in the form and actually submit it. The whole path has to work. This check finds the real problems — plenty of sites look fine page by page and break at one link in the chain.

What the fifth check finds is the most valuable. The first four are "uncomfortable to use"; the fifth is "a customer meant to contact you and could not" — which is a direct loss.

How to describe what you found

Describe what you saw; no technical terms required. Bring these and it is hard to deflect.

1. State the device and the network

   "iPhone, mobile data, not Wi-Fi." Many problems only appear on slow connections and are invisible over office Wi-Fi.

2. Give specific seconds and pages

   "The home page takes about eight seconds to show text, the contact page about five" is far more useful than "the site is slow".

3. Record your screen

   Use the phone’s built-in screen recorder and capture ten or fifteen seconds of your actual attempt. This is the most persuasive and the least ambiguous.

4. Ask which devices they tested on before launch

   Anyone naming specific models and screen widths probably tested. "Oh, we test everything" without specifics usually means they did not.

Quick fixes versus major surgery

1. Usually quick

   Type too small, buttons too small or crowded, uncompressed images making things slow, a phone number that is not tappable, horizontal scrolling. Most of these are style changes and swapped images, effective immediately.

2. Some investigation needed

   Overall slowness (is it the hosting, oversized images, or too many scripts?), forms that are awkward to complete on a phone, menus that are hard to use on a small screen. These need diagnosis before you know the root cause.

3. May mean rebuilding

   Content that only appears once scripts have run, or a site with no mobile layout at all — just the desktop version shrunk. The latter is common on older sites, and rebuilding usually beats patching. But if the old site still ranks, be careful: read rebuild the old site or improve it first.

Questions this article gets