How to check web page size and find what makes it heavy

How to check web page size and find what makes it heavy

A page that looks simple can still pull in megabytes of images, scripts, and fonts. Measure the total, see which files carry most of the weight, and check that the server compresses and caches them.

A heavy page costs every visitor

Every byte a page loads has to travel to the visitor, often over a phone connection. A large hero image, a theme that loads several stylesheets, or an embedded video player can make a short article weigh far more than its text suggests.

Guessing which file is to blame wastes time. Shrinking a small script does little when one image is several megabytes, and a missing compression header can matter more than either.

Measure the weight, then check the load path

The Page Size Checker fetches one page on our server and records its transferred and uncompressed HTML size. It then collects the scripts, stylesheets, images, preloaded fonts, and iframes the HTML links to, requests up to 50 of them, groups the bytes by type, and lists the 10 largest files.

The Page Load Analyzer fetches the same page and times DNS, connect, TLS, time to first byte, and download. It checks the resources' headers for compression and caching, and flags scripts and stylesheets in the head that can block early rendering. Neither tool runs JavaScript, so they do not measure Core Web Vitals, and files that scripts add later are not counted.

Check the size of a web page

  1. Enter the page URL in the Page Size Checker and start the check.
  2. Compare the transferred and uncompressed HTML sizes. A large gap means compression is working.
  3. Read the totals by resource type and the list of the 10 largest files.
  4. Run the same URL through the Page Load Analyzer and look for uncompressed files, missing cache headers, and render-blocking files.
  5. Fix the largest files first, then compression and caching, and check the page again.

What these checks miss

  • They read the page from our server, so timings can differ from what your visitors see.
  • JavaScript is not run. Resources injected by scripts, and Core Web Vitals such as LCP, CLS, and INP, are not measured.
  • At most 50 resources linked from the HTML are requested.

Frequently asked questions

How do I check the size of a web page?

Enter its URL in the Page Size Checker. It measures the HTML and up to 50 linked files and lists the largest ones.

Why is the transferred size smaller than the page size?

Servers compress text files with gzip or brotli before sending them. Transferred size is what actually crosses the network.

Does the page size include files loaded by JavaScript?

No. Only files linked in the initial HTML are counted, because the checker does not run scripts.

Is a smaller page always faster?

Not always. Caching, compression, and server response time matter too, and the Page Load Analyzer checks those.

Tools used in this guide

  • Page Size CheckerSEO Tools

    Reports HTML size, resource totals by type, and the largest files for one page without running JavaScript.

  • Page Load AnalyzerSEO Tools

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

More from the blog

All guides