b2KIT

Page Size Checker

Analyze total page weight, number of requests, and resource breakdown by type (JS, CSS, images, fonts).

Tested tool guide Tested browser tools Checked August 16, 2026

What Page Size Checker does and how it behaves

Enter a URL and this tool loads the page the way a browser would, then adds up everything that had to be downloaded: the document, scripts, stylesheets, images, and fonts, both first-party and third-party. You get a total byte count, a request count, and a breakdown showing which resource type dominates the weight. The result is usually a surprise: the figure includes analytics, ad scripts, and CDN fonts you never wrote, so it is almost always far larger than the sum of your own files. Sizes reflect what was transferred, which is typically the compressed size, not the size on disk.

How the result is produced

1

How the page is loaded and measured

The tool requests the URL as your browser would, with your cookies and cache. Every resource the page fetches afterward, including scripts, stylesheets, images, fonts, and third-party embeds, is recorded with its byte count and type, and the totals are summed. The page is measured once per check, so lazy-loaded content that appears only after scrolling may not be fetched, and cached resources may be served without a full download.

2

How resources are grouped and sized

Each recorded resource is assigned to a bucket: JavaScript, CSS, images, fonts, and the document itself, typically decided by MIME type or file extension. The size shown is usually the transfer size, which for text-based files means the gzip- or Brotli-compressed version, not the unpacked file on disk. This is why a page whose source files total hundreds of kilobytes can report a much smaller wire weight.

Good uses

  • Find out which resource type is responsible for most of a page's weight before optimizing, so you target image compression, script splitting, or font subsetting where it will actually move the total.
  • Confirm that an optimization worked by measuring the same page before and after, such as after swapping a framework, enabling compression, or switching image formats.
  • Check a page against a performance budget before shipping it, or compare your page's weight and request count with a competitor's to see how far apart the two pages are.

Limits and checks

  • The totals are a snapshot of one load from one machine. Cache warmth, logged-in state, ad rotation, A/B variants, and connection settings change the numbers, so two checks of the same URL can disagree even minutes apart.
  • A light page is not automatically a fast page. Bytes are only part of the cost: render-blocking scripts, image decode time, round trips, and server latency also decide how quickly a page paints, so treat the weight as one signal among several.
  • Type classification has edge cases. An SVG with an ambiguous MIME type may land in the wrong bucket, data: URLs add weight without adding a request, and resources served from cache may be counted at reduced or zero network size.

Common questions

Why is the reported weight so much larger than the sum of the files I wrote?

Because the page you load is not just your files. Analytics, ad scripts, social widgets, and fonts served from CDNs all download with it, and the tool counts every one of them. The breakdown by type usually makes the cause visible at a glance: a large scripts or images bucket you did not author.

Does this tool work for pages behind a login?

A page behind a login is measured only in whatever state the checker can reach it. If the checker does not carry your session, you get the logged-out version, which may differ from what your users load. Verify sensitive cases with your own browser's devtools network panel.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools