// Performance
Page weight is the amount of data transferred for the resources requested during a defined page-load scenario, commonly including HTML, CSS, JavaScript, images, fonts, media, and third-party assets. The reported total depends on the tool, viewport, page state, cache state, interactions, and whether it shows compressed transfer bytes or decoded resource size. It is therefore meaningful only with a stated measurement method.
Why it matters: Large transfers can delay useful content, consume metered data, and add processing or memory cost, but there is no universal 3 MB boundary at which every page becomes slow. Record a cold first visit and relevant repeat or interactive states under representative devices and networks. Break the total down by resource type, origin, route, and necessity; then remove unused requests, serve correctly sized modern media, compress text, split code by actual need, subset fonts, defer non-critical work, control third parties, and configure caching. Set page-type budgets from user and business requirements, track both bytes and request behavior in continuous checks, and confirm that reductions improve field performance rather than optimizing a total in isolation.
Explore related checks and guidance for page weight on your own site.
Open Page Weight AgentLooking for practical context? Start with the guidance behind these checks and definitions.
Explore website audit guidance