Page Weight

Page weight is a measure of how much data a page transfers or otherwise loads, depending on the reporting tool's definition. HTML, CSS, JavaScript, fonts, and images may all contribute. Tools can report transferred bytes separately from decoded or uncompressed resource size, so a single “2 MB page” figure is meaningful only with its scope and conditions attached.

A home-services page with a full-width hero video, several high-resolution photos, third-party chat, and analytics tags may transfer far more data than a focused service page. An audit should sort requests by resource type, identify which files are necessary for the first view, and check which assets are cached or loaded later. Compressing images, removing unused scripts, and reducing oversized media can make a difference, but each change should be evaluated against usability and performance metrics.

Page weight does not equal Core Web Vitals or load time. Network conditions, render-blocking code, device capability, server latency, and execution costs also shape the experience. A compressed file may be small on the wire yet expensive to process. Record repeat and first-load assumptions before comparing pages, and avoid presenting a universal “ideal” page-weight threshold. This term is about byte-oriented page resources, distinct from the visual length of a page or individual image compression.