Skip to content
CheckerGoogleRank Version française
  1. Home
  2. Technical and performance
  3. Page Size Checker

Page Size Checker

Measure what a page really weighs, and see exactly where the kilobytes go.

The page and the resources declared in its HTML are fetched and measured directly. Resources loaded later by JavaScript are not counted, so the real weight of a script-heavy page can exceed what is reported — the measurement is stated for what it is. No usage limit.

What this tool is for

Page weight is the least glamorous performance metric and the most actionable. Scores out of a hundred tell you something is wrong; a breakdown in kilobytes tells you which file to fix.

Weight also accumulates invisibly. Nobody ships a 4 MB page deliberately. It arrives one uncompressed hero image at a time, one analytics script, one icon font used for six icons — each addition reasonable, the total quietly unusable on a mobile connection.

This tool measures what the page actually transfers, breaks it down by type, and lists the heaviest items first. In most cases three files account for most of the weight, and fixing those three is an afternoon's work.

How to read your results

The total is the headline, but read it against context. A media-heavy article legitimately weighs more than a contact form. What matters is whether the weight buys anything the visitor asked for.

The breakdown by type points at the cause. Images dominating usually means originals are being served unresized. JavaScript dominating means a framework or a pile of third-party tags. Fonts dominating means too many weights, or no subsetting.

The heaviest items are where the work is. Optimisation is rarely spread evenly: a single 2 MB photograph often outweighs everything else combined, and resizing it solves the problem entirely.

Compression status is the fastest win available. If text resources are served uncompressed, enabling gzip or Brotli removes roughly 70 percent of their weight with a server-side change and no risk to the design.

The most common mistakes

Uploading images at their original dimensions. A 4000-pixel photograph displayed in an 800-pixel column transfers five times the data for no visible benefit. This single mistake accounts for most overweight pages on the web.

Loading an icon font for a handful of icons. A full icon font can exceed a megabyte to render six symbols. Inline SVG costs a few hundred bytes per icon and needs no extra request at all.

Accumulating third-party tags. Each analytics, chat or A/B testing script adds weight, a DNS lookup and a connection — and executes code you do not control on every page. Audit the list periodically; there is usually something in it nobody has looked at in two years.

Shipping an entire CSS framework. Using 5 percent of a 300 KB stylesheet means 285 KB downloaded and parsed on every page for nothing. Purge unused rules at build time.

Optimising only the homepage. Most visitors arrive from search on a deep page, not the homepage. Measure the pages that actually receive traffic — check the crawl view of those same pages while you are at it.

Related tools

Frequently asked questions

What is a reasonable page weight?

Under 500 KB is comfortable, under 1 MB is acceptable, above 2 MB is a problem on mobile networks. These are guides rather than rules: what matters is what loads before the page becomes usable. A 3 MB page whose images load lazily below the fold can feel faster than a 700 KB page that blocks on a font.

Does page weight affect ranking?

Not directly — weight itself is not a ranking factor. It affects Largest Contentful Paint, which is part of Core Web Vitals, which is part of page experience. The stronger effect is on behaviour: mobile visitors abandon slow pages, and that abandonment is measurable long before rankings shift.

Which format should images use?

WebP for photographs, saving roughly 30 percent over JPEG at equivalent quality, with support in every current browser. AVIF compresses further still but encodes slowly. SVG for logos and icons, because it stays sharp at any size and usually weighs less than a small PNG.

Why is my CSS so large?

Almost always a framework of which you use a fraction. A full framework stylesheet runs to several hundred kilobytes, of which a typical site uses under a tenth. Either purge the unused rules at build time or write the CSS the site actually needs.

Do web fonts really cost that much?

They can. A family in four weights with no subsetting easily exceeds 400 KB, and fonts block text from rendering until they load. Subset to the characters you use, limit the weights, and self-host — a font served from a third-party CDN adds a DNS lookup and a TLS handshake before it even starts downloading.

Is compression enabled on my server?

This tool reports it. Gzip typically cuts text resources by 70 percent, Brotli by a little more. It is a server setting, it takes minutes to enable, and it applies to HTML, CSS, JavaScript, SVG and JSON. A site serving uncompressed text is leaving the single largest easy gain on the table.