Free mobile-friendly test
See how your page behaves on a real phone: how fast the main content appears, whether the layout jumps, whether buttons are easy to tap and whether people can zoom. Tested by Google on a mobile profile. No signup.
Google loads the page on a simulated mid-range phone with a throttled connection, so it can take up to a minute. Nothing is stored.
Why a page can look fine on your phone and still fail
You probably check your site on a good phone, on Wi-Fi, with everything already cached. Your customers arrive cold, on a normal mobile signal, often on an older handset. This test runs the page the way Google does: a mid-range phone, a throttled connection, nothing cached. That's why the result can be harsher than what you see yourself, and closer to what your visitors actually get.
What we check
How fast the main content appears (Largest Contentful Paint): Google wants it inside 2.5 seconds. Whether the layout jumps as it loads (Cumulative Layout Shift), which moves buttons under people's thumbs. Google's mobile performance score. Whether buttons and links are big enough to tap and spaced far enough apart. Whether people can pinch to zoom. And, from the page code, the viewport tag that tells phones to fit the page to the screen. Everything except the viewport tag comes from Google's own render of the page.
What happened to Google's Mobile-Friendly Test?
Google retired its standalone Mobile-Friendly Test in December 2023. The checks moved into Lighthouse and PageSpeed Insights, which is what this tool runs for you and translates into plain English. There's more on that in Google's Mobile-Friendly Test is gone: what to use instead. For speed fixes, start with what Core Web Vitals are and how oversized images slow pages down.
This is one check. Your site needs dozens.
The full AuditCrow audit runs this alongside speed, SEO, accessibility, trust and AI readiness, then tells you what to fix first, in plain English.
Common questions
Straight answers about what this check does, and doesn't do.
Is this the same as Google's old Mobile-Friendly Test?
Google retired its standalone Mobile-Friendly Test in December 2023 and moved the checks into Lighthouse. This tool runs Google's Lighthouse test on a mobile profile and explains the results in plain English, so it covers the same ground plus loading speed.
Why is my score worse than when I try the site on my own phone?
The test uses a mid-range phone on a throttled mobile connection with nothing cached. Your own phone is probably faster, on Wi-Fi, and has already loaded the site before. The test is closer to what a first-time visitor gets.
Does being mobile-friendly affect Google rankings?
Yes. Google ranks sites using their mobile version, and loading speed and layout stability are part of its Core Web Vitals. More importantly, most local searches happen on phones, so a slow or fiddly page loses enquiries whatever it ranks.
Why does it sometimes say it couldn't measure the page?
Google's PageSpeed service occasionally times out or is busy. We show that as 'couldn't measure' rather than a fail, because it says nothing about your site. Try again after a minute.
From the blog
All postsGoogle's Mobile-Friendly Test Is Gone: What to Use Instead
Google retired the standalone Mobile-Friendly Test tool back in December 2023, but people still search for it every month. Here's where mobile usability checking actually lives now.
Read moreWhat Are Core Web Vitals? The Metrics That Affect Your Google Ranking
Core Web Vitals are three speed and experience signals Google uses to rank your site. Here's what they mean and how to improve them.
Read moreHow Large, Uncompressed Images Destroy Page Speed (With a Real 13.6 MB Example)
One accidental 13.6 MB upload can add over 20 seconds on slow 4G. Here's what that costs in load time, rankings, and visitors - and how to catch oversized assets before they wreck a page.
Read moreOther free tools
Quick checks for the things that most often go quietly wrong.