Domain & Website SEO Tools
Page Size Checker
Measure the total download size of a webpage's HTML response.
- Free to use
- No sign-up
Working on it…
Running the tool — your results will appear here in a moment.
No results yet
Enter the details above and run the tool to see your results here.
About this tool
Find out how heavy a URL's HTML document is, along with its HTTP status and how long it took to fetch. A bloated document is often the first sign of inline code, oversized markup or hidden content slowing a site down.
How to use it
- Enter the URL.
- Run the check.
- Read the HTML size, status code and fetch time.
What is a reasonable size?
Most content pages have HTML documents between about 30 KB and 150 KB. Much larger documents usually contain inline scripts, embedded images (base64), huge menus or repeated markup that could be trimmed.
Why size matters
Every kilobyte has to be downloaded before the browser can start building the screen, which matters most on mobile data. Smaller documents also make crawling more efficient for search engines.
How to slim it down
- Move inline CSS and JavaScript into cached external files.
- Avoid embedding images as base64 inside the document.
- Simplify oversized navigation menus and footers.
- Enable gzip or Brotli compression on the server.
Size vs speed
Size is only one factor. To see the full loading picture, including images and scripts, use our Page Speed Checker.
Limitations
The figure covers the HTML document only, not images, stylesheets or scripts loaded afterwards. Content added later by JavaScript is not included.
A worked example
A blog's article pages weigh 900 KB of HTML each. Investigating shows that a theme embeds every icon as inline SVG in the menu and repeats the full category list three times. Moving icons to a sprite and removing duplicate lists brings the document down to 120 KB.
What usually bloats a document
- Inline scripts and stylesheets from plugins
- Images embedded as base64 text
- Huge mega-menus and repeated widgets
- Page builders that wrap content in many nested containers
- Long JSON data blobs for sliders or galleries
Checking compression
Servers should send HTML compressed with gzip or Brotli, which typically shrinks it by 70% or more. Use our HTTP Headers Checker and look for a content-encoding header to confirm it is enabled.
How the status code helps
The report also shows the HTTP status. A 200 means success; 301 or 302 means the address redirects, and the size shown belongs to the final page.
Related tools
- HTTP Headers Checker – confirm compression and caching
- Page Speed Checker – see images and scripts too
- Website Speed Test – measure server timing
Step by step: finding what makes a document heavy
- Check the size here.
- Open the page, right-click and choose View Page Source.
- Look for long blocks of inline script, style or base64 data.
- Move or remove them, then measure again.