Skip to content

Accessibility

Why my site needs a viewport meta tag

Mobile browsers fall back to rendering at desktop width and scaling the result down, so all your text is unreadably small and every tap target is tiny. It also means Google treats the page as not mobile-friendly, which matters because indexing is mobile-first.

What 13x checks

This is rule accessibility.viewport in the public registry: Viewport meta tag is present. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.

Surface
Accessibility
Score weight
6 of the readiness score
Scope
Runs on every audited page
Applies
To every site

Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.

The fix

The same text the audit hands you when this check fails on your own site.

Add the viewport meta tag:

html code
<meta name="viewport" content="width=device-width, initial-scale=1" />

Without it, mobile browsers render at roughly 980px and scale the result down, so all your text is unreadably small and every tap target is tiny. Google also treats the page as not mobile-friendly, which matters because indexing is mobile-first.

Framework-specific versions

Where the change differs enough to be worth writing out separately.

Does your site have this problem?

13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.

No signup. Results in 30 seconds.

More accessibility checks