ToolsHub
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.

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…

Mobile-friendly in 2026

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.

Privacy: the address you enter is fetched by our server only to run this check. The downloaded HTML is passed to your browser for analysis and is not stored, and the results are not saved on our side. Requests are rate-limited to keep the service fair for everyone, so if you check many pages in a row you may need to wait a few minutes.

Limits: pages are read up to 2 MB of HTML, redirects are followed up to eight hops and each request has a short timeout. Pages behind a login, servers that block automated requests and content added only by JavaScript cannot be analysed this way; for those, copy the page source from your browser and use the paste option where it is available.

Tip: fix the problems marked red first, because they matter most. Yellow warnings are worth reviewing but are often harmless in context, and blue notes are information. After a change, run the check again to confirm the result – search engines pick up the change on their next visit to the page.

Other useful tools