↑↓ to move · Enter to open · Esc to close

Page Size Checker

Measure the size of one page and its main resources on our server. Nothing is stored.

This check runs on our server. The address you enter is used only for this check and is not stored.
Built by · Updated

Mode: Page size view

Tick the box to show you are not a robot, then press Check.

How to use the Page Size Checker

  1. Enter the page URL you want to inspect.
  2. Start the check.
  3. Review the HTML size, resource totals, and the largest files, then reduce the heavy assets that matter most.

How it works

The checker fetches one page, records the transferred and uncompressed HTML size, collects linked scripts, stylesheets, images, selected preloaded fonts, and iframes from the HTML, then requests up to 50 of those resources to estimate the total page weight.

The result groups bytes by resource type and lists the 10 largest files so you can see what is driving the page size.

Examples

  • A page with a small HTML file but several large hero images can show images as the main weight driver.
  • A stylesheet-heavy page can reveal that CSS is small individually but large in total when several files are loaded.
  • A large iframe embed can appear in the size breakdown even when the main page HTML is light.

Limitations

  • The Page Size Checker measures the page and its main resources from our server. It does not run JavaScript, so resources injected later by scripts are not counted.
  • The check does not measure LCP, CLS, or INP.
  • At most 50 resources are requested from the HTML, and the report is limited to what the raw page references.
  • For a page that references more than 50 images, the Image URL Extractor lists up to 5,000 image addresses without downloading them.

If images account for most of the measured bytes, follow the guide to compressing images for a website, then measure the page again.

Frequently asked questions

What is the difference between transferred size and uncompressed size?

Transferred size is what moves over the network after gzip or brotli compression. Uncompressed size is the raw content size after the browser or server expands it.

Why are some page assets missing from the report?

Assets loaded later by JavaScript are not visible because the tool reads only the initial HTML response.

Can a large page still load fast?

Sometimes. Caching, compression, and network conditions matter too. Page size is useful, but it is only one part of performance.

Often used together with Page Size Checker.

  • Page Load Analyzer

    Measures response timing and resource headers for one page without browser rendering or JavaScript execution.

  • Image CompressorImage Tools

    Shrinks JPG, PNG, WebP, and AVIF files with a quality slider and a before/after view.

  • Website Headers AnalyzerInternet Tools

    Grades security headers, caching, compression, version exposure and cookie attributes using a published advisory rubric.