Google retired its Mobile-Friendly Test: how to check your site's mobile-friendliness now
TL;DR: Google sunset the Mobile-Friendly Test tool, its API and the Search Console Mobile Usability report on 1 December 2023. Mobile usability still matters for how your pages are evaluated, but there is no longer a single pass or fail screen. To check a site today, run Lighthouse (built into Chrome and PageSpeed Insights), inspect a live URL in Search Console, and test on a real phone. This guide gives the checklist, the usual WordPress fixes, and where a quick first-pass tool fits.
What Google actually retired
On 1 December 2023, Google announced it was sunsetting three things together: the Mobile Usability report in Search Console, the standalone Mobile-Friendly Test tool, and the Mobile-Friendly Test API. The old test page now redirects to Lighthouse.
Google's stated reasoning was that mobile usability still matters, but that many other robust tools for evaluating it have emerged. So the tool went away, and the guidance did not.
That is why a search for "mobile friendly test" still returns plenty of results. People are looking for a replacement that behaves the way the old one did: paste a URL, get a verdict.
Why mobile-friendliness still matters
Google evaluates pages using the mobile version of your content. If the phone version is cramped, slow or missing content that the desktop version has, that is the version that gets judged.
For an Indian audience the point is sharper. Most visitors to a typical small-business or ecommerce site arrive on a mid-range Android phone over a mobile connection. A layout that merely shrinks the desktop design can pass a glance test and still lose customers on that device.
Mobile usability also overlaps with the page experience signals covered in Core Web Vitals in 2026: layout shifts, tap responsiveness and loading speed are all more visible on a phone.
What to use instead
No single tool replaces the old test. Three together cover it.
1. Lighthouse in Chrome DevTools. Open your page in Chrome, press F12, open the Lighthouse tab and choose the Mobile device option. It scores performance, accessibility and best practices and lists specific failures. This is the tool Google's own redirect points to.
2. PageSpeed Insights. It runs Lighthouse for you from a URL and, when your site has enough traffic, shows real-user field data. The difference between the lab score and the field data is covered in GTmetrix vs PageSpeed Insights.
3. URL Inspection in Search Console. Inspect a live URL and view the rendered page. This shows what Googlebot actually sees, including whether scripts, styles or images were blocked from loading, which is a common hidden cause of a broken mobile render.
Add a real phone. Emulation catches layout problems, but it cannot reproduce a slow processor, a flaky connection or a cramped on-screen keyboard.
For a quick first pass before the deeper checks, HostCloud has a free mobile-friendly test tool. Use it to spot obvious problems, then confirm anything it flags with the tools above.
The manual checklist
Most mobile failures fall into a short list. Check each on a real phone.
- Viewport meta tag. The page should declare
width=device-width, initial-scale=1. Without it, phones render a zoomed-out desktop layout. - No sideways scrolling. If the page scrolls horizontally at phone width, something is wider than the screen, usually a table, an image or a fixed-width embed.
- Readable text without zooming. Body text around 16px is a sensible floor.
- Tap targets with room. Buttons and links should be large enough to hit with a thumb and not packed against each other. Around 48px is the common guide.
- Same content as desktop. Text, images and structured data hidden on mobile may not be counted.
- No blocking pop-ups. A full-screen overlay that covers content right after arrival is both a usability problem and a ranking risk.
- Crawlable resources. CSS, JavaScript and images must not be blocked in robots.txt, or the rendered page will look broken to Google.
Common failures and the WordPress fix for each
| Problem | Typical cause on WordPress | Fix |
|---|---|---|
| Page wider than the screen | Fixed-width table, embed or image | Wrap tables in a scroll container, set max-width: 100% on media |
| Text too small | Theme or page-builder font settings | Set a 16px base size and test on a phone |
| Buttons too close together | Menu items or footer links packed tight | Increase padding and spacing on mobile breakpoints |
| Slow, janky first load | Oversized images, heavy scripts | Resize and compress images, see WebP vs JPG vs PNG and lazy loading |
| Content missing on mobile | "Hide on mobile" settings in a builder | Show the same core content on every device |
| Layout jumps while loading | Images without dimensions, late-loading ads or fonts | Set width and height attributes, reserve space for embeds |
| Intrusive pop-up on arrival | Marketing plugin on its default timing | Delay it, shrink it, or trigger it on exit or scroll |
If the theme itself is the problem, a lighter one is often a faster fix than patching a heavy one. The choice of editor and theme is compared in Elementor vs Gutenberg, and wider speed work for Indian visitors is in how to speed up WordPress for Indian visitors.
A repeatable five-minute mobile check
Run this after any theme, plugin or design change.
- Open the homepage, one product or service page and one blog post on a real phone.
- Scroll sideways. Nothing should move.
- Tap the main menu, the primary button and the search icon. Each should respond on the first tap.
- Fill in the contact form and check the on-screen keyboard does not hide the submit button.
- Run the same three URLs through PageSpeed Insights on mobile and note the failures.
- Inspect one URL in Search Console and confirm the rendered screenshot looks right.
Keep a short log of the results. A change in score after an update points straight at the cause.
FAQs
Is there an official Google replacement for the Mobile-Friendly Test?
No. Google retired the tool, its API and the Search Console Mobile Usability report together and redirected the old page to Lighthouse. Lighthouse, PageSpeed Insights and Search Console's URL Inspection are the practical combination.
Does Google still care whether my site is mobile-friendly?
Yes. Google said mobile usability remains part of its page experience guidance. It simply stopped offering a dedicated tool for it.
Why did my Search Console Mobile Usability report disappear?
Google removed it in December 2023 along with the test tool. Use Core Web Vitals reports and URL Inspection to find page-level problems now.
Can I trust a third-party mobile-friendly checker?
Use it as a first pass. Many run a few basic checks and return a quick verdict, which is useful for catching obvious problems. Confirm anything important with Lighthouse and a real device, because those test what a user and Googlebot actually see.
Is a responsive theme enough to be mobile-friendly?
It is a good start but not a guarantee. Plugins, embeds, pop-ups, large images and page-builder settings can still break the mobile experience on an otherwise responsive theme.
Does mobile-friendliness affect my search ranking directly?
It feeds into page experience and into how well your content renders for Google. A page that is hard to use on a phone loses visitors, which hurts results even before you consider rankings.
Why does PageSpeed Insights show a different score from Lighthouse in Chrome?
PageSpeed Insights runs Lighthouse on Google's servers under a set network and device profile, and may add real-user data. Chrome runs it on your own machine and connection. Expect some variation and compare trends, not single numbers.
How often should I recheck mobile usability?
After every theme, plugin or layout change, and at least quarterly for a site that rarely changes. Plugin updates can alter mobile behaviour without any change to your content.
Conclusion
The Mobile-Friendly Test is gone, but the checks it performed are still worth doing. Combine Lighthouse, PageSpeed Insights and Search Console's URL Inspection, then confirm on a real phone, and you have a more thorough test than the old one gave.
Fast mobile pages also depend on the server behind them. HostCloud's hosting is built for Indian visitors on real-world connections. See the plans at https://hostcloud.in.
Sources: