GTMRun

Mobile viewport & page weight

Last updated: 2026-11-16

Mobile viewport configured #

Google recommendation

What it is and why it matters #

Google indexes the mobile version of your site (mobile-first indexing), and most first visits from social media and email happen on phones. Without a viewport tag, phones render your page at desktop width and shrink it, so text is tiny and buttons are hard to tap.

How we check it #

We read your homepage HTML for <meta name="viewport">.

How to fix #

Add this to <head> (most frameworks and site builders already include it):

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

Then make the layout responsive with CSS (flexible widths and media queries), and don't disable zoom (user-scalable=no or maximum-scale=1 hurt accessibility).

Homepage HTML under 500 KB #

GTMRun heuristic

What it is and why it matters #

We check the size of the homepage HTML document only, not images or scripts. An HTML document over 500 KB usually means inlined data, huge inline SVGs or an unpaged product list, all of which slow the first render on mobile connections. This is a coarse heuristic of ours, not a Google threshold.

How we check it #

We download your homepage HTML (up to just over 500 KB) and measure it. Pages at or above 500 KB fail.

How to fix #

  • Move large inline JSON or data blobs to separate files loaded on demand.
  • Serve big images and SVGs as files, not inline.
  • Paginate or lazy-load long lists.

Homepage images inside the mobile budget #

Google recommendation

What it is and why it matters #

Images are most of a page's bytes. Google's page-experience guidance measures the result as Largest Contentful Paint (LCP), with 2.5 seconds as "good"; a hero image that is not sized, compressed or served in a modern format is the usual reason a page misses it on a phone.

How we check it #

This row is measured by image-optimizer's page audit: it fetches every image your homepage serves (the candidate a phone would download when several sizes are offered), adds up what they cost one after another on Lighthouse's Slow 4G profile, and flags markup problems (no width/height, no lazy loading below the fold, a format with a much smaller equivalent). It passes when the total fits inside the 2.5 s LCP budget and nothing is flagged. A page with no images passes. If the audit does not answer, the row shows not measured. Informational, 0 points.

How to fix #

Convert the images that matter to AVIF or WebP at the sizes you actually display, give every <img> a width and height, and lazy-load what is below the fold. Paste your address into image-optimizer's audit to see each image with its bytes and a labelled estimate of what it would become.

Where page speed fits #

Real page speed is measured by Core Web Vitals: Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). Google uses them as part of page experience. The two checks above are coarse proxies; run PageSpeed Insights on your homepage for the real numbers.

Verify it yourself #

curl -s https://yourdomain.com/ | grep -io '<meta[^>]*viewport[^>]*>'
curl -s https://yourdomain.com/ | wc -c   # bytes of HTML

Runs GTMRun's own checks only — seconds, no third-party calls.

Tips #

  • Check real phones, not just resized desktop windows. Chrome DevTools device mode is close, but tap targets and fonts feel different on a phone.
  • What we learned: gtmrun.co passes both checks, but PageSpeed Insights measured its mobile LCP at 5.0 s (Google's "good" threshold is 2.5 s). Passing these two checks doesn't mean the site is fast.

Sources #