Page Weight Checker
Review total transfer size, document weight, and major asset groups so you can identify which resources are contributing most to page bloat before prioritizing performance work.
What this tool checks
Total Page Transfer Weight
Measures the combined size of the HTML document and referenced page assets so you can see the overall transfer burden. Use the total as a starting point, then inspect the asset categories before deciding which resources are worth optimizing.
HTML Document Payload
Reports the raw document size separately from scripts, styles, images, fonts, and other fetched resources. An unusually large HTML payload can point to excessive inline content, duplicated markup, or server-rendered output that deserves closer inspection.
Asset Weight Breakdown
Groups scripts, stylesheets, images, and fonts by size so you can identify the categories contributing most to the page. Prioritize changes according to actual payload and page purpose instead of assuming one asset type is always the main problem.
Why Page Weight Is Useful for Performance Triage
Larger transfers can increase data use and may contribute to slower loading, especially on constrained connections or devices. A recommendation to keep key pages under 1MB is historical guidance rather than a universal rule.
Frequently asked questions
How should I judge whether a page is too heavy?
Start by comparing the page's transfer size with its purpose, audience, and required assets rather than relying on one universal cutoff. This page previously described under 1MB as ideal for mobile and under 2MB as acceptable for desktop-heavy pages, but those figures are not supported by a source URL here. Use them only as historical reference, then investigate which assets contribute most and whether each one is necessary.
What usually makes a page heavy?
Common contributors include large or poorly compressed images, oversized script bundles, unused styles, heavy font files, embedded media, and repeated third-party resources. The useful next step is to inspect the size breakdown and focus first on assets that are both large and nonessential or can be delivered more efficiently.