This week somebody tried to read this website on her phone. She could not do it. The text on some of our fanciest sections was small enough to need a magnifying glass, and she said so.
She was right. We measured it. Some labels were eight pixels tall. Eight. On a site that tells other businesses how to catch customers.
So we fixed it. Four hundred and seventy-one text sizes raised in one pass, bigger buttons, brighter contrast, tested at phone width before it shipped. And then I wrote this, because if it happened to us, it is happening to you.
The phone is not the small version. It is the version.
Pull up your analytics and look at the device split. For most local businesses, most visitors are on phones. The desktop site you approved on a big monitor in perfect lighting is the minority experience.
Which means every decision you made while leaning into a 27-inch screen gets judged by a customer squinting at six inches of glass in a parking lot.
The two-minute test
Do not audit your site. Hand your phone to someone and watch.
- Can they read the body text without pinching?
- Can they tell what you do from the first screen?
- Can they find the price, or at least the path to it?
- Can they tap the phone number with a thumb, first try?
- Can they finish your form in under a minute?
Every failure on that list is quiet. No error message fires when a 62-year-old customer with reading glasses gives up on your quote form. The visit just ends, and your analytics files it under bounce.
What we actually changed, so you can steal the list
- A floor under the text. Body text at sixteen pixels minimum. Labels close behind. If a word matters enough to print, it matters enough to read.
- Buttons built for thumbs. Tap targets sized so a working hand hits them the first time, with space between them so it does not hit two.
- Contrast that survives daylight. Light text on dark backgrounds looks sharp in a design review and vanishes on a phone in the sun. We brightened the dim text and lifted the dark-on-dark sections.
- One action per screen. A phone screen is small. It gets one job: call, start, read. Not six competing buttons.
- Shorter forms. Every extra field on a phone keyboard costs more than the same field on a desktop. Count yours.
None of that is decoration. Every line of it exists to stop a customer from leaving mid-sentence.
Put a price on it
The leak is measurable, and your own numbers are sitting in your analytics.
Price your mobile leak
Most of your visitors are on a phone. If the site works worse there than on a desktop, that gap has a dollar figure. Work out yours.
Your numbers
What that means
Device audiences may behave differently. Equal conversion is a comparison assumption, not proof of a mobile defect. Test readability, contact buttons, and forms, then measure actual results.
Runs in your browser. Nothing you type is sent anywhere.
This is an estimate
This tool returns an estimate based on the numbers you entered. Your real result depends on your own costs, rates and conditions. Check it against your own records before you make a decision with it.
How to run it, step by step
- 1Enter your monthly visitors. From your analytics. If you have none, use a guess and treat the result as a floor. Then go get analytics, because flying blind is its own leak.
- 2Set the share on phones. Your analytics knows this too. For most local businesses it is well past half, which is why the phone version of your site is the real version.
- 3Enter both conversion rates. What share of desktop visitors contact you, and what share of phone visitors do. The gap between those two numbers is the leak this article is about.
- 4Add what a customer is worth. Average value and your close rate, so the leak comes out in dollars instead of percentages.
How to read what it gives you
- The yearly figure is what the phone gap costs at your traffic and prices. It is the budget for fixing it, computed from your own numbers.
- If mobile matched desktop is the line to look at twice. That is not a fantasy number. It is what readable text, tappable buttons, and a short form buy back.
- A small leak means your site passes the phone test. Congratulations, go check your follow-up instead.
The tool is free, it does not expire, and you can put it on your own website if you want it there. Nothing on this page is locked.
Not ready to talk? Browse the rest of the free tools
The part that stings
The person who cannot read your site does not know your labels are eight pixels. She does not know what a viewport is. She knows your business felt hard to deal with and the next one on the list felt easy.
The record does not care how the site looked on your monitor. It cares what happened on her phone.
We took the correction and shipped the fix the same day. Your move is the same one: run the test, price the leak, fix the floor. And if the site fails deeper than type size, the free five-page build exists for exactly that.
Questions people actually ask
What font size should a website use on mobile?
Sixteen pixels is the floor for body text, and that is not a style opinion. It is roughly the size phone browsers consider readable without zooming, and it is the size Apple and Google use as the baseline in their own guidance. Labels and buttons should not be far behind it.
How do I test my website on a phone properly?
Hand your phone to someone over fifty, in daylight, and ask them to find your price and contact you. Watch silently. The pinching, squinting, and mis-taps you see in the next two minutes are what every customer experiences and never mentions. They just leave.
Does Google punish sites that are hard to read on phones?
Google indexes the mobile version of your site as the primary one and its own documentation says readable text and usable tap targets matter for the mobile experience. But the honest reason to fix it is closer to home: the customer who cannot read your page does not file a complaint. They call your competitor.
Do I need a whole new website to fix this?
Not always. Sometimes it is raising the type, spacing the buttons, and shortening the form on the site you have. It becomes a rebuild when the site also fails the deeper tests: no clear next step, no lead capture, no follow-up behind it. The phone test tells you where to start, not always where to stop.