Open Terminal

Page Size Checker

Available

Check how heavy a web page is: total transfer size, compression, response headers and a breakdown of HTML, CSS, JavaScript, images and fonts.

Measure a page

Some sites send smaller images to phones.

Page weight

Enter a URL to measure its total size, resources and response headers.

How it works

The NetTools server downloads the page’s HTML and the resources it references directly (stylesheets, scripts, images, fonts), records each transfer size and content type, and reads the response headers for compression and caching. Resources loaded only by JavaScript at runtime are not included.

What is counted

  • The HTML document and resources referenced directly in it: stylesheets, scripts, images (including srcset candidates actually chosen), fonts from stylesheets, and media.
  • Transfer size is what crosses the network after compression; resource size is the decoded content.
  • Not counted: anything loaded later by JavaScript (ads, analytics, lazy-loaded content) and third-party embeds created at runtime.

Safeguards & responsible use

  • Fetches only public http(s) URLs through SSRF protection, with caps on resource count (≤ 150), total bytes (≤ 25 MB) and time.
  • Per-client rate limits; downloaded content is discarded after measuring.

Frequently asked questions

What is a good page size?

Lighter is faster. Many well-optimized pages stay under 1–2 MB in total; images and JavaScript are usually the largest parts.

What is the difference between transfer size and resource size?

Transfer size is what travels over the network, after gzip or Brotli compression. Resource size is the uncompressed content the browser has to process.

Why is the result different from my browser’s developer tools?

The checker does not run JavaScript, so resources loaded by scripts (ads, analytics, lazy-loaded images) are missing, and nothing is cached.