Is your website mobile-friendly? How to check in a minute

The fastest way to check if your website is mobile-friendly is to pick up your own phone and try to do what a customer does: read the top of the page, find your phone number, tap it, and find one service. If you have to pinch, zoom or hunt for any of that, the site is not mobile-friendly, whatever a tool says. Below is a one-minute test you can run now, what each problem usually means, and how to get a measured second opinion for free.

The one-minute phone test

Use your own phone, not a desktop browser squeezed narrow. Open the browser, type your web address and go through these in order. Give each a yes or no.

Can you read the first sentence without zooming? The text should be comfortable at arm's length. If you reach for two fingers to enlarge it, it is too small.
Is it clear what you do and where, without scrolling? The first screen should say, in words, something like "Roof repair and replacement in Dayton". A logo and a photo alone do not count.
Can you tap the phone number and does the phone offer to call? Try it. If nothing happens, the number is plain text instead of a call link.
Does the menu open and close properly? Tap the menu button (often three short lines, top corner). Every item should be readable and tappable, and the menu should close again without trapping you.
Does anything stick out sideways? Drag the page left and right with one finger. A page that slides sideways has something wider than the screen, often a photo or a table.
Are buttons big enough for a thumb? Try tapping a link in the footer or a small button. If you keep hitting the wrong one, they are too small or too close together.
Can you fill in the contact form? Tap into the first box. The keyboard should appear, the box should stay visible above it, and for email and phone fields the right keyboard should show (the @ key, or the number pad).
Does anything cover the page? A cookie banner, chat bubble or pop-up that takes half the screen and is hard to close is a common way to lose a visitor in the first seconds.

If you answered yes to all eight, your site does the basics on phones. Every no is a specific thing to fix, which is more useful than a vague feeling that the site "looks old".

What the common failures usually mean

Tiny text and a page you have to zoom into almost always means the site was built for computer screens and is being shrunk to fit. Older sites, especially from before the mid-2010s, often work this way. This is not a quick setting; the layout itself was never designed to rearrange for a narrow screen. Modern sites are "responsive", which means the same page rearranges itself to suit the screen it is on.

A phone number that cannot be tapped is usually a small fix. In most website editors you can turn the number into a link starting with "tel:" followed by the digits. Making your phone number tappable shows how in the common editors.

A page that slides sideways is usually one element that is too wide: a large photo set to a fixed width, an embedded map, a price table or a video. Find the section where the sideways slide starts, and that is your culprit.

A menu that will not open or close tends to be a broken script from an old theme or plugin. It may need a developer, or a theme update on WordPress.

Pop-ups you cannot close are often an add-on you installed and forgot. Most have a setting to show a smaller version on phones, or to switch off on phones entirely.

A measured second opinion with Lighthouse

Google used to offer a simple "Mobile-Friendly Test" page. It was retired at the end of 2023, so if an old article sends you there, that is why the link fails. Two free tools do the job now.

PageSpeed Insights. Go to pagespeed.web.dev, paste your address and press Analyze. It runs Google's Lighthouse checks on the mobile version of your page. Besides speed, scroll to the "Accessibility" and "Best Practices" sections. Items like "Tap targets are not sized appropriately" or "Document doesn't use legible font sizes" are the tool's way of saying what your thumb already told you.

Lighthouse inside Chrome on a computer. Open your site in Chrome, press F12 (or right-click and choose Inspect), then click the small phone-and-tablet icon at the top left of the panel that opens. Your page now displays at phone width, and a menu at the top lets you pick a phone model. To get a report, click the "Lighthouse" tab in the same panel, tick "Mobile", and press "Analyze page load". This is handy for checking pages one after another without picking up your phone.

Tools are useful for finding things you would not notice, like a form box without a label. They cannot tell you whether the page makes sense to a customer in a hurry. Your phone test does that.

Check more than the home page

Owners often check the home page and stop. Customers do not land only there. Run the phone test on:

your most important service page,
the contact page and its form,
any page with a price list, menu or table,
your gallery or photos page,
one page Google sends people to, if you know it (Search Console shows which).

Price lists and menus as PDF files are a frequent problem: on a phone they open in a separate viewer where text is tiny. A plain web page reads far better.

When fixing is not worth it

If your site fails the first test, tiny text that needs zooming, the problem is the whole layout, not a few settings. Patching an old non-responsive site page by page tends to cost more than it seems at first and still leaves an old site. That is usually the point where a rebuild makes sense. Why your old website looks bad on phones explains the choice in more detail, and mobile-friendly websites and Google covers what Google itself looks at.

What to do this week

Do the eight-point phone test on your home page and write down every no.
Ask one person outside your business to do it while you watch.
Repeat on your contact page and your busiest service page.
Run PageSpeed Insights once and note any tap target or font size warnings.
Fix the quick ones (tappable phone number, pop-up on phones) right away.

If the list of no's is long, you can see your site rebuilt first and run the same test on the new version before you decide anything.