Skip to content

Mobile Friendly Test by Google Is Gone — Test Here

Google retired its Mobile-Friendly Test in December 2023, so run the check here. Enter a URL: we take a real mobile screenshot with Lighthouse, check the viewport tag, fixed-width layouts, tap targets, font sizes and content width, test what a Googlebot Smartphone request receives, and give a clear pass or fail.

Try:

The screenshot and audits come from Google's own Lighthouse engine via the PageSpeed Insights API on an emulated phone; we read your HTML as a phone browser. Free, no signup. Updated Oct 24, 2026 by the AEOeye team.

What happened to Google's Mobile-Friendly Test?

Google removed the Mobile-Friendly Test, its API and the Mobile Usability report in December 2023, and deleted mentions of them from its documentation (Search Central updates). This test runs on Lighthouse, Google's open-source auditing engine, through the PageSpeed Insights API.

The reason it went away matters: mobile-friendliness didn't stop mattering, it became the default. Google now indexes and ranks the mobile version of your pages, crawled with Googlebot Smartphone.

Person holding smartphone with green screen while relaxing on a couch indoors.
Photo by Vitaly Gariev on Pexels

Mobile Friendly Test: Screenshot, Viewport and Tap Targets

The test combines a live fetch with a mobile Lighthouse run:

Check Fails when
Viewport meta tag Missing, so phones render a shrunken desktop page
Fixed-width elements Inline widths of 1000px or more
Tap targets Buttons and links too small or too close together
Legible font sizes Too much text below a readable size
Content fits the screen The page scrolls sideways
Googlebot Smartphone request The page fails for both a phone browser and Googlebot

You also get the mobile screenshot Lighthouse captured, so you can see what a phone actually rendered.

Mobile Friendly Tester: What a Pass Actually Means

A pass means the page works on a phone: it scales, it's readable and it's tappable. It doesn't mean it's fast. Speed on mobile is measured separately by Core Web Vitals, where many sites that look fine on a phone still fail.

The basics are nearly universal now: in our October 2026 analysis of 315 big-brand homepages (dataset), 99% set a viewport tag. The failures we see more often are content that only appears on desktop — and Google says the mobile and desktop versions should carry the same content so both can rank.

Close-up of modern digital devices with cloud-themed wallpaper and lock screens.
Photo by Chengxin Zhao on Pexels

What should I fix first?

The viewport tag and horizontal scrolling, because they break the whole page; then tap targets and font sizes. Make sure your mobile version has the same main content, structured data and metadata as desktop.

Then check speed with the Core Web Vitals test, and confirm what Googlebot Smartphone receives with the Googlebot simulator.

One page checked. What about the rest of your site?

The free SEO audit crawls your site and scores ~90 checks across 7 areas — with the evidence and the fix for each problem.

Free · no account · crawls up to 20 pages and runs Google PageSpeed Insights. Usually 60–90 seconds.

FAQ

Is the Google Mobile-Friendly Test still available?

+

No. Google retired the Mobile-Friendly Test, its API and the Mobile Usability report in December 2023 and pointed site owners to Lighthouse, which powers this test.

Does mobile-friendliness affect rankings?

+

Google indexes and ranks the mobile version of pages, so a page that is broken on phones is effectively broken for Google. Speed and usability on mobile also feed page experience.

Why does the test take longer than other tools?

+

It runs a full Lighthouse audit on an emulated phone through Google's PageSpeed Insights API, which loads and renders the page. That usually takes 20 to 40 seconds.

Sources

Related free tools

All speed, mobile & security tools