Loading...
Loading...
Ready
Enter a domain on the left and run the test. Results stream in here.
Paste the page URL. We fetch the live HTML so we can inspect the head section.
We read the viewport meta tag's content value and the charset declaration, checking placement and correctness.
You get a clear result for mobile viewport readiness and UTF-8 encoding, with fixes for anything missing or misconfigured.
The viewport meta tag — <meta name="viewport" content="width=device-width, initial-scale=1"> — tells mobile browsers to render the page at the device's actual width instead of a default desktop width (often 980px) scaled down. Without it, mobile users see a tiny zoomed-out desktop layout. It's essential for responsive design and a Google mobile-friendliness requirement.
Indirectly, yes. Google uses mobile-first indexing, meaning it primarily evaluates the mobile version of your site. A missing or broken viewport tag makes the page fail mobile-friendliness checks, which can suppress rankings on mobile searches and hurt usability metrics. The tag itself isn't a 'ranking factor' but its absence triggers ranking-relevant problems.
The standard is content="width=device-width, initial-scale=1". Avoid setting maximum-scale=1 or user-scalable=no, which disable pinch-to-zoom and are an accessibility violation that some browsers now ignore anyway. This tool flags viewport tags that block zooming or use a fixed pixel width instead of device-width.
The charset tells the browser how to decode the page's bytes into text. The modern standard is UTF-8, which supports virtually every character and emoji. A missing or wrong charset can cause garbled characters (mojibake), broken symbols, and inconsistent rendering across browsers. It also affects how search engines parse and index your content.
The <meta charset="utf-8"> tag must appear within the first 1024 bytes of the document, ideally as the very first element inside <head>. If it appears too late, the browser may have already started decoding with the wrong encoding and will restart, wasting time. This tool checks both presence and that the encoding is UTF-8.
Yes. The Content-Type response header can include charset=utf-8, and that takes precedence over the meta tag. Many servers set it automatically. However, including the meta tag is still recommended as a fallback for when pages are saved locally or served without the header. Having both, in agreement, is the safest setup.
Mobile browsers fall back to a virtual desktop-width viewport and shrink the whole page to fit the screen, producing tiny, hard-to-tap content. Google's mobile-friendly test will fail the page, and users bounce. Adding the single standard viewport line is one of the highest-impact, lowest-effort mobile SEO fixes available.