webtoolshelper
Website Tools

Website Mobile Friendly Checker

Google retired its Mobile-Friendly Test in December 2023, but mobile-friendliness still matters for visitors and for mobile-first indexing. This checker reads a page and up to eight of its stylesheets and looks for the code signals that make a page work on phones: a correct viewport meta tag, zoom left enabled, no plugin content, no wide fixed-width elements, width-based media queries or a fluid layout, readable font sizes and images that scale with their container.

  • Encrypted connection
  • No sign-up
  • Free to use

Google retired its Mobile-Friendly Test in December 2023. This tool checks the page’s code for the signals that test used; it does not render the page. For a real mobile render and speed data, use the Core Web Vitals Checker.

How to use Website Mobile Friendly Checker

  1. Enter the page URL.
  2. Click “Check mobile friendliness”.
  3. Read the HTML and CSS checks.
  4. Confirm on a real phone or with Lighthouse.

Website Mobile Friendly Checker features

Viewport

width=device-width and zoom.

Plugins

Flash and object/embed content.

Fixed widths

Wide elements in HTML and CSS.

Media queries

Counted across stylesheets.

Font sizes

Declarations below 12 px.

Safe fetching

Only public http(s) addresses are fetched.

When to use Website Mobile Friendly Checker

  • Checking an old site before a redesign.
  • Reviewing a theme or template.
  • Explaining mobile issues to a client.
  • Quick checks of landing pages.

Website Mobile Friendly Checker FAQ

Why not render the page on a phone?

This tool analyses code without a browser engine, which is fast and works anywhere. For a real mobile render with speed data, use the Core Web Vitals Checker, which runs Google Lighthouse.

Why is disabling zoom a problem?

user-scalable=no or a low maximum-scale stops people with low vision from enlarging text, which fails WCAG 1.4.4.

What if the site uses no media queries?

Layouts built with flexbox, grid and fluid units such as clamp() can adapt without them; the tool then warns instead of failing.

Are all stylesheets read?

Up to eight linked stylesheets plus inline styles. Print stylesheets are skipped.

Is there still a Google mobile-friendly report?

The standalone test and report were retired. Lighthouse in Chrome and PageSpeed Insights still show mobile usability and performance information.

Core Web Vitals Checker See how real visitors experience your page. Enter a URL and choose mobile or… Page Experience Checker Google describes good page experience as fast, secure, mobile-friendly pages… HTML Accessibility Checker Find the accessibility barriers that can be detected in a page’s code. The checker… Website SEO Report Generator Get a site-level view of your SEO in one report. The generator reads your… Website Screenshot Enter a URL and get an image of the page as a real browser renders it. Choose a…

Pages that work on phones

Most searches happen on phones, and Google indexes the mobile version of pages. A page that needs zooming and sideways scrolling loses visitors quickly, whatever its rankings.

The essentials have not changed: a viewport tag so the page is laid out at the device’s width, flexible layouts that rearrange instead of shrinking, text large enough to read, and tap targets far enough apart. Some of these – tap spacing, real text sizes – depend on the rendered page and are best confirmed on a device.

The score weighs the viewport most, because without it nothing else works.

Google retired its Mobile-Friendly Test, but phones are where most visitors arrive and Google indexes the mobile version of pages. This checker looks for the code signals that make a page work on small screens: a correct viewport meta tag, zoom left enabled, no plugins, responsive CSS with media queries, and readable font sizes.

Disabling zoom (user-scalable=no or maximum-scale=1) is flagged because it stops people with low vision from enlarging text. Fixed widths wider than a phone screen and tiny tap targets are the other common causes of pages that feel broken on mobile.

Code checks cannot replace a real test. Open the page on a phone or in your browser’s device mode, and use Core Web Vitals data to see how fast it is for real mobile users.

Other useful tools