Page Size Analyzer

Analyze total page weight, resource breakdown, and optimization opportunities

In 30 seconds

  • A lighter page is almost always a faster page, especially on mobile.
  • Start with the largest files. One 2 MB file beats twenty small fixes.
  • Images and JavaScript are usually the biggest chunks.

What’s making this page heavy?

Enter a URL and we load the page in a real Chrome browser, record every file it downloads, and add them up:

Why weight matters

Every byte has to cross the visitor’s connection before the page is complete. On fast desktop broadband a heavy page might feel fine. On a phone on a train, it’s slow, eats data and drains battery.

Weight also drives the numbers Google cares about. Big images delay Largest Contentful Paint, and big JavaScript bundles take time to download, parse and run, which blocks the page and makes it slow to respond.

There’s no official limit, but plenty of well-built content pages come in under 1 to 2 MB. If yours is several times that, there are usually easy savings.

How to slim it down

Images

The biggest culprit on most sites. Resize to display size, compress, serve WebP or AVIF, and lazy load anything below the fold. The image SEO analyzer lists every image with its size.

JavaScript

JavaScript costs you twice: once to download, again to run. Drop libraries and plugins you don’t use, split bundles so each page loads only what it needs, and look hard at third-party scripts.

Watch out

Chat widgets, heatmaps and ad tags can easily outweigh your own code. Check the largest files list for other people’s domains.

CSS

Big stylesheets often contain styles for every page on the site, or a whole UI framework when you use three components. Remove unused CSS and combine small files.

Fonts

Every weight and style is a separate file. Use fewer weights, serve WOFF2, subset to the characters you need, or use system fonts for body text.

Video

Background videos and autoplaying embeds can add megabytes. Show a poster image and only load the video when someone presses play.

Compression and caching

Quick fix

Turn on gzip or Brotli for HTML, CSS and JavaScript, and set long cache lifetimes on versioned static files, so returning visitors don’t download them again.

Working through the largest files

Start at the top. For each big file, ask three questions: does the page need it at all, can it be smaller, and can it load later instead of during the first load?

Quick answers

Why is the size different from my browser’s?

Compression, caching, screen size and changing content like ads all affect it. We load the page fresh at desktop size, so compare results from this tool over time.

Is smaller always better?

Not if it means cutting what people came for. Cut the waste: oversized images, unused code, needless scripts. Pair this with the page speed test to see how weight turns into load time.