A customer mentions that your website was hard to use on their phone, or you go looking for Google's old website mobile friendly test and the page is gone. Either way, you are left with the same question: can someone on a phone actually find what you do and get in touch? That question has a practical answer you can get this afternoon, and it starts with the phone already in your pocket. A score from an online tool can help, but it cannot tell you whether a real person can tap your number, open your menu and send you a message. What you want is a short list of what fails, on which page, and whether each item is a small repair or a bigger job. You can build that list yourself in about fifteen minutes.
Key Takeaways
Open your home page, one service page and your contact page, then find a service, tap the phone number, use the menu and send a test inquiry without zooming.
Google retired the Mobile-Friendly Test, its API and the Search Console Mobile Usability report on December 1, 2023, and pointed site owners to Lighthouse from Chrome.
Spacing, text size, tap-to-call links and pop-ups are usually scoped repairs; missing mobile content or a contact path that cannot work without new templates points to a rebuild.
How do you check if your website is mobile friendly?
Use your own phone and try to do what a customer does. The check below takes about fifteen minutes, needs no software, and gives you a written list of real problems instead of a general feeling that the site looks dated. Each step matches something a phone visitor actually tries to do before they call or book. Do it on the phone you carry every day, with the browser at normal zoom.
Pick three pages that bring you business
Choose your home page, the service page that brings in the most inquiries, and your contact or booking page. These are the pages a phone visitor is most likely to land on right before they decide whether to reach you. If you run a store, swap the service page for a product page and add the checkout.
Run five tasks on each page
On each page, try these without pinching to zoom:
- Find a service: Can you tell what the business does and find the service you came for from the top of the page?
- Open the menu: Does it open, close and take you where you tapped, without covering the first useful content?
- Tap the phone number: Does your phone offer to dial it, or is it just text you would have to copy?
- Tap the main button: Does "Book," "Get a quote" or "Contact us" go where it promises?
- Send a test inquiry: Can you fill every field with the keyboard your phone brings up, and does the form show a clear confirmation after you send it?
A test inquiry is harmless. Put "test" in the message so whoever reads the inbox knows to ignore it, and confirm it arrived.
Scroll sideways, not just down
Drag each page left and right with one finger. If the page slides sideways, shows a strip of empty space, or cuts off the end of a line, something on it is wider than the screen. Also watch for bars that stay pinned to the top or bottom of the screen and sit on top of a button you need.
Switch to cellular data and hand the phone to someone else
Turn off Wi-Fi and repeat one task on cellular data. Then ask two people who did not build the site, ideally customers, to find one service and contact you without any instructions from you. Watch where they hesitate or tap the wrong thing. If you can borrow a second phone, try one small iPhone and one Android phone, since the same page can behave differently on each.
Write down every failure
For each problem, note the page, the phone and browser, and the task that failed. "Contact page, Android, Chrome: the Send button sits under the chat bubble" is something anyone can reproduce and fix. "The site feels clunky on mobile" is not.
What happened to Google's Mobile-Friendly Test?
Google retired it. On April 19, 2023, Google announced that the Mobile-Friendly Test, its API and the Mobile Usability report in Search Console would stop on December 1, 2023. Its reason was that, in the nearly ten years since the report launched, other strong resources for checking mobile usability had appeared, and it named Lighthouse from Chrome as one of them.
That is why a search for Google's test now brings up other companies' checkers. They can be handy for a quick look, but none of them is Google's verdict, and Google no longer hands out a pass or fail badge for mobile. Its current page experience documentation says Chrome Lighthouse can identify improvements, including for mobile usability, and asks site owners whether their content displays well on mobile devices.
If you would rather paste a web address than open developer tools, Google's PageSpeed Insights runs Lighthouse for you in the browser. Either way, treat the report as a second opinion that sits beside your phone check, not in place of it.
How do you use Lighthouse and Chrome's device view without getting lost?
Two free tools in the Chrome browser on a computer add useful signals to the phone check. You do not need to understand every line they produce. The goal is to catch problems your own phone might hide, such as a layout that breaks on a narrower screen than yours. Spend ten minutes here, not an afternoon.
Run a mobile Lighthouse report
Lighthouse is built into Chrome's developer tools. Open your page in Chrome, right-click, choose Inspect, open the Lighthouse tab, pick Mobile and run the report. Read the accessibility and best practice items first, since those tend to name specific problems like text that is too small, buttons placed too close together, or form fields with no label. Note the item and the page, then add it to your list.
Check several screen widths in device view
Chrome's device mode lets you shrink the page to a phone-sized width on your computer. Try 320, 375 and 425 pixels wide. You are looking for the same things as on your phone: lines cut off, sideways scrolling, overlapping buttons and a menu that stops working at one width but not another.
Know what the tools cannot tell you
Chrome describes device mode as a first-order approximation of how a page looks on a phone, not the phone itself. Lighthouse cannot tap your number and wait for a dial prompt, and it cannot tell you whether your test inquiry reached the inbox. A high score is useful evidence. It is not proof that a customer can reach you, and Google says good results in its reports do not guarantee top rankings.
Which mobile problems cost you calls and bookings?
Put your list in order of how badly each problem blocks someone from reaching you. No study ranks these by how often they happen on small business sites, so the order below is by damage to the contact path, not by frequency. A broken contact route comes before anything cosmetic.
| Problem | What the visitor runs into | What to check | Usual size of the fix |
|---|---|---|---|
| Menu or contact action unreachable | Cannot open the menu, find the number or reach the booking page | Every task on your three pages | Small to large, depending on the template |
| Phone number not tappable | Has to copy the number or give up | Tap the number on each page | Usually small |
| Forms that fight the keyboard | Wrong keyboard, tiny fields, errors with no explanation, no confirmation | Send a test inquiry on two phones | Often moderate |
| Pop-ups and pinned bars covering content | A dialog or chat bubble hides the button or the text | Load each page fresh and scroll | Usually small |
| Content wider than the screen | Page slides sideways, lines cut off | Scroll sideways; device view at 320 pixels | Usually small on a sound template |
| Text and buttons too small | Has to zoom to read, taps the wrong button | Read without zooming; tap closely spaced links | Usually small |
The cost of each problem is friction: a visitor who cannot tap, read or send has a reason to leave and try the next business. Google says intrusive pop-ups and dialogs can frustrate users, erode trust and make people unlikely to come back. Baymard Institute's mobile checkout research found serious form problems even on major ecommerce sites. Neither puts a number on the calls a local business loses, and no source does. Treat each item as a lost-inquiry risk, and fix the ones that block contact first.
Does being mobile friendly affect how Google ranks your site?
It affects what Google sees. Under mobile-first indexing, Google uses the version of your site that its smartphone crawler sees to index and rank your pages. So, if a service description, a set of links or a block of reviews appears on desktop but is hidden or missing on mobile, Google may not count it when it indexes the page. Google confirmed in October 2023 that the move to mobile-first indexing was complete.
Mobile-first indexing does not mean Google hands out a bonus for passing a mobile test. It means the mobile version is the one that counts, so keep your content, headings, links and contact details the same on phone and desktop. Google recommends responsive design, where the same page and web address adapt to the screen, as the easiest pattern to maintain.
Google describes page experience as many signals, not a single switch. The same documentation that recommends a good mobile display also says good report results do not guarantee top rankings. Fix mobile problems because they stop customers, and let any search benefit follow from the content Google can now see.
What standards say how a mobile page should work?
You do not have to read a standard to run the check above, but it helps to know the yardstick behind a couple of the checks. W3C's accessibility guidelines, WCAG 2.2, cover mobile use, and W3C says mobile accessibility is covered by WCAG rather than a separate mobile standard. Two items line up directly with the phone check.
The first is reflow: content should work at a width equal to 320 CSS pixels without scrolling in two directions and without losing information or functions, except where a two-way layout is essential, such as a map or a data table. That is the sideways-scroll test from your phone. The second is minimum target size: at the AA level, tap targets should be at least 24 by 24 CSS pixels, or spaced so a finger does not hit the wrong one, with some exceptions.
These are accessibility standards, and who must meet them legally depends on the organization. The U.S. Department of Justice's April 24, 2024 rule sets WCAG 2.1 AA as the technical standard for web content and mobile apps from state and local governments, with compliance dates in 2027 or 2028 depending on population. It does not create a universal rule for private businesses. For your own site, use the numbers as a practical target for readable, tappable pages.
Is it a quick fix, or does the site need a redesign?
Look at where the problems sit. If your content, menu, buttons and contact path all exist on mobile and only misbehave in places, you are usually looking at targeted repairs. If the mobile version is missing things or cannot be made to work without rebuilding the page layouts, the job is bigger. Google does not set a line between the two, so judge by the list you wrote.
Problems that are usually small, scoped fixes
On a template that is otherwise sound, these are often contained changes followed by a recheck on real phones: a missing viewport setting, content that overflows the screen, small text, cramped spacing, images that do not resize, and buttons with too little padding. Turning a plain phone number into a tap-to-call link is usually small too, though call tracking, cookie consent or a third-party booking widget can add steps.
Problems that take more work
Forms often land in the middle. A proper repair can involve labels, clear error messages, the right keyboard for each field, autofill, validation on the server, spam protection and conversion tracking. W3C's guidance on identifying input purpose is the reference for letting phones autofill a name, email or phone number. Reworking a menu or a third-party theme across every page type is larger still.
Signs the site needs rebuilding
A redesign is justified when the mobile version leaves out primary content or links, depends on a layout built only for desktop, cannot support a usable menu and contact path without new templates, or runs as a separate mobile site that cannot be kept equal to the desktop one. If you are already considering a move to a different platform, our post on what actually moves when you switch website builders covers what to plan for.
When you do not need to change anything
If every task works on real phones, Lighthouse and device view show nothing serious, your mobile content matches desktop, and neither your analytics nor your customers point to a mobile problem, you may not need a project at all. Recheck after changing your theme, a plugin, a form or a major page, and check your analytics now and then for a device split that looks off. If those numbers look strange in the first place, start with why Google Analytics can show zero or wrong visitors.
How well do you know your mobile check?
Pick an answer to begin.
1. Where can you run Google's Mobile-Friendly Test today?
2. What is the most important thing to test first on a phone?
3. Under mobile-first indexing, which version of your site does Google mainly use?
Frequently Asked Questions About website mobile friendly test
Does Google still have a Mobile-Friendly Test?
No. Google retired the Mobile-Friendly Test, its API and the Search Console Mobile Usability report on December 1, 2023.
What should I use instead of Google's mobile friendly checker?
Google names Lighthouse from Chrome. Use it together with Chrome's device view and, most of all, a task check on a real phone.
How do I see what my website looks like on a phone from my computer?
In Chrome, right-click the page, choose Inspect and turn on device mode. Try widths of 320, 375 and 425 pixels. It is an approximation, so confirm anything important on an actual phone.
What does mobile-first indexing mean for my site?
Google primarily indexes and ranks the mobile version of your pages, as seen by its smartphone crawler. Keep the same content and links on mobile as on desktop.
Do I need a separate mobile website?
Usually not. Google recommends responsive design, where the same page and web address adapt to the screen size.
What is the quickest warning sign that my site is not mobile friendly?
Any trouble finding, tapping, reading or sending your main contact action on a phone. Test that before anything else.
Wrapping Up
Checking whether your website is mobile friendly comes down to a phone and fifteen minutes. Run the five tasks on three pages, scroll sideways, try cellular data and hand the phone to someone else. Google's own test has been gone since December 1, 2023, so use Lighthouse and Chrome's device view as a second opinion, and remember that Google ranks the mobile version it sees.
With a written list sorted by what blocks contact, you know what to fix first, what can wait, and whether you are looking at a repair or a rebuild. When the list comes back clean, you can stop worrying about it and simply recheck after the next big change.
If your list has items you would rather not fix yourself, Web Leveling can go through it page by page and phone by phone. Our web design team builds custom, responsive sites that work the same on a phone as on a desktop, and we will tell you when a small repair is all your site needs. We work with small and medium businesses across the country and overseas. Send us what your phone check turned up, and we will reply with which items are quick fixes and which are bigger jobs.
Terms
Mobile website words in this post
Tap a term to see what it means.
Mobile-friendly. A site that a phone visitor can read, use and act on without zooming, missed taps or hidden content.
Responsive design. One page and web address whose layout adapts to the screen size, the pattern Google recommends.
Mobile-first indexing. Google's practice of indexing and ranking the version of a page its smartphone crawler sees.
Lighthouse. A free auditing tool built into Chrome that reports on accessibility, best practices and more.
Device mode. A Chrome feature that shows a page at phone-sized widths on a computer, as an approximation.
Reflow. A WCAG requirement that content works at a narrow width without scrolling in two directions.
Tap target. A link or button meant to be touched; WCAG 2.2 AA sets a 24 by 24 CSS pixel minimum.
