Check explainer · v1

Mobile viewport: missing, or zoom blocked

Automated

Last reviewed

Two ways to fail mobile: no viewport declaration, so the browser guesses the layout, or a viewport that forbids zooming, so the visitor cannot read what the layout produced.

How this check works

A page without a viewport meta fails — mobile rendering falls back to a desktop layout the browser has to shrink. A viewport that disables zooming (user-scalable=no) fails as well: the declaration works, and it takes away the one recovery tool a visitor has on a small screen.

What does a failure look like?

Legacy templates that never added the meta tag; a designer-fixed viewport with maximum-scale=1 and user-scalable=no shipped to stop accidental zoom; plugin output that overrides the theme’s correct viewport with a locked one.

How to fix it, step by step

  1. Declare the standard responsive viewport on every template: width=device-width, initial-scale=1.
  2. Remove user-scalable=no and maximum-scale restrictions from the viewport tag.
  3. Re-run the crawl and confirm no remaining rows report a missing or locked viewport.

What does a pass or fail look like?

Good

Every analyzed page declares width=device-width, initial-scale=1 and keeps zoom enabled.

Fail

Every product page ships user-scalable=no — the layout is fine, and visitors who need to zoom cannot.

Frequently asked questions

Why does blocking zoom fail the page?

Because zoom is an accessibility floor, not a preference: visitors with low vision depend on it. Locking the viewport to stop accidental pinch-zoom trades a minor annoyance for a hard barrier.

Does the check grade viewport width values?

No. It grades two things: the declaration exists, and zooming is not disabled. Exact width and scale values are layout questions the crawl does not attempt to judge.

Is there a single-page way to verify one URL?

The page-level viewport check reads the declaration on one URL; this rule adds the site-wide sweep and the zoom lock judgment, which the single-page check does not report.

This rule is one of the checks the audit runs. Run the full site audit

Free preview; no account needed.

Visdenda check explainers · one page per published ruleMobile viewport · v1