Website planning

Is Your Website Easy to Use on a Phone? A 15-Minute Check

Check your website on a real phone: readable text, usable buttons, working contact links, clear forms, and the same key information as desktop.

Wild Article 014, 2026-11-09: Is Your Website Easy to Use on a Phone? A 15-Minute Check

The short answer: you can spot useful issues with your own phone and a short checklist. Look for text you can read without zooming, no sideways scrolling, buttons you can tap without hitting the wrong one, a phone number that dials when tapped, a form you can finish with your thumbs, and the same important information you'd see on a desktop.

Why bother

Two reasons. First, anyone who visits on a phone needs to be able to use the site there. Second, Google's documentation says it uses the mobile version of your site's content for indexing and ranking, which it calls mobile-first indexing. Google's page says that if your mobile version has less content than your desktop version, you can expect some traffic loss.

Neither point is a promise that fixing mobile issues will raise your rankings. Google's page experience guidance says that good scores in Core Web Vitals or similar tools don't guarantee your pages will rank at the top of search results.

The check

Use a real phone, not just a shrunken desktop window. Test your homepage and one inner page.

1. Can you read it without pinching?

Text should be readable at normal zoom, and the page should not scroll sideways. The W3C's Reflow guideline (WCAG 1.4.10) says content should be presentable without scrolling in two dimensions at a width equivalent to 320 CSS pixels (a 1280-pixel-wide desktop window zoomed to 400%), except for things like maps, data tables, and diagrams that need two-dimensional layout.

Also try pinching to zoom. If you can't, ask your developer to check the page's viewport setting. MDN's viewport documentation warns that disabling zoom prevents people with low vision from reading the page.

2. Can you tap the right thing?

Try the menu, buttons, and links with your thumb. WCAG 2.2's Target Size (Minimum) criterion, at level AA, says tap targets should be at least 24 by 24 CSS pixels. There are exceptions, including links inside sentences and small targets that have enough space around them. The W3C calls this a minimum and recommends larger targets for important controls.

If you keep tapping the wrong link, that's the sign to flag.

3. Does the phone number dial?

Tap your phone number. If it doesn't start a call, ask for a "tel:" link. MDN's anchor element documentation says tel: links autodial on cellular devices. Do the same with your email address.

4. Is the important content still there?

Open the same page on desktop and your phone. Compare services, hours, service area, and contact details. Google says mobile pages should have equivalent primary content, and that long content can be moved into accordions or tabs rather than removed. Look at titles and headings too, since Google says the title and meta description should be equivalent on both versions.

5. Can you finish the form?

Fill out your contact form on your phone. Are labels visible? Can you tell what went wrong if you make a mistake? The W3C's forms tutorial says users generally prefer short forms and recommends asking only for what's required, since excessive requests make abandonment more likely.

6. Does it load in a reasonable time?

You can feel this yourself, but Google's Core Web Vitals give published targets: the largest content appears within 2.5 seconds (LCP), the page responds to taps in 200 milliseconds or less (INP), and layout doesn't jump around (CLS of 0.1 or less). Google says to measure at the 75th percentile of page loads, separately for mobile and desktop. Your own phone is one data point, not a measurement. Ask your developer for field data if speed matters to you.

Quick scorecard

  • No sideways scrolling
  • Text readable at normal zoom
  • Menu and buttons tap cleanly
  • Phone number dials, email opens a message
  • Hours, services, and contact details match desktop
  • Form completes, with clear error messages
  • Page feels responsive on mobile data, not just Wi-Fi

Hypothetical example: an electrician's homepage shows three service areas on desktop but hides them entirely on mobile. The phone number is plain text. The owner flags two items for the developer: restore the service areas (perhaps in an accordion) and turn the number into a tap-to-call link.

What this check can't tell you

It won't prove a site meets WCAG or any accessibility law. The criteria above are only a few of many. Accessibility requirements vary by situation, and legal questions need a qualified professional. It also won't measure real-world speed, and a clean result on your phone doesn't cover other devices and browsers.

Turn the check into a useful fix list

Write down the page, the task you tried, and what got in the way. A screenshot and your phone model give your developer a clearer starting point than a general request to make the site mobile-friendly. For deciding how much work is needed, see when to redesign versus repair.

Evidence

Sources

  1. Mobile-first Indexing Best PracticesGoogle · Retrieved
  2. Understanding Google Page ExperienceGoogle · Retrieved
  3. Understanding Success Criterion 1.4.10: ReflowW3C WAI · Retrieved
  4. Viewport metadata - MDNMDN Web Docs · Retrieved
  5. Understanding Success Criterion 2.5.8: Target Size (Minimum)W3C WAI · Retrieved
  6. <a> HTML anchor element - HTMLMDN Web Docs · Retrieved
  7. Forms TutorialW3C WAI · Retrieved
  8. Web Vitals  |  Articles  |  web.devGoogle web.dev · Retrieved

A useful next step

Keep a useful record

Use the ownership checklist to organize the accounts and people involved in your site.

Open the ownership checklist