Free mobile-friendly test.

No. Google shut its tool and its API down on December 1, 2023 and pointed people at Lighthouse and PageSpeed Insights instead. This test covers the checks that tool made from the page source (viewport configuration, fixed-width content, tiny text, plugins) plus the crawl and weight checks Google’s never did, and it hands the two checks that need a rendered browser, tap-target spacing and real Core Web Vitals, to PageSpeed Insights with a one-click link for your URL.

We fetch your page once with a mobile Chrome user agent from our edge, read the response headers and the HTML, and fetch your robots.txt. Thirteen checks are scored from what we could read, each weighted by how much it changes what a phone shows. A check we could not read is dropped from the maximum rather than counted as a failure, and the result says so.

Mobile-ready on the basics means 85 or above: every fetch-level check passes and what remains needs a browser. Fixable gaps is 60 to 84. Not mobile friendly is under 60, which almost always means the viewport tag is missing or pinned to a desktop width. These bands are ours for reading the result; they are not a Google score and we do not rank you against other sites.

Tap-target spacing depends on the rendered layout and the CSS your page loads, and Core Web Vitals depend on real visitors on real phones over 28 days. Neither exists in a single fetch. PageSpeed Insights reports both, free, so the result links straight to it for your URL instead of inventing a number.

No. Mobile usability is a floor, not a ranking factor you can stack. A page that fails the viewport check renders badly and converts badly on phones; fixing it removes a penalty on the visitor. Rankings still come from relevance, authority and the quality of the page.

The page is fetched, read and discarded; the facts are returned to your browser and scored there. We keep an aggregate count of tests run and nothing that identifies the page or you.