Mobile Friendly Checker
Google retired its Mobile-Friendly Test in December 2023. This checker reads your HTML for seven mobile basics, from the viewport tag to tap targets and font sizes. To render the page, use Lighthouse.
How to check a page for mobile basics
Four steps, from page source to a rendered test.
Copy the page source
Right-click the page, choose View Page Source and copy all of it. This is the HTML before any script runs.
Paste it and run the check
The tool reads the viewport tag, style attributes and any style blocks in the page. Linked CSS files are not fetched or read.
Read the seven results
Each check is pass, warning or fail, and the score is the share passed with a warning worth half. The notes further down say which warnings are safe to ignore.
Confirm in a rendered test
Run Lighthouse in Chrome or the live test in Search Console's URL Inspection tool to see the page as a phone and Googlebot render it.
How do I check if a page is mobile friendly now that Google's test is gone?
Use Lighthouse. When Google retired its Mobile-Friendly Test, the Mobile-Friendly Test API and Search Console's Mobile Usability report on December 1, 2023, it named Lighthouse from Chrome among the resources for evaluating mobile usability that had appeared since the report launched. Lighthouse runs in Chrome DevTools, and PageSpeed Insights runs it for you on any URL with no installation. To see how Googlebot renders a page, use the live test in Search Console's URL Inspection tool, which fetches the URL in real time and shows a screenshot taken from the mobile version. The checker above is a quicker, narrower first pass on the source code.
Why did Google retire the Mobile-Friendly Test?
Google said in its April 2023 announcement that in the nearly ten years since it launched the Mobile Usability report, many other resources for evaluating mobile usability had emerged, including Lighthouse. It added that retiring the tools does not mean mobile usability is unimportant, and that it remains part of Google's page experience guidance. Google had expanded its use of mobile-friendliness as a ranking signal to mobile searches in all languages on April 21, 2015.
Does mobile friendliness still matter for SEO?
Yes, mostly because of mobile-first indexing. Google's mobile-first indexing documentation says it uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking. On October 31, 2023 Google announced that the move to mobile-first indexing was complete, with a very small set of sites that do not work on mobile at all still crawled by the legacy desktop Googlebot. Whatever is missing from your mobile pages is missing from Google's index, which is why the same documentation asks for the same content, the same structured data, and equivalent titles and meta descriptions on both versions.
Google recommends responsive web design because it is the easiest pattern to implement and maintain: one URL and one set of HTML for every device. Dynamic serving relies on user-agent sniffing and a Vary: user-agent header, and separate mobile URLs need the desktop URL as canonical with the mobile URL as its alternate. Our technical SEO audit checklist covers how to confirm the mobile version carries everything.
What does this checker test?
Seven things in the HTML and inline CSS you paste, scored by the tool's own rules. Read the results with these notes:
- Viewport tag: a tag with
width=device-widthandinitial-scale=1passes; no tag fails. Without one, phones may lay the page out in a virtual viewport around 980 pixels wide and shrink it to fit, as MDN explains. The checker warns when initial-scale=1 is absent, but MDN calls it a common practice that is usually unnecessary, so treat that warning as minor. - Media queries: two or more @media rules using min-width or max-width in style blocks pass. Linked stylesheets are not read, so a warning here often just means your CSS lives in a separate file.
- Small tap targets: a link, button, form field or element with role="button" whose inline style sets a width or height under 44 pixels is flagged. The 44 figure matches the WCAG 2.2 enhanced target size (level AAA); the AA minimum is 24 by 24 CSS pixels, and web.dev suggests about 48 pixels with about 8 pixels between targets. Sizes set in style blocks or linked stylesheets are not read.
- Font size: any font-size in pixels below 12 fails. The line comes from Lighthouse's legible font size audit, which flagged pages where 40% or more of the text was smaller than 12 px and was removed in Lighthouse 13.
- Wide fixed elements: widths over 500 pixels, in CSS or in width attributes, fail; max-width values and media query breakpoints do not count. Width and height attributes on img tags are left out, because web.dev recommends them on every image to prevent layout shift. Whether those images scale down is the images check's job.
- Images: an img tag counts as responsive if it carries max-width: 100%, width: 100% or a srcset attribute, and all images count when a style block in the page has a rule such as
img { max-width: 100% }. Rules in linked stylesheets are not read. - Line height: values under 1.4 (or 140%, or 18 px) get a warning.
The score is the share of checks passed, with a warning worth half. It is this tool's own number, not a Google measure.
What can't a source code check tell you?
How the page actually renders. The checker never lays the page out, so it cannot see content that overflows at real screen widths, elements that overlap, menus that hide content on phones, or anything JavaScript adds after load. Google's mobile-first documentation suggests using the URL Inspection tool to check that the content is visible on the rendered page. For pages with real traffic, Search Console's Core Web Vitals report shows how Chrome users on phones experienced loading, responsiveness and layout stability; our glossary entry on Core Web Vitals explains the three metrics and their thresholds.
Mobile-friendly page questions.
Google's retired test, viewport tags, tap targets and rankings.
Does Google still have a mobile-friendly test?
No. Google retired the Mobile-Friendly Test, the Mobile-Friendly Test API and Search Console's Mobile Usability report on December 1, 2023, and pointed to Lighthouse from Chrome as an alternative. Lighthouse runs in Chrome DevTools and inside PageSpeed Insights. The live test in Search Console's URL Inspection tool also shows a screenshot taken from the mobile version of a page.
What is the correct viewport meta tag?
<meta name="viewport" content="width=device-width, initial-scale=1"> works for almost every site. MDN recommends width=device-width and describes initial-scale=1 as a common practice that is usually unnecessary. Avoid user-scalable=no: MDN warns that disabling zoom stops people with low vision from reading the page, and that WCAG requires at least 2x scaling.
How big should tap targets be on mobile?
Google's web.dev recommends about 48 by 48 pixels on a page with a proper mobile viewport, roughly 9 mm or the size of a finger pad, with about 8 pixels between targets. WCAG 2.2 sets 24 by 24 CSS pixels as the minimum at level AA and 44 by 44 for its stricter AAA level. This checker flags inline sizes under 44 pixels on links, buttons and form fields.
Is mobile friendliness a Google ranking factor?
Google expanded its use of mobile-friendliness as a ranking signal to mobile searches in all languages on April 21, 2015, and says mobile usability remains part of its page experience guidance. The larger effect today is mobile-first indexing: Google indexes and ranks the mobile version of your content, so anything missing on mobile is missing from Google. Relevance still comes first.
Should I build a separate mobile site?
Usually not. Google recommends responsive web design because it is the easiest pattern to implement and maintain. A separate mobile site needs the desktop URL as canonical and the mobile URL as its alternate, plus the same content, structured data, titles and meta descriptions on both versions, which is upkeep a responsive site avoids.
Mobile is one part of a technical audit.
This check reads the HTML you paste. Our technical SEO audit checklist covers what else to test on the mobile version Google indexes, from rendering to structured data, ordered by what blocks ranking first.
What to do next.
Run these next
All 25- Page Speed AnalyzerAnalyze page load performance and get optimization recommendations
- Core Web Vitals CalculatorCheck LCP, INP, and CLS scores against official CWV thresholds
- Image SEO CheckerAudit image alt text, file sizes, formats, and lazy loading
- SEO Score CalculatorA 30-question self-check of on-page basics
Read next
Rather have it done?
CRO audit, $99
Why visitors leave your key pages, tied to your own numbers, with the fixes in order. From files you export, back within 8 hours.
See the audit