Skip to content
Devtoolry
Sign InJoin for Free

Mobile-Friendly Test

Test if a page is mobile-friendly now that Google retired its own test: viewport, content wider than the screen, small text, plugins and Googlebot smartphone access.

Something not working, or missing a feature? Send feedback

About the Mobile-Friendly Test

The Mobile-Friendly Test checks whether a page works on a phone, with the checks Google's own Mobile-Friendly Test made before Google retired it in December 2023. It loads the page as Googlebot smartphone and reads the viewport tag, the page's stylesheets and its HTML. It reports content wider than the screen, text that is too small, disabled zoom, plugins phones cannot run, and CSS or JavaScript that robots.txt hides from Google. Each area is scored, with a plain verdict at the top and what to fix.

Our server requests the URLs you enter, like a crawler: it reads the response without running the page's scripts, and the analysis runs in your browser. Up to 6 of the page's stylesheets are read the same way. The URLs and results are not stored.

How to use the Mobile-Friendly Test

  1. Enter the page address. Googlebot smartphone is the default; pick Safari (iPhone) to see what a visitor's phone gets.
  2. Press Test page and read the verdict: mobile-friendly, or the failed checks that stop it.
  3. Fix failures first: a missing viewport tag, fixed-width containers, blocked CSS or JavaScript.
  4. Open the Page Speed Checker from the report for mobile Core Web Vitals and Lighthouse's tap-target checks.

Common mistakes

  • Disabling zoom. user-scalable=no or maximum-scale=1 in the viewport stops people with poor eyesight from zooming in. Remove them; a responsive page does not need them.
  • Blocking CSS in robots.txt. Old WordPress robots.txt files block /wp-includes/ or /wp-content/. Google then renders the page without styles and judges a broken layout. Allow them.
  • Fixed-width containers. A wrapper with width: 960px forces sideways scrolling on every phone. Use max-width: 960px with width: 100% instead.

Works well with the Mobile-Friendly Test

Frequently asked questions

Where did Google's Mobile-Friendly Test go?

Google retired the Mobile-Friendly Test, its API and the Mobile Usability report in Search Console on 1 December 2023, and pointed people to Lighthouse in Chrome. Mobile-friendliness still matters: Google crawls and indexes every site with its smartphone crawler (mobile-first indexing). This test makes the same checks without a Google account.

What makes a page mobile-friendly?

A viewport tag with width=device-width, a layout that fits a 360–430px screen without sideways scrolling, body text of about 16px, tap targets with enough space, no Flash or other plugins, and no pop-ups that cover the content. Responsive design (one HTML with CSS media queries) does all of this for every screen size.

Why does it say "no viewport meta tag"?

Without <meta name="viewport" content="width=device-width, initial-scale=1"> in the <head>, phones assume a 980px desktop page and shrink it to fit, so the text becomes tiny. Add the tag to your theme's header template; it is one line.

Does it run JavaScript?

No. It reads the HTML and up to six stylesheets as the server sends them, which is what Google gets first. If your layout is built by JavaScript, also run the Page Speed Checker: Lighthouse renders the page in a real phone-sized browser and measures tap targets.

Is mobile-friendliness a ranking factor?

Google uses page experience signals, and it indexes the mobile version of every page. A page that is hard to use on a phone keeps fewer visitors, and content missing from the mobile version is missing from Google. There is no separate "mobile-friendly" label in results any more.

Related tools