Mobile-Friendly Test

Enter a page address to see it on a phone-sized screen and check the viewport, content width, text size and tap targets.

The addresses you enter are sent to our server to run the check. We don't store them or the results.

How to use the mobile-friendly test

Paste a page address and press Test page. The tool downloads the page as an iPhone would request it, renders it in a 375-pixel-wide frame (the width of a typical phone screen), and measures what a visitor would experience. You get a verdict, a list of problems with suggested fixes, and a live phone-sized preview you can scroll through.

What is checked

  • Viewport tag: without <meta name="viewport" content="width=device-width, initial-scale=1">, phones render the page at desktop width and shrink it. This is the most common reason a site fails.
  • Content width: any element wider than the screen forces sideways scrolling. The test names the widest elements so you can find them in your code.
  • Text size: the share of text that is at least 12 pixels on the phone. Below 60 percent, the page is hard to read without zooming.
  • Tap targets: buttons and links smaller than 24 by 24 pixels, the minimum in the WCAG 2.2 accessibility guidelines. Links inside sentences are excluded.
  • Zoom: whether the viewport blocks pinch-to-zoom, which makes pages hard to use for people with low vision.
  • Other issues: plugin content that phones can't show, missing HTTPS and very heavy HTML.

Why this test exists

Google retired its own Mobile-Friendly Test and the Mobile Usability report in Search Console in December 2023. Mobile-friendliness still matters just as much: Google now crawls and indexes websites with its smartphone crawler, so the mobile version of a page is the version that gets ranked. Most visitors to most sites are also on phones, and a page that needs pinching and zooming loses them quickly.

How to fix common problems

Content wider than the screen: the usual causes are images, tables, videos or embedded widgets with a fixed pixel width. Add max-width: 100%; height: auto; to images and videos, and wrap wide tables in a container with overflow-x: auto.

Text too small: set body text to at least 16 pixels and avoid sizes below 12 pixels even for footnotes and menus.

Small tap targets: give buttons, menu items and icon links enough padding to make them at least 24 by 24 pixels, and ideally 44 by 44 pixels, with space between neighbouring links.

Limits of the test

For safety, the preview runs with JavaScript turned off. Pages that build their layout or content with JavaScript, such as some single-page apps, may look emptier here than on a real phone. The measurements are still a reliable check of the page's HTML and CSS, which is what most mobile problems come from.

Frequently asked questions

Did Google shut down its Mobile-Friendly Test?

Yes. Google retired the Mobile-Friendly Test tool and the Mobile Usability report in December 2023. Lighthouse in Chrome DevTools and tools like this one are the common replacements.

Is mobile-friendliness a ranking factor?

Google uses mobile-first indexing, so it ranks the mobile version of your pages. Page experience, including mobile usability, is also one of many signals Google considers.

What is the viewport meta tag?

A meta tag named viewport in the page's head, usually set to width=device-width, initial-scale=1. It tells phones to match the page width to the screen. Without it, phones show a shrunken desktop layout.

Why does the preview look different from my phone?

The preview runs without JavaScript and uses a 375-pixel width. Content loaded by JavaScript, cookie banners and sliders may not appear, and your own phone may have a different screen width.

Last updated