What it means
The page has no <meta name="viewport"> tag, or has one that fights the user: a fixed pixel width, or maximum-scale and user-scalable=no preventing zoom.
Why it matters
Without the tag, mobile browsers assume a desktop-width layout viewport — typically 980px — and scale the whole page down to fit. Your media queries never trigger, so the responsive stylesheet you built is simply not applied. The visitor gets a shrunken desktop page, unreadable text and pinch-zooming as the only way through it. Google evaluates mobile usability on the rendered mobile layout, so the same omission has a search cost.
The inverse mistake is worse for some users: blocking zoom removes the only accommodation available to a visitor with low vision, and fails WCAG 1.4.4.
How W3Audit detects it
The head of every audited page is checked for the tag, its content parsed, and the values validated: width=device-width present, initial-scale=1, no zoom restriction, no fixed pixel width. Pages are then rendered at a 320px viewport and checked for horizontal overflow and clipped content, because a correct tag with a rigid layout underneath still fails on a phone.
How severe it is
Critical when missing, since mobile visitors — usually most of them — receive a broken layout. Critical when zoom is disabled, on accessibility grounds. High for an incorrect value that produces a partly working layout, such as a fixed width or an unexpected initial scale.
How to fix it
Add the standard tag to every page’s head, once, and remove any zoom restrictions.
<!-- broken --> <meta name="viewport" content="width=980" /> <meta name="viewport" content="width=device-width, maximum-scale=1, user-scalable=no" /> <!-- correct --> <meta name="viewport" content="width=device-width, initial-scale=1" />
If adding it exposes a layout that overflows, that is the real finding: the tag was hiding a non-responsive layout, and the fix is fluid widths, wrapping and a horizontally scrollable container for wide tables.
How to verify the fix
Load the page in a device emulator at 320px and confirm no horizontal scrolling and no clipped content. Pinch-zoom to 400% and confirm zoom works and text stays readable without side-scrolling. Then check the rendered head for exactly one viewport tag — duplicates are common when a CMS and a template both add one, and the browser honours only the first.
Where this sits in your audit
This finding belongs to the UX & accessibility category — see the UX & accessibility audit for everything else reviewed alongside it, or the methodology for how its severity and score contribution are calculated. The website audit checklist includes it as a step you can run yourself.