Free Mobile Friendly Test
Check whether a page works on a phone, with a rendered screenshot and the viewport, tap target and image checks reported separately. No sign-up required.
How to test if a page is mobile friendly
1. Enter a page URL
Any public page. The test always runs on an emulated phone, since that is the question being asked.
2. See it rendered
You get a screenshot of how the page actually draws on a phone screen, alongside the verdict.
3. Read the checks
Viewport, tap targets and image scaling reported separately, so you know which one to fix.
Google retired its Mobile-Friendly Test
If you came looking for Google's mobile friendly test, it no longer exists. Google retired the tool in December 2023, along with the Mobile Usability report in Search Console and the Mobile-Friendly Test API, on the grounds that the mobile web had matured enough not to need a dedicated checker.
Google's own suggested replacement was Lighthouse, which is what this tool runs. Any site still presenting itself as the official Google test is a third party using the name.
Worth knowing what went with it: Search Console no longer reports mobile usability at all. The nearest remaining signal is the Core Web Vitals report, which is measured on mobile by default.
What this mobile responsiveness checker looks at
Reported separately, because two of these break a page and three only degrade it.
| Check | Weight | Why it matters |
|---|---|---|
| Viewport meta tag | Critical | Without it, phones render the page at desktop width and shrink it. Text becomes unreadable without pinching, and this alone makes a page fail. |
| Tap target size | Critical | Links and buttons under roughly 48 pixels, or crowded together, get mis-tapped. The most common complaint about otherwise responsive sites. |
| Image sizing | Secondary | Images served much larger than they display waste cellular data and slow the page, without breaking the layout. |
| Viewport configuration | Secondary | Whether the viewport is set up so the layout genuinely adapts, rather than only declaring that it does. |
| Mobile speed | Context | LCP, layout shift and blocking time under mobile emulation. A responsive page that takes eight seconds is still a bad mobile page. |
Why this matters more than it used to
Google has used mobile-first indexing for every site since 2019. The mobile rendering of your page is the version that gets crawled, indexed and ranked, including on desktop results. If content is hidden or broken on mobile, that is the version Google evaluates.
This is a different claim from the usual one. Mobile friendliness is not a bonus applied to pages that pass. It is the lens through which every page is now read, which makes a broken mobile layout a content problem rather than a cosmetic one.
Speed compounds it. Core Web Vitals are measured on mobile by default, so a page that reflows correctly but takes eight seconds on a phone still fails the visitor. The tool reports both.
Frequently asked questions
Is there a Google mobile friendly test checker available?
How to test a mobile friendly website?
How to check mobile responsiveness?
How can I check if my website is responsive?
How can I check if my website is mobile-responsive online?
What tool can I use to check if my website is responsive?
What is the best tool to check if a website is mobile friendly?
Is my website mobile-friendly on Google?
How do I make my website mobile-friendly?
How do I see what my website looks like on mobile?
How to view responsive design in Chrome?
How can I test a website on different devices?
Is responsive web design still a thing?
What are some examples of mobile-friendly websites?
Does mobile friendliness affect SEO?
Millions of people will ask AI about your category this week
RankSpot researches, writes and publishes daily, and sends you the short list of what's left. Free for 3 days.
Start free trial
