See what’s making
your site heavy.
Scan your site to see how much code it ships, which third-party services come along for the ride, and where the biggest costs are hiding. Free, read-only, and no signup.
Measured by xlogs. No simulated score. We report what we could actually read from the deployed site.
What it measures
The bytes your deployment actually served: the document, every same-site script we could download, and which of them are largest. Alongside that, the third-party hosts your page loads code from, counted and named but never downloaded, and the analytics, support and marketing tools riding along in your bundle. Where something could not be weighed, the total says so rather than quietly leaving it out.
Questions
Why is there no score out of 100?
Because a score would be a judgement we cannot support. Whether 2 MB is a problem depends on your app, your audience and their connection, and none of those are visible from a scan. We report what your site ships and what is carrying the weight, and let the size speak. Google already provides a score if you want one.
How is this different from PageSpeed Insights?
PageSpeed runs Lighthouse in a simulated browser and gives you a score that moves by a few points between identical runs. This measures the bytes your deployment actually served us, so the same deployment measured twice gives the same answer. The two are complementary: one estimates the experience, this one counts what was shipped.
Why does it say “at least” sometimes?
Because we could not weigh everything. If a script could not be downloaded, or a response was larger than we were willing to read, the total is a lower bound and we say so rather than quietly understating it. A number that invites a decision has to be honest about what it excludes.
Why are third-party scripts not included in the total?
We do not download them. Fetching a stranger's CDN to weigh it would turn a read-only measurement into traffic against someone else's infrastructure. They are counted and named instead, so you can see how many separate connections your visitors pay for.
Does this change anything about my site?
No. It is the same read-only fetch a browser makes when it loads your page, and it skips the security probes entirely. Nothing is installed, nothing is executed, nothing is written.