Page Size Checker

Page weight is how many bytes a browser transfers to render a URL, split across HTML, images, scripts, and CSS. Real weight comes from a network transfer. This screen shows those categories without downloading the URL.

Real page weight comes from a network transfer. Use the browser’s network panel, or a lab run, when you need bytes. This screen is only the shape of that report.

Total is one of the values Page Size Checker puts on screen. Total weight is the bytes transferred for the URL. The kilobyte figure is filled in on the page. Do not put it in a performance budget.

Read HTML on its own before you mix it with the other rows. The document itself is one slice of the weight. The HTML share is part of the sample split. It is not the size of the live document.

Images answers a narrower question than the headline number. Images are often the heavy slice. The image share is a sample bucket. Do not compress files because this bucket looked large.

Treat Scripts as a label with a specific job. JavaScript is another slice. The script share is not measured. A bundler report is the real script weight.

The CSS line is worth a full stop. Stylesheets and sometimes fonts sit in this bucket. The sample assigns a share without downloading CSS. Use the network panel for real stylesheet bytes.

The host is not contacted. A second run does not measure a new download. If the figures move, they are still not your site’s weight.

If you remember one sequence from Page Size Checker, remember the fields in the order they change a decision. Total matters because Total weight is the bytes transferred for the URL. In practice, The kilobyte figure is filled in on the page. The mistake to avoid is this: Do not put it in a performance budget. HTML matters because The document itself is one slice of the weight. In practice, The HTML share is part of the sample split. The mistake to avoid is this: It is not the size of the live document. Images matters because Images are often the heavy slice. In practice, The image share is a sample bucket. The mistake to avoid is this: Do not compress files because this bucket looked large. Scripts matters because JavaScript is another slice. In practice, The script share is not measured. The mistake to avoid is this: A bundler report is the real script weight. CSS matters because Stylesheets and sometimes fonts sit in this bucket. In practice, The sample assigns a share without downloading CSS. The mistake to avoid is this: Use the network panel for real stylesheet bytes. After that, the checks are simple. You did not quote the total as measured. You did not blame images from the sample bucket. You did not compare two URLs here. CSS and script shares stayed out of the ticket. A network panel is the next measurement.

The worked example for Page Size Checker, read as one scene, is this. Type https://example.com. The panel shows a total and four shares. Those numbers were not counted from example.com’s responses. Open the same URL in a browser, reload, and read transferred bytes. That total replaces this panel.

Final notes for Page Size Checker, written as decisions rather than as a table. When Total is in front of you, decide using this: Total weight is the bytes transferred for the URL. Do not put it in a performance budget. When HTML is in front of you, decide using this: The document itself is one slice of the weight. It is not the size of the live document. When Images is in front of you, decide using this: Images are often the heavy slice. Do not compress files because this bucket looked large. When Scripts is in front of you, decide using this: JavaScript is another slice. A bundler report is the real script weight. When CSS is in front of you, decide using this: Stylesheets and sometimes fonts sit in this bucket. Use the network panel for real stylesheet bytes. Then apply the checks without skipping one. You did not quote the total as measured. You did not blame images from the sample bucket. You did not compare two URLs here. CSS and script shares stayed out of the ticket. A network panel is the next measurement.

Keep Page Size Checker as this step only. When the job moves on, the Page Speed Test UI is the next page: Page Speed Test UI shows a performance score and lab-style metrics for a URL you type. The Mobile-Friendly Checker covers a different piece of the same work: Mobile-Friendly Checker asks for a URL and then shows a pass or fail plus a short list of checks.