Free tool

Page Size Checker

Measure how heavy a public page really is — the HTML document, the scripts, the stylesheets and the images — and see which assets are doing the damage.

Page address

The page is fetched by our own server, not a third party. Only public http and https addresses can be checked.

How it works

Paste a public URL

Any http or https page. The fetch happens on our server, so it works even on sites that block cross-origin requests.

We measure the page

We download the HTML, find the scripts, stylesheets and images it references, then ask each one how big it is.

Read the breakdown

You get a total weight, a per-asset list sorted heaviest first, and the response headers that explain the caching and compression.

Why page weight is an SEO problem

Page weight is not a ranking factor on its own, but it drives the ones that are. Largest Contentful Paint — one of the Core Web Vitals Google measures — is largely a function of how many bytes have to arrive before the main content can be painted. A 3 MB page on a mid-range phone over a normal mobile connection is not going to hit a good LCP no matter how clever the server is.

The behavioural cost is worse than the ranking cost. Every extra second of load time measurably increases the share of visitors who leave before the page appears, and those visitors never enter your funnel at all.

Where the weight usually hides

In our experience the order is nearly always the same. Images come first: a single unoptimised hero photograph can outweigh every other asset combined. Serving modern formats and sizing images to their actual display width usually cuts total weight by half.

Third-party scripts come second — analytics, chat widgets, A/B testing, ad tags, consent managers. Each is small on its own and each loads more code of its own. They are also the assets you have the least control over.

Your own JavaScript and CSS come third. Frameworks ship a lot of code you never call, and most sites load one enormous stylesheet on every page rather than only what that page needs.

What the numbers here mean

This checker reports the uncompressed size the server declares for each asset, measured with HEAD requests. Assets served without a Content-Length header, and pages with a very large number of assets, are sampled rather than measured exhaustively, so treat the total as a solid floor rather than an exact figure. For a full waterfall with compression and timing, run the page through a lab tool such as WebPageTest or the Network panel in your browser.

Frequently asked questions

Is the page fetched by my browser or your server?

Our server. Browsers refuse to read the content of pages on other domains, so a purely client-side checker would fail on most sites. Fetching server-side means every public page can be checked.

Do you store the URLs people check?

No. The address is used to make the request and then discarded. We keep a short-lived counter per IP address purely to rate-limit abuse, and it holds no URLs.

Why is the total lower than what my browser reports?

Two reasons. We measure only the assets referenced in the initial HTML, so anything injected later by JavaScript is missed. We also sample very asset-heavy pages to keep the check fast. Treat the figure as a minimum.

What is a good page size?

Under 500 KB is light and loads well almost anywhere. Between 500 KB and 1.5 MB is normal for a modern content page. Above 1.5 MB you are measurably losing visitors on slower connections.

Can I check a page behind a login?

No. Only publicly reachable pages can be measured, because our server requests the page as an anonymous visitor with no cookies or credentials.

Why did I get a rate-limit message?

The endpoint allows 25 checks per address every ten minutes so that one user cannot turn the tool into a crawler. Wait a few minutes and it will clear on its own.