Web Page Mobile Friendly Test: What to Use Now It's Gone

Google's Mobile-Friendly Test Is Gone — Here's What That Means for You

If you searched "web page mobile friendly" hoping to paste in a URL and get a clean pass/fail verdict, you've hit a wall. Google's Mobile-Friendly Test was retired in December 2023, and the standalone tool no longer loads for new checks. Google's own retirement announcement pointed webmasters toward Lighthouse as the replacement for the mobile usability report, alongside PageSpeed Insights and the URL Inspection tool in Search Console.

That's a change in how you have to think about mobile testing, not just a URL change. The old tool gave a single yes/no answer; its replacements don't. Lighthouse scores performance and best practices separately. PageSpeed Insights blends lab and field data. Search Console shows how Googlebot Smartphone rendered a specific page, but only after it's been crawled. There's no single "mobile friendly test alternative" that replicates the old simplicity — which is why so many site owners now get three different signals and don't know which to trust. The rest of this article resolves that with a concrete checklist and a way to check it at scale.

What 'Mobile Friendly' Actually Means Today

Mobile-friendliness isn't a badge Google hands out anymore — it's baked into how your pages get indexed. Under mobile-first indexing, Google predominantly uses the mobile version of your content for indexing and ranking, so a clunky mobile experience doesn't just annoy phone users — it can suppress how your page performs in search overall, including on desktop. Mobile-first indexing has been rolling out for years, and reporting shows it now covers the vast majority of indexed sites, so this is the default, not an edge case.

In practical terms, a page counts as mobile friendly when it's readable and usable on a small touchscreen without extra work: no pinching to read text, no horizontal scrolling, tap targets that don't require surgical precision, and load times that don't stall on a mobile connection. Mobile usability, in Google's framing, is a proxy for whether a real person on a real phone can use your page without friction.

How to Check If a Page Is Mobile Friendly Right Now

Start with Search Console. Open URL Inspection, paste in the page, and look at how Googlebot Smartphone rendered it — this shows the actual mobile crawl, not a guess. The URL Inspection tool is also the most reliable way to confirm mobile-first indexing status for a specific page, since it tells you which version of the page Google is actually using.

From there, run two manual checks that take about thirty seconds each: open the page on an actual phone and try to pinch-zoom (if you need to, something's wrong), and resize your desktop browser window to phone width to see whether content reflows or breaks. If either check reveals overflowing content or unreadable text, the root cause is almost always the viewport configuration — worth its own look via this breakdown of correct viewport meta tag syntax and the mistakes that break it.

The Core Mobile-Friendliness Checklist

Once you know something's off, work through these five checks in order — they cover the vast majority of real-world mobile usability failures.

• Viewport meta tag present and correct. Without width=device-width, initial-scale=1, mobile browsers render a desktop-width layout and shrink it, causing every other item on this list to fail. If you're unsure what the tag controls, this explainer covers what viewport settings govern and why they matter.
• Readable font size without zooming. Body text below roughly 12px on mobile forces users to zoom, one of the fastest ways to trip a usability flag.
• No horizontal scroll or content overflow. Images, tables, or fixed-width elements that spill past the viewport edge break the reading experience and often stem from the same viewport misconfiguration above.
• Tap targets sized and spaced correctly. Buttons and links need enough size and breathing room for a thumb to hit them accurately; current guidance puts minimum comfortable tap target size and spacing at specific thresholds that a lot of themes still miss. Tap target problems overlap heavily with accessibility issues, so it's worth reviewing what an accessibility checker actually catches.
• Fast mobile load time, especially Largest Contentful Paint. A visually complete, tap-friendly page still fails users if the main content takes seconds to render; mobile LCP is measured separately from desktop and typically runs slower on real-world connections.

Checking Mobile-Friendliness at Scale

All of this works fine for one page. It falls apart the moment you're responsible for thirty landing pages, a client's e-commerce catalog, or an agency portfolio spanning a dozen domains. Checking each URL individually through Search Console's URL Inspection tool means clicking through the same workflow dozens or hundreds of times, then manually reconciling notes across pages — not something you want to redo every sprint.

This is where a site-wide mobile audit earns its keep. Rather than inspecting one URL at a time, an automated mobile-friendly checker crawls the whole site and consolidates viewport configuration, tap target spacing, font sizing, overflow issues, and mobile load speed into a single report per page. If your workflow already includes crawling a site for other SEO purposes, it's worth understanding how a site crawl works and how to run your own so mobile checks can piggyback on that same pass instead of becoming a separate manual task.

Optimevra's audit tool is built around exactly this gap: instead of bouncing between Search Console, Lighthouse, and PageSpeed Insights and reconciling three different scoring systems, you get one fix-ready report that flags viewport errors, tap target problems, layout overflow, and speed issues together, page by page, across an entire site.

Manually stitching together Search Console, Lighthouse, and PageSpeed Insights for every page gets old fast — especially once you're managing more than a handful of URLs. Run a free audit with Optimevra's live demo to see a consolidated mobile-friendliness report in minutes, or check Optimevra's pricing if you're evaluating it for ongoing use across a team or agency. Start at Optimevra.

Frequently Asked Questions

Does Google still have a mobile-friendly test tool?

No. Google retired the standalone Mobile-Friendly Test tool in December 2023 along with the mobile usability report in Search Console. Google now points webmasters toward Lighthouse, PageSpeed Insights, and the URL Inspection tool as replacements, though none produces the same single pass/fail verdict the old tool gave.

How do I know if my website is mobile friendly if Google's test is gone?

Use Search Console's URL Inspection tool to see how Googlebot Smartphone rendered the page, then confirm manually by pinch-zoom testing on an actual phone and resizing your browser to phone width. If text is unreadable without zooming or content overflows horizontally, the page has a mobile usability problem.

What is considered mobile-friendly in 2026?

A mobile-friendly page has a correctly configured viewport meta tag, readable text without zooming, no horizontal scroll, adequately sized and spaced tap targets, and fast mobile load speed measured through metrics like Largest Contentful Paint. These criteria replace the old binary pass/fail check with a set of measurable thresholds.

Does mobile-friendliness still affect SEO rankings?

Yes, because mobile-first indexing means Google predominantly indexes and ranks pages based on their mobile version. A poor mobile experience can suppress rankings across both mobile and desktop search results, not just mobile search.

What's the difference between mobile-friendly and responsive design?

Responsive design is a technical approach where layout adapts to screen size, while mobile-friendly describes the actual usability outcome. A site can be built responsively and still fail mobile-friendliness through issues like cramped tap targets, tiny fonts, or content that overflows on specific devices.

Can a page be mobile-friendly but still fail Core Web Vitals?

Yes. A page can have a correct viewport, readable fonts, and well-spaced tap targets while still loading slowly on mobile connections, causing it to fail Core Web Vitals thresholds like Largest Contentful Paint. Mobile usability and Core Web Vitals measure different things and need to be checked separately.