HTML Page Size Analyzer
Break down what the HTML document is made of: markup, inline CSS and JS, comments.
About this tool
Breaks down the HTML document itself — how much is markup, how much is inline CSS and JavaScript, how much is comments, and how many elements the browser has to build.
This measures the one document that was fetched, and nothing else. Total page weight means downloading every image, script and stylesheet too, which is a crawl rather than a request. Rather than guess at a number it cannot know, this reports what one fetch establishes: the document a browser must parse before it can even discover the rest.
Common questions
How big should an HTML document be?
Under about 100 KB before compression is comfortable. Past that, parsing itself becomes measurable on a mid-range phone, and it is usually a symptom — inlined CSS, a large state blob, or markup generated per row.
Does this measure total page weight?
No, and it will not pretend to. It measures the HTML document only. Images and external scripts are usually most of a page's weight, and finding them all means crawling the page rather than fetching it once.
Is inline CSS bad?
A small block of critical CSS is a deliberate optimisation. A large one is usually an accident — it cannot be cached separately, so every page pays for it on every visit rather than once.
Why does the DOM element count matter?
Every element costs memory and time in layout and style recalculation. Lighthouse warns past about 1,500. A very high count usually means deeply nested wrapper divs rather than genuine content.