Mobile-friendly test. Live PSI mobile audit.
Enter a URL. The test runs Google PageSpeed Insights against the mobile preset, parses the four mobile-usability audits (viewport, tap-targets, font-size, content-width), and returns a verdict plus per-issue fix.
Enter a URL. The test runs Google's PageSpeed Insights v5 API in mobile mode, parses four mobile-usability audits (viewport, tap-targets, font-size, content-width), and returns a pass/fail verdict per audit with fix recommendations. Typical run: 25-45 seconds.
Sources used
- Google PageSpeed Insights v5 API — runs the underlying Lighthouse mobile audit
- Google Search Central — mobile-first indexing
- MDN viewport meta tag reference
- WCAG 2.5.5 Target Size (Minimum) — 48×48px tap-target rule
- web.dev mobile-friendly guide
The URL is sent only to Google's PageSpeed Insights API. Nothing is logged on Digital Heroes servers. Recent tests use browser localStorage and stay on your device.
Privacy: URL is sent only to Google PSI. Digital Heroes does not log it.
Mobile-first is the only SERP.
Google completed mobile-first indexing in October 2023 — every site is now indexed by Googlebot Mobile only. Mobile-unfriendly pages drop in mobile SERPs, which is 65%+ of US queries. The four checks the mobile-friendly test runs are pass/fail: viewport meta tag, tap targets ≥ 48×48px, body font ≥ 12px, content fits viewport. Failing any one is a ranking cost. The tool above runs the audit live via Google PSI mobile preset and surfaces the per-audit verdict.
Three rules for mobile-friendly. One, the viewport meta tag is non-negotiable: <meta name="viewport" content="width=device-width, initial-scale=1"> in every page's head. Two, tap targets must be 48×48 CSS pixels minimum (WCAG 2.5.5 Level AAA) — never make icons less than 48px the entire tap surface; pad them. Three, body font 16px is the modern default; never go below 14px (the test's 12px is the absolute legacy floor).
Tools in the same cluster: Lighthouse Score Checker for the broader 4-category grade. Core Web Vitals Checker for the LCP / INP / CLS view (also mobile-first by default). Website Audit for the composite scorecard.
Five answers.
What does mobile-friendly mean for SEO in 2026?
Google switched to mobile-first indexing in 2019, then completed the rollout in October 2023 — every site is now indexed by Googlebot Mobile only. Mobile-unfriendly pages rank significantly lower in mobile SERPs (the dominant SERP, since 65%+ of US queries are mobile). The four checks Google's mobile-friendly test runs: viewport meta tag present, tap targets at least 48×48px, body font at least 12px, content fits in viewport (no horizontal scroll). All four are pass/fail; failing any one costs ranking.
What does the viewport audit check?
The viewport meta tag tells the browser how to scale the page for the device width. Pages without a viewport tag render at 980px and zoom out to fit, which makes text tiny and tap targets unusable on mobile. The correct tag: <meta name="viewport" content="width=device-width, initial-scale=1">. The audit fails if viewport is missing or if it sets user-scalable=no (which blocks accessibility zoom).
Why 48×48px tap targets?
48×48 CSS pixels (~9mm physical on most mobile displays) is the WCAG 2.5.5 Level AAA target size minimum and matches the average human fingertip. Smaller tap targets cause mis-taps and adjacent-button hits. The audit fails if any focusable element is smaller than 48×48 OR if multiple smaller targets are within 8px of each other (the spacing variant of the rule). The fix: increase padding on links, buttons, form controls; never use raw 16px icons as the entire tap surface.
Mobile-friendly test vs Lighthouse mobile score?
The mobile-friendly test is a binary pass/fail across 4 specific mobile-usability audits — it answers 'is this page indexable by Google as mobile-friendly?'. Lighthouse mobile score (0-100) is a graded performance score across many audits including the mobile-usability ones plus LCP/CLS/INP/TBT performance. Use mobile-friendly test for the SEO-eligibility check; use Lighthouse for the broader performance grade. Both run via Google PageSpeed Insights API; this tool focuses on the mobile-usability subset.
Does this tool save my data?
The URL you enter is sent only to Google's public PageSpeed Insights API for the mobile audit. Nothing is logged on Digital Heroes servers. The 'recent tests' panel uses your browser's localStorage and stays on your device only.
Failing mobile audits?
Our mobile + web development engagements ship fully mobile-first builds — viewport, tap targets, font legibility, content-width fit baked in from kickoff. Most mobile-friendly fixes ship in under 1 week.
Published · Last updated .