How does your site feel on a phone?

Most of your visitors are on a screen about the size of your palm. This audit loads your pages at that size and checks the things that decide whether the experience is usable: text you can read, buttons you can hit, and images that fit.

Pages loaded at 375×667 in a real browser
Tap targets big enough to hit with a thumb
Viewport configuration, responsive images and layout structure

Run your free audit

Measured where it can be, inferred where it cannot.

When the headless browser is available we load each page at 375×667 and read the computed font sizes and tap-target areas off the rendered result. Those are measurements. When it is not available we fall back to reading your viewport configuration and markup, which is a reasonable proxy and nothing more. Your report tells you which of the two it used.

What no automated check can tell you is whether the experience is any good. A page can pass every test here and still be a maze on a phone. Treat a clean score as permission to stop worrying about the mechanics, not as evidence that the design works.

Mobile test FAQs

No, and it cannot be: Google retired that tool in December 2023. This runs our own checks, the same ones that produce the mobile pillar of our full site audit. The questions are similar because they are the questions that matter on a small screen.

375 by 667 CSS pixels, which is roughly an iPhone SE. It is deliberately at the small end of what people carry: a layout that works there works nearly everywhere, and problems show up at the narrow end first.

Measured means we rendered the page in a real browser and read the computed font sizes and tap-target areas. Inferred means the browser was not available for that run, so we estimated from your viewport tag and markup.

Usually links sitting close together in body copy or a footer, or icon buttons that were sized for a cursor. Responsive layout and comfortable tapping are different problems, and the second is the one people feel.

Up to eight. Mobile problems live in templates rather than individual pages, and each page goes through a real render, so a handful of representative pages answers the question about as well as thirty would.

Mobile usability is part of how Google evaluates pages, so yes, indirectly. But the better reason to fix it is the one you can see in your own analytics: people leave sites they cannot comfortably use.