Mobile Friendly Test (HTML signals)
Paste one URL to check mobile HTML signals: viewport meta, zoom lock, lang, charset, wide fixed widths in inline CSS, tiny font-size, and srcset on images. It reads the HTML response only — not Google's retired Mobile-Friendly Test, not external stylesheets.
- Enter page URL
- Review mobile checks
- Fix mobile blockers
- Browser-based — no install
- Instant results
By Faisal YUpdated
What this mobile friendly test checks
This tool fetches one public URL and scores common mobile HTML signals from the response body. It looks at the viewport meta tag, whether pinch-zoom is blocked, the html lang attribute, charset declaration, fixed pixel widths over 500px inside inline styles or <style> blocks, font-size under 12px in that same CSS, and whether <img> tags use srcset.
It does not execute JavaScript, read external stylesheets, measure tap targets, or call Google. Google retired its public Mobile-Friendly Test in December 2023, and retired the Search Console Mobile Usability report the same month. Use PageSpeed Insights, Lighthouse, and the Core Web Vitals report in Search Console for performance signals.
When to run it
Run it after a template change or before a mobile ad landing page goes live when you need a quick HTML preflight on viewport and zoom. Pair with the PageSpeed Checker and Core Web Vitals tool for lab and field performance numbers.
How to read pass, warn, and fail
Pass means the signal looks fine in raw HTML. Warn means something is missing or risky but not always fatal. Fail means a clear mobile usability problem in HTML (missing viewport, zoom lock, or very wide fixed layout in inline CSS). Each row includes a plain fix you can hand to a developer.
Limits
One URL per run. External CSS files are not fetched. Links or layout that only exist after JavaScript runs are invisible to this checker.
Frequently Asked Questions
Is this Google's Mobile-Friendly Test?
No. Google retired its public Mobile-Friendly Test in December 2023. This tool checks HTML and inline CSS signals on the live response only. It does not contact Google or return a Google pass/fail badge.
Does this tool run JavaScript?
No. It parses the initial HTML. Client-rendered layouts, lazy-injected viewports, or links added by JavaScript are not evaluated.
What viewport meta tag should I use?
Use width=device-width and avoid user-scalable=no or maximum-scale below 2. A common baseline is <meta name="viewport" content="width=device-width, initial-scale=1">.
Why check srcset on images?
srcset lets browsers pick a smaller file on narrow screens, which helps load time on mobile. This tool only sees srcset on <img> tags in the HTML, not responsive images built purely in CSS or JS.
What should I use for full mobile performance?
Use the PageSpeed Checker and Core Web Vitals tool for Lighthouse and CrUX field metrics. In Search Console, use the Core Web Vitals report (not the retired Mobile Usability report). This HTML check is a quick preflight, not a complete audit.
Related tools
PageSpeed Checker
PerformanceAssess Core Web Vitals and load times to provide actionable insights for technic…
Core Web Vitals Checker
PerformanceCheck LCP, CLS, INP scores with mobile vs desktop comparison powered by Google P…
Image Size Checker
PerformanceCheck image file sizes, formats, alt text and dimensions for any URL with optimi…
Lazy Load Checker
PerformanceVerify the implementation of deferred image loading to enhance initial page load…