Page Weight Analyzer

Page Weight Analyzer shows the HTML document size (in bytes) of a URL together with how many external resources it references. It counts script, stylesheet and image tags by type so you can quickly gauge how heavy a page's structure is.

The tool only fetches and analyzes the HTML document itself on the server — it does not download individual resources like scripts or images. So the KB figure is the size of the HTML document, and the resource counts are based on the number of references declared in that document. For full transfer size, pair this with your browser's Network tab.

How page weight and request count affect performance

Slow pages usually come from two factors: too many bytes to download, and too many files (requests) to fetch. A large HTML document delays first paint, and the more scripts, stylesheets and images a page references, the more extra requests the browser must handle, which slows rendering.

• HTML size: longer markup takes longer to parse and transfer. Excessive inline styles and scripts bloat the document.
• Script count: many external scripts increase download, parse and execution cost, and raise the chance of render blocking.
• Stylesheet count: scattered CSS files delay the start of rendering. Consider bundling and merging.
• Image count: more image tags mean more requests and transfer. Consider lazy loading and modern formats.

How to read the numbers

The counts here reflect references declared in the HTML, not the bytes actually transferred. A script referenced multiple times, or resources loaded only conditionally, are all counted as static tags. A high number is not automatically a problem, but dozens of script or image references on a single page is a signal to review bundling, lazy loading and caching.

• For accurate transfer size and load time, use the browser Network tab or a field-data performance tool.
• If the HTML is unusually large, check whether server-side rendering is embedding too much inline data.
• To cut text transfer size, check whether gzip/brotli is on with the compression check, and if the page is image-heavy, review the best format with the image format recommender.

Performance budget baselines

These are widely used page-weight and request-count guidelines, set conservatively so a page still loads comfortably on mobile 3G/4G. Compare your own page against the table to spot which item blows the budget. (The total transfer figure below is HTML plus every resource — different from the HTML-only size this tool reports.)

Worked example: reading one page

Say a scan returns HTML 312 KB, scripts 41, stylesheets 9,images 60. Held against the table above, here is how to read it.

• HTML 312 KB (at risk): over the 250 KB line. An SSR framework is likely inlining a full initial-state JSON blob (e.g. __NEXT_DATA__), or the markup contains base64 inline images. Trim the inline data first.
• 41 scripts (at risk): the classic pattern of accumulated third-party tags — ads, a tag manager, A/B testing, a chat widget. Consolidate into one or two bundles and load marketing tags with async or defer them.
• 60 images: adding loading="lazy" to below-the-fold images cuts the initial request burst significantly.

Common pitfall

The most frequent mistake is treating this tool's KB figure as the “whole page size.”It is the size of a single HTML document only — the JavaScript bundles, images and fonts the user actually downloads are not included. A 30 KB HTML page that references a 5 MB script is still a heavy page. For the real total, always read the “Transferred” sum in your browser's Network tab.