Skip to content

Mobile-Friendly Test: viewport, layout, and tap-target guidance

This mobile friendly test checks the machine-readable signals of mobile readiness for any URL — the viewport meta tag, language declaration, page weight, and HTTPS — and pairs them with practical responsive and tap-target guidance. Layout quality and touch usability need a real device or emulator to judge, so this page reports signals honestly instead of inventing a mobile score.

Run the instant check

Instant readiness signals, not a device test. This check reads viewport, language, weight, and HTTPS from one fetch — it does not render the layout or tap the buttons, so it issues guidance, not a score.

Enter a URL to begin

Instant signals only — nothing is stored.

What mobile-friendliness means

A mobile-friendly page adapts to small screens: text reads without horizontal scrolling, content reflows to the viewport width, and controls are comfortably tappable.

The viewport meta tag is the technical starting point — without it, phones render the desktop layout shrunk down, which fails every other criterion.

Responsive design does the heavy lifting after that: fluid layouts, flexible images, and breakpoints that rearrange content instead of squeezing it.

Touch usability finishes the job: tap targets at least around 44 pixels, spaced so fingers hit the right one, with no overlapping or microscopic links.

What the instant check covers

Covered by this check

  • Viewport meta tag presence
  • Language declaration for correct rendering
  • Page weight affecting mobile networks
  • HTTPS baseline for mobile trust

Not covered — needs a lab test

  • Rendered layout on real screen sizes
  • Tap-target measurement
  • A mobile-friendliness score
  • Device-specific screenshots

How to become genuinely mobile-friendly

  • Set the viewport tag

    One line of HTML enables proper mobile scaling. Our check confirms it is present on any URL.

  • Design fluid layouts

    Use flexible grids and images that shrink with the screen instead of fixed pixel widths.

  • Size tap targets generously

    Aim for at least 44px targets with clear spacing — then verify by tapping through on a real phone.

  • Keep mobile pages light

    Heavy pages hurt most on mobile networks. Compress media and defer anything non-essential.

  • Test on real devices

    Emulators catch layout breaks, but only a phone in hand confirms touch feel. Check key flows manually.

How Traffsite shows your mobile audience

Most sites now earn the majority of visits from phones. Traffsite breaks your own traffic down by device, so you can see exactly how much of your audience experiences the mobile version.

Start a free trial to meet your mobile visitors in the data before redesigning for them.

Common questions

Is this mobile friendly test free?

Yes. Paste any public URL for viewport, language, weight, and HTTPS signals plus responsive guidance — no account needed.

Why is there no mobile score?

Real mobile-friendliness depends on rendered layout and touch interaction, which a single fetch cannot judge. We report what we measured and guide the rest instead of inventing a number.

What is the viewport meta tag?

An HTML tag telling phones to render the page at device width. Without it, mobile browsers show a shrunken desktop layout.

How big should tap targets be?

Around 44 pixels minimum with comfortable spacing between targets. Confirm by testing your key flows on a real phone.

Related tools

See all tools

Track your site visitors with Traffsite Web Analytics

Start free