Mobile-Friendly Tester
Paste HTML and run static checks for the mobile-readiness signals Google's bots look for — viewport meta, tap target sizes, font sizes, and horizontal-scroll triggers.
Why a Static Mobile Check Still Has Value
Real mobile testing runs the page in a headless browser, measures rendering, and reports layout shift. This tool does not replace that — Lighthouse and Chrome DevTools are still the right call for final verification. What a static checker does well is the catch-it-before-you-deploy pass: spotting a missing viewport meta in a hand-edited template, a 10-pixel font size buried in inline styles, links spaced four pixels apart that would fail Google's tap target rule. Those are template-level bugs that Lighthouse would flag too — but only after you have already loaded the page in a slow simulation. A static check finds them in seconds, in the editor, with no server roundtrip. Use alongside the Core Web Vitals Cheatsheet for the runtime side.
How the Heuristics Score Your HTML
The tool runs four passes over the pasted HTML. Pass one is meta — does the head contain `<meta name='viewport'>` and is its content value a reasonable `width=device-width, initial-scale=1`? Common bugs flagged: missing tag entirely, `initial-scale=1` without `width=device-width`, fixed pixel widths, `user-scalable=no` (which blocks accessibility zoom). Pass two is touch targets — every `<a>` and `<button>` is checked for inline width/height styles below 44 pixels and the surrounding markup is scanned for spacing rules under 8 pixels. Pass three is typography — body text below 14 pixels and explicit `font-size` declarations under that threshold are flagged. Pass four is layout — fixed pixel widths over 360 on top-level containers (the rough minimum mobile viewport) and elements with `overflow: visible` and inline widths exceeding that. Each pass reports as a separate section with line-referenced findings.
Frequently Asked Questions
Built by Derek Giordano · Part of Ultimate Design Tools