For years, the answer to “is my website mobile friendly?” was simple: paste your URL into Google’s Mobile-Friendly Test, wait a few seconds, get a green tick or a list of problems. Millions of site owners used it. Then, in December 2023, Google switched it off.
Not just the tool. Google retired three things at once:
- The Mobile-Friendly Test at search.google.com/test/mobile-friendly
- The Mobile-Friendly Test API that many SEO platforms used under the hood
- The Mobile Usability report inside Google Search Console
If you have bookmarked the old test, it is gone. This post covers what Google recommends now, what each alternative actually gives you, and the fastest way to run the old-style check today.
Why Google retired the Mobile-Friendly Test
Google’s reasoning was straightforward: mobile-friendliness stopped being a feature and became a baseline. When the test launched in 2014, responsive websites were still the exception. A decade later, most themes, builders, and frameworks are responsive by default, and Google’s evaluation of page experience moved on to Core Web Vitals, which measure how fast and stable a page feels, not just whether it technically fits a phone screen.
So Google consolidated. Instead of a standalone yes/no test, it now expects you to use Lighthouse for audits and the Core Web Vitals report for real-user data.
Here is the catch: none of the official replacements actually replicate what the old tool did.
What Google offers instead (and what each one lacks)
| Option | What it gives you | The catch |
|---|---|---|
| Lighthouse (Chrome DevTools) | Deep technical audit: performance, accessibility, SEO, best practices | Developer-oriented. You need DevTools open and some patience to interpret the report |
| PageSpeed Insights | Speed scores and Core Web Vitals from lab and field data | No simple “mobile friendly: yes/no” verdict anymore |
| Search Console (Core Web Vitals report) | Real-visitor experience data for your pages | Only works for sites you own and verified. No per-URL usability verdict |
| Bing Webmaster Tools | Still has a mobile friendliness test | Requires a Microsoft account sign-in |
Notice what is missing from every row: the original workflow. Paste any URL, including a competitor’s, and get an instant plain-English verdict without signing in or opening developer tools.
The fastest replacement: run the check here
That gap is exactly why we built our free Mobile-Friendly Test. It works the way Google’s tool did:
- Paste any public URL, yours or anyone else’s
- Get a mobile-friendliness score in seconds
- See a plain-English list of issues, ordered by impact
It checks the same fundamentals the retired test covered: the viewport meta tag, readable font sizes, tap target sizing, and content that overflows the screen. It also checks things the old tool never did, because the mobile web moved on: responsive images with srcset, lazy loading, render-blocking scripts, zoom restrictions that hurt accessibility, and touch icons.
No signup, no limits, nothing stored.
What to actually fix (the checks that matter)
Whichever tool you use, mobile-friendliness in 2026 comes down to a short list:
- Viewport meta tag. Without
<meta name="viewport" content="width=device-width, initial-scale=1">, phones render your page zoomed out at desktop width. This is still the single most common and most damaging failure. - Readable text. Body text at 16px or larger. If visitors pinch-zoom to read, you failed.
- Tap targets. Buttons and links at least 48x48px with breathing room. Fat-finger misses cost conversions.
- No horizontal scroll. Fixed-width images, tables, and divs wider than the screen break the layout. Use max-width: 100% and let tables scroll inside their own container.
- Fast enough to feel instant. Mobile users are on slower processors and networks. Compress images, defer non-critical JavaScript, and lazy-load below-the-fold media. This is where mobile-friendliness meets Core Web Vitals.
For the design side of this, our guide to responsive, mobile-first web design covers how to build pages that pass these checks by default.
Does mobile-friendliness still affect rankings?
Yes, just not as a labeled, standalone signal anymore. Google uses mobile-first indexing: the mobile version of your page is the one that gets crawled, indexed, and ranked. A page that is broken on mobile tends to fail Core Web Vitals, frustrate visitors into bouncing, and underperform in search as a result.
In other words: Google retired the test, not the expectation. The sites that treated the green tick as a finish line are exactly the ones losing ground now.
If your site fails the check and you would rather have someone fix it than read documentation, that is literally what we do: website redesign and speed optimization, mobile-first by default.
