Mobile Friendly Test
Free Mobile-Friendly Test to check any URL for viewport, font size, tap targets, and responsive design with a scored report and fixes.
Share on Social Media:
The Mobile-Friendly Test checks how well any web page works on phones — analyzing the viewport tag, font sizes, tap targets, and more — then gives you a scored report with specific fixes. With Google ranking the mobile version of your site first, this is one of the most important checks you can run. Free, instant, and no signup required.
Your Mobile Page Is Your SEO
This is the reality of search in 2026: through mobile-first indexing — Google's default since 2021 — the search engine primarily crawls and ranks the mobile version of your page, even for desktop searches. If your phone experience is broken, your rankings suffer everywhere. Add that mobile drives over 60% of web traffic, and a page that's hard to use on a phone is losing both rankings and the majority of its audience at once.
How to Use It
- Enter your URL.
- Run the test to analyze the mobile signals.
- Fix the issues, starting with the viewport tag.
Why a Standalone Test Now
Here's a fact many people miss: Google retired its own Mobile-Friendly Test, the Mobile Usability report, and the testing API on December 1, 2023, directing users to Lighthouse and Search Console instead. That left a gap for quick, per-URL checks — which this tool fills. You get instant, scored feedback with actionable fixes on any page, without needing Search Console access or having to verify site ownership. Test a competitor's page as easily as your own.
The Single Most Important Fix: The Viewport Tag
If a page fails just one thing, it's usually this. The viewport meta tag — <meta name="viewport" content="width=device-width, initial-scale=1"> — tells mobile browsers to render at the device's screen width rather than a desktop width. Without it, the page loads zoomed out with tiny, unreadable text, and nothing else you do matters until it's fixed. Adding this one line is often the highest-impact mobile improvement available.
The Checks That Matter
| Signal | The rule |
|---|---|
| Viewport tag | width=device-width, initial-scale=1 |
| Font size | At least 16px body text; never below 12px |
| Tap targets | At least 48×48px with ~8px spacing |
| No horizontal scroll | Content must fit the viewport width |
| Responsive images | Use srcset so phones don't load huge images |
Tap Targets and Readable Text
Two of the most common failures are easy to fix. Tap targets — buttons and links — should be at least 48×48 CSS pixels with roughly 8 pixels of spacing, so fingers hit them cleanly without mis-taps. Body text should be at least 16 pixels so readers never have to pinch-zoom. Small, crowded elements frustrate mobile users and quietly cost you conversions.
An Accessibility Warning: Don't Disable Zoom
Avoid the tempting shortcut of user-scalable=no to lock zoom. It violates WCAG accessibility guidelines because users with low vision depend on pinch-to-zoom, and it's flagged as an accessibility error. Always use the standard viewport tag and leave zoom enabled — good for users and for your audit score alike.
Mobile-Friendly vs. Mobile-Optimized
An honest caveat: passing this test is a strong baseline, not the finish line. Google also weighs Core Web Vitals — loading (LCP), interactivity (INP), and visual stability (CLS) — as part of page experience. Aim to be genuinely mobile-optimized: fast, stable, and pleasant to use, not merely technically passing. As a bonus, the same fast, clean, semantic HTML that wins on mobile also helps the AI search crawlers (from AI Overviews to other assistants) that fetch pages much like mobile Googlebot does. Free, with no signup.
Mobile-Friendly Test FAQs
What does a mobile-friendly test check?
It analyzes a page's HTML for the signals that determine how well it works on phones: the viewport meta tag, font sizes, tap target sizes and spacing, content that overflows the screen, responsive media queries, fixed-width elements, image responsiveness, and render-blocking scripts. It then flags the issues that would make the page hard to read or use on a mobile device.
Didn't Google have its own mobile-friendly test?
Yes, but Google retired its official Mobile-Friendly Test, the Mobile Usability report, and the testing API on December 1, 2023, pointing users toward Lighthouse and Search Console instead. That's exactly why a standalone mobile-friendly test is useful now — it gives you instant, per-URL feedback with actionable fixes, without needing Search Console access or site ownership verification.
Why does mobile-friendliness matter so much for SEO?
Because of mobile-first indexing, which has been Google's default since 2021: Google primarily crawls and ranks the mobile version of your page, even for desktop searches. If your mobile experience is broken or has less content than desktop, your rankings suffer everywhere. With mobile driving over 60% of web traffic, an unfriendly mobile page also loses most of your actual audience.
What is the viewport meta tag and why is it the most important fix?
The viewport tag — meta name="viewport" content="width=device-width, initial-scale=1" — tells mobile browsers to render the page at the device's screen width instead of a desktop width. Without it, your page appears zoomed out with tiny, unreadable text. It's the single most important mobile-friendliness element, and adding it is usually the highest-impact fix you can make.
What are the rules for tap targets and font size?
Tap targets (buttons and links) should be at least 48×48 CSS pixels with about 8 pixels of spacing between them, so fingers can hit them without mis-taps. Body text should be at least 16 pixels and never below 12, so readers don't have to pinch-zoom. Both are common, easy-to-fix failures that significantly affect mobile usability.
Should I disable zoom with user-scalable=no?
No. Setting user-scalable=no to prevent pinch-to-zoom violates accessibility guidelines (WCAG) because users with low vision rely on zoom, and it's flagged as an accessibility error. Always use the standard viewport tag with width=device-width and initial-scale=1, and leave zoom enabled.
Does passing the test mean my mobile SEO is done?
Not entirely. Passing a mobile-friendly test is a strong baseline, but Google also weighs Core Web Vitals — loading (LCP), interactivity (INP), and visual stability (CLS) — as part of page experience. Aim to be mobile-optimized, not just mobile-friendly: fast, stable, and genuinely pleasant to use, not merely technically passing. The same fast, clean HTML also helps AI search crawlers that behave like mobile Googlebot.
Is the mobile-friendly test free?
Yes, it's free with no signup. Enter any URL to get a scored mobile-friendliness audit with specific, prioritized fixes.