Dashboard

Sign out?

You'll need to sign in with Google again to open your dashboard.

Check explainer · v1

Page weight: transfer bytes, blocking scripts and compression

Automated

Last reviewed

Page weight is not one file. It is every response the render fetched, the scripts that stop the parser, and the text that arrived without compression.

How this check works

Three grades read the resource log of the render. Total transfer warns above 2 MiB (2,097,152 bytes) across document, script, stylesheet, image, font, media and fetch responses; third-party bytes, host counts and media bytes are listed for context but do not warn on their own. Head parser-blocking scripts — classic scripts with a src, no async or defer and no type=module — warn when at least one exists; head stylesheets are counted as reference only. Uncompressed text warns when a same-origin 2xx HTML, CSS, JavaScript, JSON or SVG response of at least 1 KiB has no content-encoding. Without resource measurements the grades report na (insufficient_signal); zero known bytes is na, not pass.

What does a failure look like?

A 3.4 MiB landing page dominated by hero media; a head analytics bundle without async or defer; a 180 KiB JavaScript file served without gzip or Brotli — each is a warning with its own fix, not a failed page.

How to fix it, step by step

  1. Compress and resize the heaviest assets, serve modern image formats, and defer media below the first viewport.
  2. Add defer or async to head scripts where order allows, and move non-critical scripts out of the head.
  3. Enable gzip or Brotli for text responses and confirm the content-encoding header survives the CDN.

What does a pass or fail look like?

Good

1.2 MiB total transfer, no parser-blocking head script, and every text response compressed.

Fail

2.9 MiB total transfer, one synchronous head script, and a 210 KiB CSS file with no content-encoding.

Frequently asked questions

Why does an empty resource log report na?

na means the audit had nothing to weigh. When the local render lane is off, or the resource log carries zero known bytes, the grade reports na (insufficient_signal) instead of treating unknown bytes as 0 and passing the page.

Do third-party requests count toward page weight?

Their bytes count in the total, and the report inventories the hosts for context. Third-party weight is not a separate failure: the rule warns on the 2 MiB total, so a heavy third-party tag matters through the bytes it adds.

Is this a performance score?

No. The page gets three warning-level grades and no Lighthouse or composite performance score. Each grade names what crossed its threshold so the fix stays specific.

This rule is one of the checks the page scan runs. Run the free page scan

Free preview; no account needed.

Visdenda check explainers · one page per published rulePage weight · v1