- Home
- Free tools
- Mobile-friendly checker
Mobile-friendly checker
Check the basics that make a page work on a phone: the viewport tag, zoom, responsive CSS and elements that overflow narrow screens. A static check of your HTML and CSS, with fixes you can copy.
How to use it
- Enter a page address.
- Read the verdict and the fix list. A missing viewport or blocked zoom is the most serious.
- Use the starter snippets, then run the full audit for the rendered mobile view.
What it checks
- The viewport meta tag and its width
- Whether pinch-zoom is blocked (user-scalable, maximum-scale)
- Width-based @media rules in inline and linked CSS
- Fixed-width tables, iframes, embeds and inline widths over 480 px
- Tiny inline text sizes and browser plugins
- Phone-friendly input types, touch icon and theme colour
Limits
- Reads the HTML and CSS for mobile signals such as viewport, zoom and responsive rules. It does not render the page on a phone.
- Layout problems that appear only when the page runs, such as overlapping elements, are not detected.
- Google retired its own mobile-friendly test, so this is a guide to common problems, not an official verdict.
Public pages only, one page at one point in time. See the methodology and terms.
Frequently asked questions
Did Google retire its Mobile-Friendly Test?
Yes. Google shut down the Mobile-Friendly Test tool, its API and the Mobile Usability report in December 2023. Mobile still matters (Google indexes the mobile version first), but there is no official pass or fail any more.
What does this tool actually check?
It reads the page's HTML and linked CSS. It does not render the page, so it cannot measure tap-target size, real text size or sideways scrolling. The full audit adds Lighthouse's rendered mobile checks.
What is the viewport tag?
A meta tag that tells phones to lay the page out at the device's width instead of pretending to be a 980 px desktop screen. Without it most pages look tiny and zoomed out.
Why should I not disable zoom?
People with low vision pinch-zoom to read. Blocking it fails accessibility rules (WCAG 1.4.4) and frustrates users.
My site uses a framework, so why is responsive CSS not found?
Some builders inject CSS with JavaScript, or serve more than five stylesheets, so the check cannot always confirm media queries. The result then says it could not be confirmed.
What else makes a site mobile-friendly?
Readable text (about 16 px), tap targets at least 44 px, no horizontal scrolling, fast loading and no intrusive pop-ups. The Core Web Vitals test covers speed and layout shifts.