Skip to content
search-engine-optimizedby Netsolution
  1. Home
  2. Technical and performance
  3. Page Size Checker

Page Size Checker

Measure what a visitor discovering your page actually downloads.

Every resource on the page is downloaded with no cache, as on a first visit. Compressed and uncompressed weight are measured separately. No usage limit.

What this tool is for

A page’s weight is the most direct cause of its slowness, and it is also the simplest lever to pull. Unlike code optimisation, slimming down needs no particular skill and breaks nothing.

The value of the measurement is less the total than its breakdown. Knowing a page weighs 4 MB teaches nothing; knowing that 3.6 MB come from three images and 300 KB from fonts says exactly what to do, and in what order.

The measurement runs with no cache, as for a first-time visitor. That matters: your own browser already holds everything and gives you an impression of speed your new visitors do not share.

The useful marker: getting under 1 MB on first load already puts your site ahead of most of the web. It is an achievable target on most sites, from images alone.

How to read the results

The total transferred weight is what the visitor actually downloads, compression included. That is the figure that determines the wait on a mobile connection.

The breakdown by type names the culprit. On the great majority of sites, images come well ahead. When it is the scripts, it is usually the accumulation of third-party tools added over the years.

The number of requests counts beyond the weight. Every file implies a network round trip. Fifty small files cost more than five bundled files of the same total weight, especially on mobile.

The compressed / uncompressed gap reveals the state of compression. On text, a ratio of three to four is normal. No gap at all means compression is not enabled: that is a server setting, and an immediate gain.

The blocking resources are those that prevent display until they have loaded. They are the ones that weigh most on the LCP.

Common mistakes

Trusting how fast it feels at your desk. You test with a warm cache, a good connection, a good device. Your visitors, often, do not.

Dealing with small files before big ones. Optimising forty 2 KB icons while a 3 MB image sits at the top of the page is wasted time. Always sort by decreasing weight.

Forgetting the fonts. A regularly underestimated item, and one of the easiest to reduce: limiting the number of weights, or switching to system fonts, removes hundreds of kilobytes.

Stacking third-party tools. Every widget, banner or pixel adds weight and requests. Take an inventory of what is genuinely used: scripts from tools abandoned years ago are often still there.

Measuring only the home page. It is often the most carefully built. The inner pages, the ones that receive the organic traffic, are rarely optimised.

Going further

Frequently asked questions

What is the maximum weight for a page?

There is no official limit, but a useful marker: aiming for under 1 MB on first load already puts your site ahead of most of the web. What counts more than the total is the weight needed before the page becomes usable — the rest can load afterwards.

Does weight affect search rankings?

Indirectly, through load time, which is itself a factor via Core Web Vitals. A 6 MB page cannot show a good LCP on mobile over an average connection. Google does not measure your weight, it measures how long your visitors wait — and weight is the main cause of that.

Should I count compressed or uncompressed weight?

The transferred weight, so compressed, since that is what the visitor actually downloads. The tool shows both: the gap reveals whether compression is properly enabled. On text, HTML, CSS and JavaScript, it usually divides the weight by three or four.

Why does my weight differ from my browser’s inspector?

Because your browser already holds some of the resources in cache and does not download them again. The tool measures a full first load, with no cache — the exact situation of a new visitor, who is the one that counts.

What should I do with a very heavy page?

In order of return: images first, which are the biggest item and can be fixed without risk, then fonts, by limiting the weights loaded, then third-party scripts, by removing what no longer serves. Application JavaScript comes last, because it takes the longest to work through.

Do fonts really weigh anything?

Far more than people think. A family in four weights and two styles is eight files, easily 400 KB, and they often block the text from displaying. Two weights are enough for almost every site. A system font stack brings that item down to zero.