Why Your Website Breaks on Phones and What It Costs You
Most people looking up a local business are doing it on a phone - standing in a driveway, sitting in a truck, waiting for a table. If your site makes them pinch to read, scroll sideways to see the whole page, or hunt for a phone number they cannot tap, a good share of them leave and call the next business on the list. Here is what actually breaks on small screens, how to test your own site in about a minute, and what to fix first.
Test your own site in a minute
Open your site on your own phone, in a normal browser - not through a preview inside your website builder. Builders show you a tidy simulated phone that hides real problems. Then do these four things and watch what the page does.
The one-minute phone test
- Swipe left and right.The page should not move sideways at all. If it does, something on it is wider than the screen - usually a table, a fixed-width image, or a long unbroken word like an email address.
- Read a paragraph without zooming.Body text should be comfortable at arm's length. If you are pinching, the text is set too small or the whole page is being scaled down to fit.
- Tap the phone number and the address.The number should dial and the address should open maps. If nothing happens, they are plain text, and you are asking a customer to memorise digits and retype them.
- Count to three while it loads.Do this on cell data, not your own wifi. Most slow pages on small business sites are slow for one reason: full-size camera photos uploaded straight from a phone.
What is actually breaking
Nearly every mobile fault I find on a local business site is one of four things.
| What you see | Usual cause | What it costs |
|---|---|---|
| Sideways scroll | A fixed-width table, image or embedded map that never got a mobile rule | The layout looks careless and part of your content sits off-screen |
| Text too small | A desktop layout scaled down to fit rather than reflowed | People give up before they reach what you do or where you are |
| Taps that miss | Links packed too close together, or targets smaller than a fingertip | The tap lands on the wrong thing and the visitor blames your business |
| Slow, heavy pages | Photos served at full camera resolution and shrunk in the browser | Visitors on cell data leave before the page finishes painting |
Scroll the table sideways for the rest of each row.
The cost is quiet, which is why it goes unfixed
A broken desktop site gets complaints. A broken phone site gets silence. Nobody emails to say the menu would not open on their iPhone - they order somewhere else. That is what makes this worth checking while the phone is still ringing. The enquiries you never hear about show up nowhere, so a poor mobile site can be losing you work every week without ever looking like a problem.
Patch it or rebuild it
Some of this is a genuinely small fix. A width rule on images, a viewport tag that was never added, turning a phone number into a tappable link, running photos through a compressor. That is an afternoon of work, worth doing yourself if you are comfortable in your editor. On a mainstream builder with a modern theme, that is often all it takes, and I would rather say so than sell you something you do not need.
It is a different conversation when the layout was never designed for a small screen: a site built before responsive design was standard, or a template stretched so far out of shape that every page needs its own patch. Then you are maintaining a workaround forever, and a rebuild done mobile-first is less work than the patching. The honest test is simple. Fix the four faults above, and if the site still feels like a desktop page squeezed onto a phone, the structure is the problem.
Questions I get asked
My builder says my site is already responsive. Is it?
Responsive means the layout reflows, which most modern templates do. It does not mean anyone checked yours. Custom sections, embedded menus, PDFs, tables and third-party widgets are where responsive templates break - those pieces are not part of the template.
Do I need a separate mobile site?
No. Separate m-dot sites were an early-2010s workaround and they cause more trouble than they solve: two sets of content to keep in step and split search signals. One site that adapts is the standard now.
How do I test without a drawer full of phones?
Chrome's device mode on a desktop catches layout faults, and Google's PageSpeed Insights gives you a real mobile score naming the files that slow you down. Use your own phone on cell data for the last check.
If you would rather see the fix than read about it, I build a working demo on your own content before you pay anything - open it on your phone and judge it there. Tell me what your site is doing wrong.