Mobile-Friendly Test & Checker

Last updated: Jul 12, 2026

Run a lightweight HTML mobile-readiness check on any public page. Review viewport settings, responsive markup, image signals, zoom controls and potential issues before testing the rendered page on real devices.

Enter a URL to check mobile-friendliness:

How the Mobile-Friendly Checker Works

This tool analyzes HTML-level mobile-friendliness signals:

Enter a URL. The tool fetches the page and analyzes the HTML markup, inline CSS, and meta tags.
Viewport check: verifies the viewport meta tag is present with correct width=device-width and initial-scale settings, and that zoom isn't restricted.
Responsive signals: looks for media queries in returned HTML, fixed-width inline styles, and responsive image attributes. It cannot calculate the rendered layout.
Loading hints: checks script attributes and image lazy-loading markup. It does not measure speed or Core Web Vitals.
Mobile features: verifies touch icon, theme color, app manifest, and absence of incompatible technologies like Flash.

Why Mobile-Friendliness Matters in 2026

Mobile usability affects how people discover, read, and act on a page. Use this static check as an early warning, then verify the rendered experience:

Mobile-first indexing, Google uses the mobile version of your page for indexing and ranking. If your mobile experience is broken, your desktop rankings suffer too.
Rendered usability, horizontal overflow, tiny text, crowded controls and unstable layouts can make a technically accessible page frustrating to use.
Core Web Vitals, use PageSpeed Insights or Lighthouse for LCP, INP and CLS. This checker does not calculate those metrics.
Conversions, test important forms, navigation, checkout and calls to action on representative devices instead of relying on one score.

For complete mobile optimization, also check your page performance, image optimization, and accessibility.

What to Use After Google's Mobile-Friendly Test

Google shut down its official Mobile-Friendly Test tool, the testing API, and Search Console's Mobile Usability report in December 2023. The tool millions of site owners used to check "is my website mobile friendly?" no longer exists.

Google now points people to three scattered alternatives, each with a catch:

Lighthouse: built into Chrome DevTools. Thorough, but technical. You need to open DevTools, run an audit, and interpret a developer-oriented report.
PageSpeed Insights: measures speed and Core Web Vitals, but no longer gives a simple mobile-friendly verdict.
Search Console: only works for sites you own and verified, and the dedicated mobile usability report is gone.

This tool provides a fast first-pass review of public HTML signals such as viewport settings, inline width declarations, responsive image attributes, zoom restrictions and loading hints. It does not render a mobile viewport, calculate computed tap targets or font sizes, take a screenshot, or replace Lighthouse and real-device testing.

Want the full story on what happened and how the alternatives compare? Read our guide: Google's Mobile-Friendly Test is gone, here's what to use instead.

Essential Mobile-Friendly Checklist

Make sure your site hits these fundamentals:

Viewport meta tag: <meta name="viewport" content="width=device-width, initial-scale=1"> in every page's <head>.
Responsive CSS: use media queries, flexible grids, and relative units (%, rem, vw) instead of fixed pixel widths.
Readable text: minimum 16px font size for body text. No need to zoom to read.
Tap targets ≥48px: buttons and links should be at least 48×48px with adequate spacing between them.
Responsive images: use srcset + sizes to serve appropriate image sizes per screen. Add loading="lazy" for below-fold images.
No horizontal scroll: nothing should extend beyond the viewport width. Use max-width: 100% on images and overflow-x: auto on tables.

For professional mobile optimization, explore our web design services and SEO services. Also check your color contrast; mobile screens in bright light make low-contrast text even harder to read. Then verify your font loading isn't blocking mobile rendering.

Next steps

Mobile-Friendly Checker related tools and articles

Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.

Image SEO Checker

CSS Clamp Responsive Font Size Generator Tool Online

CSS Clamp Generator

Accessibility Checker

Image SEO: Alt Text, File Names, Compression, and More

Website Typography Guide: Font Sizes, Hierarchy & Best Practices

How to Choose Fonts for Your Website in 2026

Mobile-Friendly Checker: FAQ

What does this checker measure?

It fetches the page HTML and applies static heuristics for viewport settings, inline responsive CSS, small inline fonts, fixed-width images and elements, tables, hover patterns, blocking scripts, lazy loading, Flash, and a few mobile metadata signals.

Is this a rendered mobile or Lighthouse test?

No. It does not run a browser, set a mobile viewport, take a screenshot, calculate Core Web Vitals, or interact with the page. Use real-device testing and a browser-based performance or accessibility audit for rendered behavior.

How is the score calculated?

The score starts at 100, subtracts 20 for each error and 5 for each warning, ignores informational items, and is clamped to 0 through 100. The Mobile friendly label means no error-level heuristic fired, even if warnings remain.

Why can it say no responsive CSS when my site is responsive?

The checker sees media queries embedded in the HTML and media attributes on link elements, but it does not download and parse ordinary external stylesheets. Most production CSS lives externally, so this warning often needs manual verification.

How accurate are the font, tap, image, and overflow checks?

They inspect simple HTML attributes and inline style patterns, not computed layout. CSS classes, container queries, transforms, responsive frameworks, rendered dimensions, and actual touch-target spacing are outside the analysis.

Should I apply every lazy-loading or script suggestion?

No. Keep likely LCP images eager when appropriate, and assess script dependencies before adding async or defer. The findings identify candidates for testing, not context-aware deployment instructions.

What should I do after a low score?

Fix clear viewport and zoom-accessibility errors first, then inspect each warning in a mobile browser. Test representative pages at several widths, keyboard and touch interaction, text zoom, horizontal overflow, and real network performance.

What data is sent during this mobile HTML check?

The submitted URL is sent to Web Aloha's server so it can fetch the public HTML and calculate the heuristic report. The endpoint does not include application logic that persists the page or result, though normal hosting logs may record requests.

Free 48-Hour Website Audit

Not sure what to fix first on your own website? We'll review it and tell you, in plain English. Free & non-obligatory.

Get My Free Audit 💪

Need a Mobile-First Website?

We build fast, responsive websites designed mobile-first for modern users.

Explore Web Design Services 🚀