Mobile friendly test

Run this mobile friendly test to review viewport settings, small text and tap targets. Use the HTML, CSS and Lighthouse findings to plan your fixes.

Free, no account. Ten checks per hour across the AI readability, mobile and technology checkers.

We send the address to our API for this check. Results can be cached for five minutes.

A page is mobile friendly when it fits a phone screen without sideways scrolling and keeps its text and buttons easy to use. Google retired its Mobile-Friendly Test on December 1, 2023. This test reads the page’s viewport tag and CSS, then asks Google’s PageSpeed Insights API for a Lighthouse mobile run.

How to use this checker

The page as a phone asks for it
Our server requests the page with a current Android Chrome user agent and reads up to 3 MB of HTML, plus up to six of its stylesheets at 300 KB each. Font stylesheets from font services are skipped.
Static checks
The viewport tag should set width=device-width and leave zoom on. CSS rules outside screen size queries are checked for widths of 480 pixels or more, a base font size under 12 pixels and links or buttons under 24 pixels tall, the minimum target size in WCAG 2.2. Rules a size query hides or resizes are left out.
Lighthouse lab run
We ask Google’s public PageSpeed Insights API for a mobile run. It loads the page in an emulated phone and returns a screenshot, Core Web Vitals lab metrics and audits such as viewport and image resolution. Results are kept for a day.
Mobile-first content parity
We compare mobile and desktop raw HTML text, up to 25 distinct links, Googlebot directives and bounded JSON-LD blocks. Differences may include timestamps or personalization. Dialog and paywall markup is a hint for visual review, never proof of an intrusive overlay. Google’s mobile-first guidance was checked on October 12, 2026.
Field data
When Chrome has collected enough visits, PageSpeed Insights adds real user data for the page, or for the whole site when the page has too little. It covers the last 28 days.

Questions about this checker

Google retired the Mobile-Friendly Test, its API and the Mobile Usability report in Search Console on December 1, 2023, and pointed site owners to Lighthouse. This page combines checks of the HTML and CSS with a Lighthouse mobile run from PageSpeed Insights.

PageSpeed Insights has a shared daily allowance for requests without a key, and it can also fail to load a slow or blocked page. The static checks still run on their own. Open PageSpeed Insights from the result to test the page in your browser.

It catches the common faults: a missing viewport tag, blocked zoom and layouts fixed to desktop widths. It cannot see styles added by scripts or measure real tap spacing. The Lighthouse run and the phone screenshot fill that gap.

Google indexes the mobile version of a page and counts page experience among many signals. A page that works well on phones keeps visitors who arrive from search and from links in AI answers.

Related tools

  • Color contrast checker

    Use this color contrast checker to measure a foreground against a background. Review WCAG 2.2 AA and AAA results, the nearest passing color, transparent layers and palette pairs.

  • Page speed checker

    Run a page speed test for mobile and desktop with Google Lighthouse. Review Core Web Vitals when available, compare a competitor and choose a fix.

  • Image compressor

    Use this image compressor to aim under a size limit, compare quality and download a batch ZIP. Your images never leave your browser.

Check your business in AI answers

A page that crawlers can read is the starting point. The free AI visibility scan shows how assistants answer about your business and what to work on next.

Run the free AI visibility scan