What is the viewport meta tag, and do you still need it?
Yes, and it is not optional. It is the one line that tells a phone to render your page at the phone's width. Without it, a mobile browser assumes your site was built for a desktop and shows a shrunken, zoomed-out version of it.
What it actually is
Mobile browsers inherited a compatibility behaviour from an era when almost no site was designed for phones: pretend to be a desktop screen, render the page wide, and scale the result down so it fits. The viewport tag switches that off and says this page knows what a phone is. Everything responsive in your design depends on it being there.
Why it matters
Without the tag a phone falls back to a compatibility behaviour browsers have carried for fifteen years: pretend to be a desktop screen roughly 980 pixels wide, render the page at that width, then shrink the result down to fit. Every responsive rule you wrote is then measured against a width the device does not have, so none of your breakpoints ever fire. The page is not slightly worse on a phone — it is a zoomed-out miniature with text too small to read and buttons too small to hit, and on most sites that is the version the majority of visitors get.
What good looks like
Every page declaring that it should be rendered at the device's own width at normal zoom, and doing so without preventing people from zooming in. That last part matters — some sites disable zoom to keep a layout tidy, which breaks the page for anyone who needs to magnify text to read it.
Being honest about it
This is a presentation detail, and it does not move your score. The tag tells a phone how to lay the page out; a crawler or an AI fetcher reads the same HTML with or without it, so we measure it, show it, and leave it out of the number. It matters a great deal to the person holding a phone, and it is nearly always already correct because every modern theme and site builder includes it. When it is missing, something unusual is going on: a hand-built page, a legacy template, or a landing-page tool that bypassed the site's normal layout.
Where most sites go wrong
It is rarely absent site-wide. The realistic failure is a single page escaping the normal template — a campaign landing page, an embedded application, a page built by a different tool — where the rest of the site is fine and one commercially important page is not. The other real problem is zoom being disabled, which passes a naive check while making the page inaccessible to a substantial number of people.
On the web
State of the Web · November 2026In November 2026, 94% of the sites we could read passed the “Mobile viewport is set” check.
Webflow sites pass it most often, at 98%. WordPress sites pass it least often, at 86%.
On the sites scanned in both October 2026 and November 2026, it stayed at 76%.
The month-by-month line counts the sites scanned in each calendar month, so it can differ from the figure above, which uses each site’s latest scan from the last three months.
Not enough history yet.
Based on the sites Bot Appétit has scanned. Most of these sites come from lists we scan for research. Not a random sample of the web.
Not sure where yours stands?
A free scan checks this and everything else in about 20 seconds — no signup. Or if it's already flagged and you'd rather it were simply handled, we do that too.
Flagged for this one? We handle it. No pitch, just a plain-English chat.
Book a call