LastingWeb

Free tool · No signup

Mobile-friendly test

See your homepage on real phone, tablet and desktop widths, with screenshots, and find the layout problems that make visitors pinch, zoom and leave.

No signup · Results in ~40 seconds · Nothing stored except the shareable report

What we check and why

How the test works

Google retired its own Mobile-Friendly Test in December 2023, but the question it answered still matters: does your site work on the device most first-time visitors use? We load your homepage in a real Chrome browser at seven widths — 320, 360, 390, 430, 768, 1024 and 1440 pixels — and measure the layout at each one. Screenshots of the phone, tablet and desktop views appear in the report so you can see what clients see.

  • Sideways scrolling: content wider than the screen, usually a table, image or embedded map.
  • Text smaller than 12 pixels as a share of all visible text.
  • Buttons and links smaller than 44 × 44 pixels, which are hard to tap accurately.
  • Fixed overlays, such as cookie banners or chat bubbles, covering a large part of the first screen.
  • Whether your main headline and a call to action appear on the first phone screen.
  • A sticky contact button, and whether tablet and desktop layouts fit their width.

Why mobile matters for professional firms

People often look for a lawyer, accountant or clinic on their phone, between other things, sometimes in a stressful moment. If the first screen is filled by a cookie banner and a large stock photo, or the phone number is not tappable, many will go back to the search results rather than scroll.

Google indexes the mobile version of your pages first, so content missing on mobile is effectively missing for search. Accessibility guidelines point the same way: WCAG 2.2 asks for tap targets of at least 24 × 24 pixels at level AA, with 44 × 44 recommended at AAA.

Fixing what we find

Sideways scrolling is usually fixed by making tables scroll inside their own container and giving images and embeds max-width: 100%. Raise base font size to 16 pixels, add padding to small links and icons, and make the cookie banner a compact bar instead of a full-screen wall. Put a short headline and a Call or Book button in the first screen of the phone layout.

After the fixes

Re-run the test and compare the screenshots. Then check two or three journeys on your own phone: find the phone number and call, open the menu, read a service page and fill in the contact form. Automated measurements catch layout problems reliably, but a two-minute manual check confirms that the experience feels right.

Frequently asked questions

Is there still an official Google mobile-friendly test?

No. Google retired the Mobile-Friendly Test and the Search Console mobile usability report in December 2023. Lighthouse and real-device testing remain the recommended approaches.

Why 44 pixels for tap targets?

It is a widely used guideline, matching WCAG's AAA target size criterion and Apple's interface guidelines. WCAG 2.2 level AA sets a minimum of 24 pixels with spacing exceptions.

Do you test on real phones?

We use a real Chrome browser with phone-sized viewports and device scaling. That catches layout problems reliably; touch behaviour and phone-specific browser quirks still deserve a quick check on your own phone.

Does the cookie banner count against me?

Only if it covers a large share of the first screen. A banner covering more than about 30% of a phone screen hides your content at the moment visitors decide whether to stay.

Done for you

Want these fixed? We build it right.

LastingWeb builds fast, secure, compliant websites for professional firms — hosting, TLS, email authentication and GDPR-friendly analytics included.

See packages