Loading...
Loading...
Ready
Enter a domain on the left and run the test. Results stream in here.
Paste any page URL. The tool fetches the raw HTML document directly from the server.
It measures the HTML byte size and counts every script, stylesheet, image, and DOM node referenced in the markup.
Get the document size, estimated request total, and flags for high resource counts that commonly cause slow loads.
Page weight is the total size of everything a browser must download to render your page. Heavier pages load slower, especially on mobile and slow connections. Google uses page speed as a ranking signal, and slow pages directly hurt conversions. This tool measures the HTML document size and counts the resources it references so you can spot bloat.
It measures the raw HTML document size and counts the resources (scripts, stylesheets, images) the page links to. It does not download every external asset, so it cannot report the exact total transferred bytes including images and fonts. Use it as a fast structural weight check, then a full waterfall tool for byte-level totals.
There is no hard limit, but each request adds latency, especially before HTTP/2. As a rough guide, pages with more than 80 to 100 total requests usually have room to consolidate. Combining files, lazy-loading below-the-fold images, and removing unused scripts are the highest-impact fixes.
Most well-optimized HTML documents are under 100 KB before compression. Documents over 200 KB often contain inlined data, oversized inline SVGs, or server-rendered state blobs that could be trimmed. A very large DOM (thousands of nodes) also slows rendering even if the byte size looks reasonable.
Common causes are tag managers that inject many third-party scripts, analytics, A/B testing tools, chat widgets, and ad networks. Each external script is a separate request and can block rendering. Audit which scripts are essential, defer or async non-critical ones, and remove abandoned tags.
Indirectly, yes. Google recommends keeping the DOM under about 1,500 nodes. Very large DOMs increase memory use, slow style and layout calculations, and worsen interaction responsiveness (INP), which is a Core Web Vitals metric. Reducing wrapper divs and paginating long lists helps.
Start with the biggest wins: compress and lazy-load images, enable Gzip or Brotli compression on the server, defer non-critical JavaScript, remove unused CSS, and trim third-party scripts. Re-run this analyzer after each change to confirm the resource counts are dropping.