Page Breakdown
See what any page is made of.
We'll load your page in a real browser, tally every request, and break it down to show the share of JavaScript, images, fonts, CSS, and the rest. You'll also be able to see how much is first-party vs. third-party and which hosts are serving it.
The numbers you see here directly connect to the experience of every one of your visitors. They matter!
-
What'll this give me?
Total page weight, how much of it is third-party, and a cube of JavaScript, CSS, images, fonts, video, and HTML sized by share of the payload. Select a category to see hosts (and, for images, which formats you're serving).
-
What's "third-party" mean here?
Anything loaded from a domain other than your own. That includes analytics scripts, tag managers, hosted fonts, CDN assets, and ad networks. Third-party requests are often the biggest drag on page performance because you don't control their caching or size.
-
How does it work?
Your page is loaded in a real headless Chrome browser at mobile dimensions, then we record every network request it makes as it renders. Because we're using an actual browser, dynamically injected scripts and images get counted too — not just what's in the raw HTML.
-
Will you store my results?
Results are cached for one hour. Reloading or sharing a URL like
/page/breakdown?url=https://example.comwill reuse that cached breakdown instead of loading the page again. After an hour, the next visit runs a fresh analysis. -
Why do sizes look like estimates?
Sizes come from what each server reported when we downloaded the asset. Compressed or streamed responses sometimes omit that info, so totals can skew low. Counts, hosts, and categories are always exact.
-
How is this different from Request Breakdown?
The Request Breakdown tool measures a single HTTP request — DNS lookup, TLS handshake, time-to-first-byte, and so on. This tool zooms out to everything the page loads after that first response arrives. They pair well together.