Question 1

How is webpage size measured?

Accepted Answer

The tool fetches the page and every sub-resource (CSS, JS, images, fonts, video) using the browser's normal request path, sums up Content-Length / decoded byte length and groups them by type. Cached resources are still included so the total reflects first-load weight.

Question 2

Does this send my data to a server?

Accepted Answer

The fetch goes directly from your browser to the target site using a CORS proxy. The page HTML and resource list are processed in your browser; nothing is stored on our servers.

Question 3

What is a good webpage size?

Accepted Answer

Google recommends keeping total transferred bytes under 1.6 MB for fast 4G delivery. Aim for under 100 requests and compress images, defer non-critical JS and inline critical CSS.

Question 4

Why are some resources missing?

Accepted Answer

Resources blocked by CORS, behind authentication, lazy-loaded after the analyzer finishes, or returned with zero Content-Length (chunked encoding) may not show a size. The total still reflects what was measurable.