Page weight & requests
Every request the page makes on a cold load: request count and total transfer size over the wire.
At a glance the headline numbers for Page weight & requests
Every request the page makes on a cold load: request count and total transfer size over the wire.
The typical page weighs 2.3 MB across 71 requests.
Distribution & median INP site count and median INP at each level of page weight & requests — n
Passing INP by page weight & requests — n which level passes the INP most often
Page weight & requests — n 71. p75 120. p99 439. At the low end (1–2): INP 45ms. At the high end (>p98): INP 68ms. computed
Distribution & median INP site count and median INP at each level of page weight & requests — size
Passing INP by page weight & requests — size which level passes the INP most often
Page weight & requests — size 2.3 MB. p75 4.5 MB. p99 33.3 MB. At the low end (0 KB): INP 47ms. At the high end (>p98): INP 54ms. computed
Why this matters for the Core Web Vitals, and where to start fixing it
Page weight is a bandwidth problem. The network can only move so many bytes per second and every resource on the page competes for that capacity. The LCP image does not load alone. It shares bandwidth with every script, stylesheet and tracking pixel that loads at the same time. A heavier page means the main content arrives later.
Request count matters next to the bytes. Every request adds queueing and scheduling overhead. On a busy connection important requests wait behind unimportant ones. Script bytes keep costing after the download. The main thread has to parse and execute them, and that delays interactions (INP). The resource type breakdown shows where the bytes sit.
How does page weight affect the Core Web Vitals?
Passing LCP barely moves across the range: 86% at one end, 83% at the other. This signal does not separate passing sites from failing ones.
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.