Skip to content

Free tools for SEO, AI search, Google Ads and local businesses. No sign-up. See all tools

DigitalSnot

Page Weight Checker: what makes your page heavy?

Total page size, requests and the biggest files, with uncompressed, uncached and blocking files flagged.

  • Free to use
  • Nothing to install
  • No sign-up

How to use the Page Weight Checker

Read what the guide says

This is the Page Weight Checker.

It shows how heavy a page is, and which files make it heavy.

Use it on your home page or a service page: big files load slowly on mobile data.

Enter the full address of one page.

Or press Try an example: a sample page of a made-up clinic, with some heavy files on purpose.

Press Measure page. It can take half a minute, as we measure each file.

The top card shows the total weight, split by type of file.

This page is under the 1,600 KiB that Lighthouse's documentation suggests.

The tiles count the requests, the files the page asks for, and the other sites they come from.

This box lists what to fix first: here, an image twelve hundred pixels wide, shown at four hundred.

Biggest files shows where making a file smaller saves the most.

Open How to fix to see why it matters and the steps.

Here, resize the image to at most about twice the width it's shown at.

Our Image Compressor can make the sizes and the srcset code for you.

Further down, two text files came without gzip or Brotli compression.

Every file is listed below, biggest first. Download the CSV for whoever looks after your site.

Make the files smaller, then check again to see the total fall.

You can also email yourself a PDF of the result.

The full address of one page. We measure up to 60 of its files, so it can take half a minute. The example is a sample page with some heavy files on purpose.

Share this free tool

About the Page Weight Checker

Enter a page address. We read the page and list every file it asks for: stylesheets, scripts, images (srcset and lazy-loaded ones included), fonts and embeds, plus the fonts and images its CSS names. Then we measure each file and show the total weight by type, the number of requests, the biggest files and the other sites files come from, with what to fix first: images in JPEG or PNG, images much larger than shown, text sent without compression, files with no cache lifetime, scripts that hold up the page and files that fail to load. Download the full file list as CSV.

How it works

  1. Step 1

    Enter the full address of a page, such as your home page or a service page.

  2. Step 2

    We read the HTML, find the files it loads and measure up to 60 of them, one at a time. It can take half a minute.

  3. Step 3

    Start with the biggest files and the "do these first" list, then check the page again to see the total fall.

Why page weight matters

Every file has to download before the page is complete, and the bigger the total, the longer that takes on slow mobile data. Lighthouse's documentation suggests keeping a page under 1,600 KiB and flags pages over 5,000 KiB. Images are often the biggest part: AVIF and WebP compress better than JPEG and PNG, and a page should not send an image larger than the size it is shown at.

How we measure

We ask each server for compressed files, as a browser does, and record the size it sends. Images, fonts and embeds get a quick HEAD request; CSS, JavaScript and SVG files are downloaded so we can check their compression and read the fonts and images the CSS names. For an image with srcset we count the largest version, which a wide or sharp screen may download. Limits from Lighthouse are named as such; the rest are our measure.

What this tool cannot do

We do not run JavaScript, so files a script adds later (chat widgets, trackers, sliders) are not counted, and an embed such as a video or a map counts only its own page, not what loads inside it. Fonts and background images named in CSS load only if the page uses them, so the real total can be lower. We measure up to 60 files within a time limit, and we do not measure speed or Core Web Vitals.

Frequently asked questions

What is a good page size?

Lighthouse's documentation suggests keeping a page's total download under 1,600 KiB (about 1.6 MB), and flags pages over 5,000 KiB. It quotes HTTP Archive data that puts the median page at 1,700 to 1,900 KiB. Smaller is better, especially for visitors on mobile data.

Which files should I make smaller first?

The biggest ones: the file table is sorted by size. Images usually come first. Resize them to the size they are shown at and save them as WebP or AVIF, which our Image Compressor does in your browser. Then remove scripts, fonts and plugins the page does not need.

What does render-blocking mean?

Lighthouse counts a script in the page's <head> without defer or async as render-blocking: the browser stops building the page until the script has downloaded and run. Add defer to scripts that can wait, or async to independent ones such as analytics. Module scripts are deferred by default.

Why does it say my files are not compressed?

Text files (HTML, CSS, JavaScript and SVG) shrink a lot with gzip or Brotli. We asked for compressed files, and the server sent these without compression. Lighthouse flags text files over 1.4 KiB when compression would save 10% or more. Turn on compression in your hosting panel, caching plugin or CDN, or ask your host.

Is this the same as PageSpeed Insights?

No. PageSpeed Insights measures how fast a page loads and its Core Web Vitals. This tool reads the page as the server sends it and measures each file, so it shows which files make the page heavy, but not how fast it feels. Use both.

Sources and checks

Rules last checked

The Page Weight Checker follows these official pages:

The page size limits (1,600 and 5,000 KiB) and the compression threshold come from Lighthouse's audit documentation; the other limits are our measure.

Scores, limits and suggestions marked "our checklist", "our measure" or "our suggestion" are ours, not Google's or the platform's. How our tools work

Related reading

Rather have us do it for you?

Tell us about your business and what you want to fix. We reply within one business day.

Talk to us Our service: Technical SEO services

More free tools

All tools

Want us to fix what the tool found?

Tell us about your business and what you want to grow. We reply within one business day with next steps, not a sales script.

  • A reply within one business day
  • A quick look at your site and search visibility before we talk
  • Your details are only used to answer your enquiry

Prefer email or a call?

[email protected]

+91 70079 75411

Popular