- Home
- Free tools
- Page weight checker
Page weight checker
Measure the files a page asks for: how many bytes each type adds, which files are the heaviest, and which block the page from appearing.
How to use it
- Enter a page address.
- Read the weight by type and the heaviest files. The biggest wins are usually one or two images or scripts.
- Fix them and check again, then run the full audit for the speed effect.
What it checks
- HTML size, before and after compression
- Scripts, stylesheets, images, fonts and frames referenced in the HTML (sizes for up to 25)
- Render-blocking scripts and stylesheets in the head
- Files over 300 KB, and uncompressed CSS and JavaScript
- Number of script files and other hosts involved
- Total measured weight
Limits
- Measures the files referenced in the HTML, with sizes for up to 25. Files that scripts load later are not counted.
- The total is an estimate and will differ from a browser's Network panel, which includes everything that loads while the page runs.
- Measures a cold load from our server, not what repeat visitors download from their cache.
Public pages only, one page at one point in time. See the methodology and terms.
Frequently asked questions
How heavy should a page be?
Lighter is better, especially on mobile networks. As a practical guide, aim for under about 1.5 MB for the first view. Many pages are far heavier, mostly because of images and JavaScript.
Why is the real weight higher than the result?
We read the files named in the HTML. Fonts and images referenced by CSS, files loaded by scripts and API calls are not included, so treat the number as a minimum.
What does render-blocking mean?
A script or stylesheet in the head that the browser must download and process before it can show anything. Adding defer to scripts and inlining critical CSS reduces the delay.
What is the quickest win?
Usually images: resize them to the displayed size and use WebP or AVIF. After that, remove unused JavaScript and turn on Brotli or gzip compression.
How is this different from the full audit?
The audit runs Lighthouse in a real browser and reports timing metrics such as LCP. This tool is quicker and only measures bytes.
Are sizes the compressed size?
Yes, bytes sent over the network. Servers that do not compress text send much more than the same file would after compression.