Most visitors are on a phone. Is your site ready?

Pull up your website on your phone right now. Not on Wi-Fi in your living room. Do it the way a stranger would: out in the parking lot, one bar of signal, thumb on glass, ten seconds of patience before they're gone. What do you see?

If the answer involves pinching to zoom, text that runs off the edge, or a menu that requires surgeon-level precision, you have a real problem. One that is costing you customers right now, quietly, every single day.

The numbers are not close

Around 63% of web traffic in the US comes from phones. For local service businesses, that number is often closer to 74%. Someone's pipe burst at 11pm and they're Googling you from the couch. A bride-to-be is comparing photographers between back-to-back meetings. A homeowner is standing in your competitor's parking lot, second-guessing herself, looking you up.

Every one of those people is on a phone. And most small business websites were built to look good on a laptop, as a desktop demo in some agency's conference room. That is the gap between the site you think you have and the one your customers are actually seeing.

A slow or broken mobile experience doesn't just annoy people. It sends a signal. If your site is hard to use, the visitor reads your business as disorganized. They bounce. They call someone else. You never even knew they were there. A slow-loading site does the same damage, and the two problems almost always travel together.

What a bad phone experience actually feels like

Here's what happens when someone lands on a site that was never built for mobile. The page loads. Sort of. The font is 9px because it was set in pixels on a desktop layout and nobody adjusted it. The hero image is enormous and takes four seconds to paint in. The navigation is a row of six links crammed into a horizontal bar, and tapping any of them is a coin flip because they sit 12px apart.

The phone number is an image, not a real link, so tapping it does nothing. The contact form has six fields, a tiny keyboard pops up, and the submit button is buried below the fold. The visitor has to scroll sideways to read a paragraph. None of this is catastrophically broken. The site "works." It just makes the person feel like they're fighting it.

Most people don't complain. They leave.

What good actually looks like on a small screen

A well-built mobile site does a handful of specific things. Text is big enough to read without zooming, typically 16px or larger. Tap targets, meaning buttons, links, phone numbers, are at least 44px tall so a thumb can hit them reliably. Images are compressed and sized for the screen, not served at full desktop resolution. The layout is a single column. Scrolling is vertical only.

The phone number is a real tel: link. One tap, they're calling you. That alone is worth something. Your contact form matters too, and on mobile, shorter is almost always better. Three fields beats seven, every time.

The menu collapses into a simple button. Navigation is predictable. The most important information, what you do, where you are, how to reach you, is visible without scrolling. It doesn't need to be flashy. It needs to work in someone's hand while they're distracted and mildly impatient.

Why "mobile responsive" is not the same as mobile good

This is the part that trips people up. You may have been told your site is "mobile responsive." That just means the layout doesn't completely break on small screens. It does not mean it was designed for a phone. There is a real difference between a desktop site that technically squishes down and a site that was built from the small screen outward.

A responsive site might stack your three desktop columns into one mobile column, sure. But if those columns had tiny text, oversized images, and a navigation menu that's still 8 links deep, the phone version is still a mess. Responsive is a floor, not a finish line. There are other warning signs worth checking while you're in there.

If your developer or website builder checked the "mobile responsive" box a few years ago and called it done, that's probably the version your customers are seeing today. Go check it yourself before you spend another dollar on ads.

The fix isn't always a full rebuild

Sometimes it is. If the site is old, slow, and built on a template from 2017, starting fresh is usually faster and cheaper in the long run than patching. The real cost of leaving a bad site up is one of those things that doesn't feel urgent until you do the math and realize what it's been quietly bleeding.

But sometimes the fix is targeted. Compressing images can shave 3 seconds off load time. Making the phone number tappable takes about ten minutes. Bumping the font size and trimming the form removes most of the friction before a visitor even thinks about leaving. If you know what to look at, you can fix the worst offenders without scrapping the whole thing.

The goal isn't a perfect site. The goal is a site that doesn't make someone's thumb give up before they find out you exist.

If you want to know what a stranger actually sees when they find you on their phone, tell me what you've got and I'll take a look.