Mobile-friendly websites: why it matters and how to check yours

Open your website on your phone. Not the office monitor, the phone. Now try to do the thing a customer would do: find the service, read about it, and get in touch. If any step made you pinch, squint, scroll sideways or miss a button, that is what every mobile visitor experiences, and in most businesses that is more than half of them.

Why it matters more than it used to

Google indexes and ranks the mobile version of your site. If the mobile version is missing content that the desktop version has, or is hard to use, that is the version being judged. A site that “works on desktop” is being ranked on the version you never look at.

Speed is measured on mobile too. Google’s page experience signals come from real visitors’ phones, and phones on mobile networks are slower than the laptop on your office wifi.

And the visitors themselves: for a local business, a clinic, a trade, a restaurant, mobile share is often seventy percent or more. People searching for you are standing somewhere, holding a phone.

What mobile-friendly means now

It used to mean “the layout squeezes down to a phone width”. That is the minimum. In 2026 it means:

• Text readable without zooming. Sixteen pixels or larger for body text, real line breaks, no walls of text.
• Tap targets you can hit. Buttons and links big enough for a thumb, with space between them. Google’s own guidance is roughly forty-eight pixels.
• No sideways scrolling. Nothing wider than the screen: no tables, images or embedded maps that push the page out.
• The menu works. Opens with one tap, closes with one tap, and every page is reachable from it.
• Fast. Under three seconds to something useful on a mid-range phone on a mobile connection. Images sized for phones, not desktop images scaled down.
• Forms you can fill with a thumb. Few fields, the right keyboard for each (number pad for phone numbers), and a button you can find.
• The phone number is tappable and the address opens a map.
• Nothing that only works with a mouse. Hover menus, hover-to-reveal content, drag interactions.

The five-minute check

1. Open the site on your phone and on a second phone from someone else, ideally a cheaper one.
2. Do the customer task from above. Note every moment of friction.
3. Turn the phone sideways. Some layouts break in landscape.
4. Go to Google’s PageSpeed Insights, paste your address, and look at the mobile tab. The top section is what real visitors experience. Anything in orange or red is a problem.
5. In Search Console, open the Core Web Vitals report and the Pages report. Both will tell you if Google sees mobile problems.

What the fixes involve

If the site was built responsive and it is only a few things wrong, images too large, a table that overflows, a menu that misbehaves, that is a day or two of fixes.

If the site was built desktop-first, with a mobile version bolted on or none at all, there is no cheap fix. Responsive layout is a property of how the site was built. This is one of the clearest cases where a rebuild is the honest answer, and the good news is that a modern rebuild is mobile-first by default, so the problem does not come back.

Our scanner checks the mobile viewport setting and the speed signals as part of every scan. It is a start. Your own phone is the rest of the test.