Is Your Website Actually Mobile-Friendly? A Checklist You Can Run on Your Own Phone

A while back I watched a friend try to book a haircut from her phone. The shop’s website loaded fine. She spent most of a minute pinching and zooming to find the phone number, tapped it, and nothing happened, because the number was plain text on the page. She tried copying it, lost the last two digits somewhere between apps, gave up, and booked with a different barber four blocks away. The whole thing took maybe two minutes, and the first shop will never know it happened.

That gap is what this post is about. I touched on mobile in my guide to conversion-optimized websites, and it’s the section I most wanted to expand, because this is where I see local businesses lose the most customers with the least awareness that anything’s wrong. Your site can look great on the office computer and still be quietly unusable on the screen where most of your customers actually meet it.

So here’s the long version: why local search lives on phones, what mobile-friendly means in practice, and a full checklist you can run on your own phone in about fifteen minutes. There’s nothing to install. Your phone and your thumb are the whole toolkit.

Local search is a phone activity

Think about when people actually search for a business like yours. A furnace dies at eleven on a February night, and the homeowner is under a blanket on the couch typing “emergency furnace repair” with cold thumbs. Nobody’s getting up to boot the desktop in the den for that.

Sometimes the search happens in a car. Someone hears a grinding noise from a front wheel, pulls into a plaza parking lot off Kingston Road, and looks for a mechanic while the engine ticks. Whoever seems competent in the next ninety seconds gets the call.

Sometimes it’s a job site. A contractor standing in a half-gutted kitchen realizes his countertop supplier fell through and he needs a replacement this week. He searches right there, drywall dust on the screen, one work glove off.

Those moments have two things in common. The searcher is holding a phone, and they’re ready to act right now. That second part is what makes mobile traffic so valuable for a local business. People at a desk are often still researching. People on a phone are frequently minutes away from calling somebody, and the only open question is who.

For most local businesses, phones supply the majority of visits, and for urgent trades it skews even harder. So when you’re judging your own website, the version on a five-inch screen is the one doing the work.

“It loads on my phone” is a low bar

Most owners check their site on a phone once, see that it comes up, and file mobile under handled. Loading is step one of about ten.

A page can render at the correct width and still fail everyone who touches it. Text that reads fine on a monitor becomes squint material at arm’s length. A button that’s an easy click with a mouse pointer is a misfire with a thumb. A menu that opens on hover never opens on a touchscreen, because touchscreens have no hover. The site technically works the way a door with a broken handle technically works. You can get in if you’re determined. Your customers aren’t determined. They have nine other search results waiting below you.

Genuinely mobile-friendly means a stranger in a hurry can figure out what you do and start a call with one thumb, probably while half doing something else. That’s the standard the checklist below tests.

There’s a trust layer under all of this too. The DreamHost 2026 Local Business Trust Index found 70% of consumers are more likely to do business with a company that has a website. The catch is that for most of those people, the website they judge is whatever shows up on their phone. A site that fights their thumbs doesn’t bank much of that credibility.

The self-test: fifteen minutes with your own phone

Pull out your phone and open your website. If you can, switch off wifi and use cellular data, because that’s how customers arrive, and office wifi hides speed problems. Then work through these eight checks.

1. Read a full paragraph without zooming. Go to your services page and read it at a normal arm’s length. If you pinch to zoom even once, the text is too small. You don’t need to measure font sizes; your eyes will tell you within a sentence. Squinting counts as a failure, because a customer in a parking lot won’t squint. They’ll leave.

2. Tap the phone number. Every phone number on your site should start a call with a single touch. This works through something called a tel link: in the code, the number is wrapped in a small instruction beginning with “tel:”, which tells the phone those digits are callable. With it, one tap rings your business. Without it, the number is decoration, and the visitor has to memorize or copy it, which is exactly where my friend’s haircut booking died. Check the number in your header, your contact page, and your footer, since visitors tap the first one they see.

3. Press the buttons with your thumb. Use your actual thumb, the way a customer would while standing up and holding a coffee. Can you hit each button cleanly on the first try? Are links spaced far enough apart that you don’t tap the wrong one? A tap target should be roughly the size of a fingertip pad, with breathing room around it. If you keep landing on the link beside the one you wanted, so will everyone else, and each mistap is a small dose of frustration on the way to your phone number.

4. Open the menu. On phones this is usually the three-line icon in a corner. Tap it. Does it open instantly? Can you close it again without hunting? Do all the items respond to touch? I’ve tested sites where the menu opened but the close button sat behind another element, so the visitor was stuck staring at a navigation panel with no way back. That visitor leaves and remembers nothing about your business except the trap.

5. Find your main service in two taps. Hand the phone to someone who doesn’t work in your business and give them a job: “find the drain cleaning page” or “find wedding cake pricing.” Count their taps from the homepage. Two should do it. If reaching your bread-and-butter service takes four taps through nested submenus, the structure is working against the people most ready to hire you.

6. Scroll and watch the edges. Swipe slowly down the whole homepage and a couple of inner pages. The page should only move vertically. If it wiggles side to side, or a stray image or block pokes past the edge and creates a horizontal scroll, something is overflowing the screen. It reads as broken even to visitors who couldn’t name what’s wrong, and it usually means one element on the page was never sized for small screens.

7. Fill out your contact form. Actually submit it. While you type, watch which keyboard your phone offers. A properly built form marks each field with its type: the email field is coded as an email field, so the keyboard appears with the @ symbol ready, and the phone field is coded as a phone field, so you get a big number pad instead of full qwerty. Small thing, real effect, because thumb-typing a phone number on a letter keyboard is annoying enough that some people quit mid-form. Also check that the fields are large enough to tap into, that you can see what you’ve typed, and that the confirmation message actually reaches your inbox.

8. Find your address and hours. A customer deciding whether to visit wants two facts fast: where you are and whether you’re open. Your hours should sit somewhere obvious, like the contact page or the footer, without a PDF or a deep click. Your address should be linked so that tapping it opens the map app with directions ready. If someone has to copy your address and paste it into Google Maps by hand, you’ve added a chore to the last step before they walk in.

Tally it up. Eight passes puts you well ahead of the local competition. Each miss is a specific, fixable leak, and every one of them sits between a customer who already found you and the phone call you wanted.

The quiet mobile killers

Beyond the checklist, a few patterns sink mobile experiences over and over. I see these constantly when I audit sites around Toronto.

Popups you can’t close on a small screen. A newsletter popup built and previewed on a desktop often renders on a phone with its close button pushed off the visible screen, or shrunk to a speck under the notch. The visitor gets a wall. Some will rotate the phone or zoom around looking for the X. Most just leave. If you run any popup at all, test closing it on a phone, and consider whether a banner tucked at the bottom of the page would do the same job without ever blocking anyone.

PDFs standing in for real pages. Restaurants are the classic case, posting the menu as a scanned PDF, but I’ve seen contractors do it with price lists and clinics do it with intake info. On a phone, a PDF opens as a tiny full-width page you have to pinch into, pan around, and sometimes wait several megabytes for over cellular. The information your hungriest, most ready-to-buy visitors want most ends up in the least usable format on your whole site. Put it on an actual page as regular text. As a bonus, Google can then read it properly too.

Important links styled like fine print. Somewhere along the way, key pages end up living only in the footer, set in the same tiny type as the privacy policy. On a desktop that’s survivable. On a phone those links are nearly untappable and nobody scrolls down there anyway. Anything a customer genuinely needs, like services, pricing, or booking, deserves a spot in the main menu and a real button.

Tables that force sideways scrolling. A five-column pricing table that looks tidy on a monitor gets crushed on a phone, and the visitor has to drag sideways to see half of it, usually while the row labels scroll out of view. By the third drag they’ve lost track of which price belongs to which service. Stacked lists or simple cards carry the same information without the gymnastics.

For a service business, the call is the conversion

Here’s the frame that makes all of this matter. An online store has a long funnel with several steps where polish helps. A plumber’s funnel is short: someone searches, glances at your site, and calls. The call is the whole conversion. Everything on your mobile site either shortens the distance to that call or stretches it.

Every extra tap is a toll booth. So is every pinch-zoom, every mistapped link, and every popup hunt. Picture a hypothetical: ten people with a burst pipe land on your site this month, and a broken tel link makes each of them copy your number by hand. You won’t lose all ten. You’ll lose some, and you’ll never see it happen, because an abandoned visit leaves no voicemail. The customer just calls the next result, and for an emergency trade that’s likely a job worth hundreds of dollars, gone over a detail that takes minutes to fix.

That invisibility is the trap. A rude employee gets complained about. A leaky mobile site loses the same customers in silence, month after month, while the owner concludes the website “doesn’t really bring in business.”

What Google does with your mobile site

One plain sentence covers it: Google primarily uses the mobile version of your website when deciding how to rank it, an approach called mobile-first indexing.

The practical upshot is that the experience you just tested with your thumb is also, roughly, the version of your site Google evaluates. If content is hidden, broken, or unusable on the phone version, you shouldn’t expect the desktop version to bail you out. I won’t pretend to know Google’s internal weightings, and neither does anyone selling you guarantees about them. The safe conclusion is simpler: making your site genuinely work on phones serves the customers you can see and the ranking system you can’t, and it’s the same work either way.

When patching stops making sense

Some sites can be fixed with an afternoon of small changes: a tel link here, bigger type there, one overflowing image resized. If your checklist misses were narrow, do that this week.

Other sites fail the checklist for structural reasons. A few signs you’re in that territory:

• The design has a fixed width from the era when every visitor had a monitor, so it can shrink but never reflow.
• It was built on a theme or page builder that’s no longer updated, and every mobile fix visually breaks something on desktop.
• The quotes you’re collecting for repairs are creeping toward the price of building fresh.
• You’ve patched it before, and each round of fixes surfaces a new layer of problems underneath.

At that point, patching is renovating a foundation problem with paint. A rebuild sounds drastic until you price it against another year of silent losses from the phone traffic that makes up most of your visitors.

When I build sites, the phone layout is the starting point and the desktop layout adapts outward from it, which is the opposite of how older sites were made. Every item on the checklist above is baked in from the first day: readable type, tappable numbers, thumb-sized buttons, a two-tap path to services, forms that summon the right keyboard. A five-page site built that way, on fast static hosting, will beat a patched-up old build on every check without you having to think about any of this again.

Run the test this week

Fifteen minutes, your own phone, the eight checks above. You’ll either confirm your site is solid, which is worth knowing, or you’ll walk away with a specific list of what’s costing you callers.

If the list turns out longer than you want to deal with, that’s the job I do for a living. I build conversion-focused, mobile-first websites for small local businesses. My standard build is $1,000, and new clients currently pay $500, with the first year of hosting and support included and $250 a year afterward if you’d like me to keep looking after it. The full details are at hughmcnamara.com/new-clients. Run your site through the checklist first, then send me your results if you’d like a second opinion. I’ll tell you plainly whether you need a few fixes or a fresh start.