Page Size Checker
Fetch a URL or paste its HTML to measure the raw HTML weight, see how much is inline script, CSS and images, and count external resources.
Page to measure
External resources referenced
Page weight
Raw HTML weight
Raw HTML does not include files that load from their own URLs, such as external scripts, images and fonts. Use the Network tab in your browser's developer tools for the full download size.
How to use the page size checker
Enter a URL and click Measure page, or switch to Paste HTML and paste the page source. The tool measures the raw HTML weight, splits it into inline JavaScript, inline CSS, inline base64 images and everything else, and counts the external scripts, stylesheets, images, preloaded fonts and iframes the page references.
Why HTML weight matters
The HTML document is the first file the browser downloads, and nothing renders until enough of it arrives. Large inline scripts and styles make that first file heavier and can delay the first paint. Base64 images inside the HTML cannot be cached separately and are re-downloaded with every page view. Knowing the breakdown tells you where to cut.
Raw HTML vs. total page weight
This tool measures the HTML your server delivers. The total download for a page, including linked scripts, images, fonts and stylesheets, is usually many times larger. For the full picture, use the Network tab in Chrome's developer tools or WebPageTest. Raw HTML weight is the right number for spotting inline bloat and slow server responses.
Frequently asked questions
What is a good raw HTML weight?
Under 100 KB is excellent and 100 to 500 KB is healthy. From 500 KB to 1.5 MB is heavy, and beyond 1.5 MB the page is likely to feel slow on mobile connections.
Should I inline scripts and CSS?
Inline the small amount of CSS needed for the top of the page so it paints quickly. Load the rest as external files, with scripts deferred or async. Inlining everything makes every page heavier and stops the browser from caching shared code.
Why does my page feel fast even though it is heavy?
Compression such as gzip or Brotli shrinks text a lot on the way to the browser, and a fast connection hides the rest. The weight still matters on slower phones and networks, where parsing and downloading take longer.
How does this relate to Largest Contentful Paint?
LCP measures when the largest visible element finishes rendering. Heavy inline scripts can block rendering, and large inline images must be downloaded with the HTML before they can be painted, both of which push LCP later.