How to use the Mobile-Friendly test
- 1Enter the page address and press Test page to run the HTML checks from our server.
- 2Read Mobile checks: viewport tag, zoom settings, page language, embeds and image dimensions.
- 3Press Run Lighthouse mobile test for font-size results, a mobile performance score and a screenshot.
- 4Optionally choose a Device size and press Show preview to see the page at that width in your own browser.
Example: a viewport that blocks zoom
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
Warning Viewport meta tag user-scalable=no blocks pinch zoom; maximum-scale=1 limits zoom. Use width=device-width, initial-scale=1 and allow zooming (WCAG 1.4.4).
What mobile-friendly means today
A mobile-friendly page renders at the phone's width without sideways scrolling, uses text that's readable without zooming, has buttons and links big enough to tap, and still lets people zoom in when they need to. Since Google switched to mobile-first indexing, it indexes and ranks the mobile version of every page, so content or links missing on mobile are missing for Google too.
Viewport, font size and tap targets
- Viewport:
<meta name="viewport" content="width=device-width, initial-scale=1">tells phones to use their real width. Without it, they render a 980 px desktop layout and shrink it.user-scalable=noormaximum-scale=1block zooming, which fails WCAG 1.4.4. - Font size: Lighthouse's "legible font sizes" audit checks that most text is at least 12 px; 16 px body text is a comfortable default.
- Tap targets: WCAG 2.5.8 asks for targets of at least 24 × 24 CSS px or enough spacing; 44–48 px is a common design guideline. Newer Lighthouse versions no longer report tap targets, so the tool shows the check only when Lighthouse returns it.
Screenshots on common phone sizes
The Lighthouse test returns a screenshot taken on Google's emulated phone, which works even when a site refuses to be embedded. The phone-size preview loads the page in your own browser at a phone's width (iPhone SE 375 px, iPhone 15 393 px, Pixel 8 412 px, Galaxy S24 360 px). It shows the responsive layout but isn't a different browser or a touch device, and many sites forbid embedding; the tool warns when the site's headers will block it.
Google's retired Mobile-Friendly Test and what replaced it
Google retired its Mobile-Friendly Test tool, its API and Search Console's Mobile Usability report in December 2023, pointing people to Lighthouse instead. This page combines the checks it covered: the viewport tag and zoom settings from the HTML (from our server) and Lighthouse's mobile audits, mobile performance score and screenshot (from PageSpeed Insights). For a deeper look, the device mode in Chrome's developer panel emulates phones on your own computer.
Fixing common mobile problems
- Content wider than the screen: fixed-width containers, wide tables or images without
max-width: 100%. - Tiny text: set a base font size of 16 px and use relative units.
- Crowded links: add padding to menu items and buttons.
- Pop-ups covering content: intrusive interstitials on mobile are a page-experience problem.
- Slow loading: check the website speed test on the mobile setting and the page size checker.
What happens to the address I enter?
This tool sends the address you enter to Google PageSpeed Insights to run a Lighthouse mobile test, only when you press Run Lighthouse mobile test (the HTML checks run on our server). Their privacy policy applies to that request. Some checks also request the page from our server, which doesn't store what it fetches. We don't store the results.