Test Mobile Usability: What to Use Now That Google's Tool

Google Killed Its Mobile-Friendly Test Tool — Here's What to Use Now

If you typed Google's old Mobile-Friendly Test URL from memory and got a dead page, you're not alone. Google retired the Mobile-Friendly Test tool, its API, and the Search Console Mobile Usability report in December 2023. There's no successor with the same name, and most articles online haven't caught up — they link to a tool that no longer exists or send you to app-testing platforms built for user-panel research, not live websites.

Google's reasoning was that mobile usability had essentially become the default expectation for the web, not a separate pass/fail check (Google Officially Retires the Mobile Usability Tools). With most sites now built responsively, a dedicated "is this page mobile-friendly?" tool made less sense than folding those checks into broader page-experience and Core Web Vitals reporting. That's reasonable for Google's index — but it's a real gap for anyone who needs to test mobile usability on a specific site today. This guide closes that gap with the tools that still exist and work in 2026.

What 'Mobile Usability' Actually Means (and What It Doesn't)

Mobile usability, page speed, and mobile-friendliness get used interchangeably, but they measure different things.

Mobile usability is about whether a real person can comfortably use your page on a phone: does content fit the screen without horizontal scrolling, are tap targets big enough to hit accurately, is text legible without pinch-zooming, and is the viewport configured correctly. Page speed measures how fast content loads and becomes interactive — a separate concern covered by Core Web Vitals like LCP and INP. Mobile-friendliness is a looser, older term meaning "does this page even render on mobile at all," mostly a solved problem now that most sites are responsive.

A proper mobile usability checklist isolates layout and interaction issues from performance issues. A page can load in under a second and still be unusable on mobile because buttons are too small or the viewport meta tag is missing. Conversely, a well-laid-out mobile page can still frustrate users if it loads slowly — a separate fix, covered in Speed Page Google: How to Check and Fix Your Score Fast.

How to Test Mobile Usability in 2026: Step by Step

Here's a practical, repeatable sequence for testing mobile usability on any live page without relying on a tool that no longer exists.

Run Google Lighthouse or PageSpeed Insights

Lighthouse is Google's own recommended replacement for the old Mobile-Friendly Test, built into Chrome DevTools — open DevTools, go to the Lighthouse tab, select "Mobile," and run an audit (Google Retires Mobile-Friendly Test, Suggests Lighthouse). If you'd rather skip setup, run the same audit at pagespeed.web.dev by pasting in a URL. Under the mobile report, check the accessibility and best-practices sections, which flag tap targets that are too small, text too small to read, and content that overflows the viewport — the closest thing left to a dedicated mobile usability test.

Check the Core Web Vitals Report in Search Console

Search Console no longer has a standalone Mobile Usability report, but device-level usability signals still surface inside the Core Web Vitals and page-experience reports. Filter the URL groups by device to isolate mobile-specific issues across your indexed pages. It won't catch every layout problem Lighthouse does, but it's useful for spotting patterns across many URLs at once rather than testing one page at a time.

Do a Manual Real-Device Pass

Automated tools miss things a thumb catches instantly. Pull up the page on an actual phone and check:

• One-thumb reachability — can primary actions (menu, search, checkout) be reached without repositioning your grip?
• Sticky headers or footers — do they eat so much vertical space that content underneath becomes cramped or unreadable?
• Pop-ups and interstitials — do they cover the full screen and make it hard to dismiss, especially right after load?
• Form fields — are inputs large enough to tap accurately, and does the correct keyboard type appear (numeric for phone numbers, email keyboard for email)?
• Font scaling — does text remain legible if the user has increased their system font size?

None of this shows up as a score. It's a checklist, and it's the part most automated audits — including the old Mobile-Friendly Test — never fully covered.

Common Mobile Usability Issues Worth Fixing First

Not every issue carries equal weight. If you're triaging, fix these first:

1. Tap targets smaller than ~48px or spaced too closely together — the single most common cause of mis-taps.
2. Missing or misconfigured viewport meta tag — causes desktop-width layouts to render on mobile screens.
3. Text under 16px that forces users to pinch-zoom to read body copy.
4. Content wider than the screen, usually from a fixed-width image, table, or embed that ignores container constraints.
5. Full-screen interstitials that block content immediately after page load, particularly on entry from search.

Fixing these five typically resolves the majority of mobile usability complaints, well before you touch anything related to speed.

Testing Mobile Usability Across an Entire Site (Without Doing It by Hand)

Running Lighthouse and a manual device pass works fine for one page. It breaks down fast once you're managing a site with hundreds of URLs, or you're an agency responsible for a dozen client sites — nobody has time to manually test mobile usability at scale, page by page, every time content changes.

This is the gap Optimevra is built to close. Instead of running Lighthouse manually and cross-referencing Search Console filters, Optimevra's AI audit automatically checks tap target sizing, viewport configuration, text legibility, layout overflow, and other UX and accessibility issues across every page on a site — continuously, not just as a one-time snapshot. It pairs this with broader performance and conversion checks, so mobile usability findings sit alongside the rest of the picture rather than in a separate silo (more in AI Website Audit: What It Checks and How It Works). For agencies managing client sites, that means one dashboard flagging issues across every property instead of a rotation of manual spot-checks.

Frequently Asked Questions

Is there still a free Google tool to test mobile usability?

No. Google retired the Mobile-Friendly Test tool, its API, and the Search Console Mobile Usability report in December 2023, and there's no direct free replacement bearing that name. Google now points people to Lighthouse and PageSpeed Insights, both free but structured as general audits rather than a dedicated mobile usability pass/fail check.

What replaced Google's Mobile-Friendly Test tool?

Google explicitly recommends Lighthouse, accessible through Chrome DevTools or at pagespeed.web.dev, as the closest available replacement. It doesn't produce the same single mobile-friendly verdict, but its accessibility and best-practices sections flag the same underlying issues: small tap targets, illegible text, and viewport problems.

How do I check mobile usability in Google Search Console now?

Mobile usability signals now live inside the Core Web Vitals and page-experience reports rather than a standalone report. Open the Core Web Vitals report and filter by device to see mobile-specific performance and experience issues across your indexed URLs.

What's the difference between mobile-friendly and mobile usability?

Mobile-friendly generally means a page renders correctly on a mobile device at all, while mobile usability measures whether it's genuinely comfortable to use — tap target size, text legibility, layout fit, and lack of horizontal scrolling. A page can be technically mobile-friendly and still fail on usability if buttons are too small or text requires zooming.

Can I test mobile usability without a real phone?

Yes, to a point. Lighthouse and PageSpeed Insights simulate a mobile viewport and catch most structural issues like viewport configuration and tap target sizing. But some problems — one-thumb reachability, sticky elements eating screen space, intrusive pop-ups — are easiest to catch with an actual manual pass on a real device.

How often should I test my website's mobile usability?

Test after any layout, template, or content change that affects page structure, and re-check on a regular schedule if you manage multiple pages or client sites. Manual, one-off checks are fine for a single page, but sites with frequent updates benefit from continuous, automated monitoring rather than periodic manual audits.

Manually running Lighthouse, filtering Search Console, and thumb-testing tap targets across every page doesn't scale once you're past a handful of URLs. See it flagged automatically instead — run the live demo on your own site, or check pricing if you're ready to put continuous mobile usability monitoring in place. Start at Optimevra.