Transparent Per-Check Verdicts
Instead of one opaque score, every check — viewport, layout, tap targets, and field data — returns its own pass, warning, or fail with a plain-English reason and fix.
Mobile-Friendly Test for Viewport, Layout, and Tap Targets
TL;DR: Mobile-Friendly Test checks check viewport, layout, tap targets, and phone crux field data. so you can confirm the current issue, understand when it matters, and move directly into the next fix without leaving the browser.
Replace Google's retired Mobile-Friendly Test with a live, transparent usability check.
Actualizado
Loading tool interface...
Viewport meta tag validation Fixed-width and responsive layout detection Font size and tap-target heuristics Real-user phone CrUX field data Device-frame rendering preview
What does Mobile-Friendly Test do?
This Mobile-Friendly Test fetches your page, inspects its viewport meta tag, scans for fixed-width and non-responsive layout patterns, evaluates font and tap-target legibility, and pulls real-user phone field data from the Chrome UX Report. It returns a pass, warning, or fail verdict per check plus a device-frame preview so you can see how the page is likely to render on a phone.
Why it matters for SEO: Google indexes the web mobile-first, so the mobile version of your page is what gets crawled and ranked. A missing viewport tag, a fixed-width desktop layout, or text that is too small to read forces phone users to pinch, zoom, and scroll sideways — exactly the friction that depresses mobile rankings and conversions.
Fills the Google gap: Google retired its standalone Mobile-Friendly Test and the Mobile Usability report in Search Console, leaving teams without a quick, dedicated checker. This tool restores that workflow with transparent, rule-by-rule reasoning instead of a single opaque verdict.
Pre-launch QA: Validate new templates, landing pages, and CMS changes before they ship to confirm the viewport is configured correctly and no fixed-width blocks slipped into the markup.
Debugging mobile drops: When mobile rankings or engagement slide, run the page to isolate whether the cause is a usability regression (viewport, layout, tap targets) or a performance regression (phone Core Web Vitals from CrUX).
When should you use Mobile-Friendly Test?
Mobile-Friendly Test is most useful when you need a direct answer on a live URL or draft before you change templates, ship content, or rerun a wider audit.
Cómo utilizar esta herramienta
- 1 Enter the page URL you want to test.
- 2 Run the test to fetch the page and analyze it.
- 3 Review the pass/warn/fail verdict for each mobile check.
- 4 Fix flagged issues, then rerun to confirm a clean pass.
What should you do next?
After confirming mobile usability, dig into mobile performance with the Core Web Vitals Checker and verify your viewport and meta setup with the Meta Tag Checker. Then move to the related checks below to confirm the fix on the live canonical page.
Lo que obtienes
Real Phone Field Data
Pulls PHONE form-factor CrUX so you see how real Chrome users experience LCP, INP, and CLS on the page, not just a synthetic guess.
Device-Frame Preview
A 360px phone frame visualizes whether your content fits the screen or overflows and forces horizontal scrolling on mobile.
Frequently Asked Questions
Respuestas sobre Mobile-Friendly Test
No, Google retired its standalone Mobile-Friendly Test and the Search Console Mobile Usability report in late 2023. This tool fills that gap by checking the same signals — viewport configuration, responsive layout, and legible tap targets — and adding real-user phone field data, so you keep a dedicated mobile usability workflow.
A mobile-friendly page has a correct viewport meta tag (width=device-width, initial-scale=1), a fluid layout with no large fixed-pixel widths, and text that is legible without zooming. This test evaluates each of those signals and flags zoom-blocking viewports, fixed-width blocks that cause horizontal scrolling, and sub-12px fonts that hurt readability and tap accuracy.
A viewport fails when the tag is missing or omits width=device-width, and warns when it disables zoom with user-scalable=no or maximum-scale=1. Without device-width the page renders at desktop width on phones, and blocking zoom is a mobile usability and accessibility problem, so the tool flags both with the exact directive to fix.
It shows how real Chrome users on phones experience your page across LCP, INP, and CLS, using Google's Chrome UX Report. When URL-level data is not available the tool falls back to origin-level data, and if no field data has accumulated yet it says so rather than failing — common for newer or lower-traffic pages.