TontonTools

Page Size Checker

Check a page's total size — how heavy it is and why it's slow.

100% Free No signup Privacy-friendly Website Management
Updated Sep 2026

Share X / Twitter Facebook LinkedIn WhatsApp

How to use Page Size Checker

  1. Enter the page URL.
  2. Read the total size — under 1MB lean, 2-3MB average, 5MB+ heavy.
  3. Find the biggest contributor — usually images, then JavaScript.
  4. Fix the heaviest first: compress images, defer/minify JS, then re-check.

What is Page Size Checker?

A page size checker measures how many bytes a web page weighs — the total download of HTML, CSS, JavaScript, images and other resources needed to render it. Page weight is one of the two main drivers of load speed (the other being server response time), and it's the one you most directly control.

The numbers have real thresholds: a lean page is under 1 MB, an average page around 2–3 MB, and anything past 5 MB is heavy — slow on mobile, punishing on slow connections, and costly in bandwidth. Since most of the world browses on mobile data far slower than your office wifi, page weight is felt hardest by exactly the visitors you're likely underserving.

About the Page Size Checker

Enter a URL and see its total page size, ideally broken down by what's contributing the weight.

What the breakdown reveals: images — almost always the biggest offender (unoptimized photos alone can outweigh all the code; the fix is resize + compress, our Image Compressor); JavaScript — the second culprit (heavy frameworks, third-party scripts, chat widgets and trackers), costly not just to download but to parse on mobile CPUs; fonts — multiple weights of custom fonts add up; and everything else — CSS, video, embeds.

Why it matters concretely: page speed is a Google ranking signal (Core Web Vitals), and every second of load time measurably increases bounce and cuts conversions — the classic finding is that half of mobile visitors leave a page taking over 3 seconds. Diagnosing weight is step one of fixing it: compress images (biggest win), minify and defer JavaScript, subset fonts, lazy-load below-the-fold media. Pair with our Core Web Vitals Checker for the user-experience metrics and Page Speed Checker for response-time diagnosis.

Frequently Asked Questions

Under 1 MB is lean, 2-3 MB is average, and over 5 MB is heavy — slow on mobile and expensive in data. Lighter is faster; the target depends on content, but most pages carry more weight than they need.
Images first, by a wide margin — a few unoptimized photos can outweigh all the code combined. Then JavaScript (frameworks, third-party scripts), custom fonts, and video/embeds. Compressing images is the highest-impact single fix.
Indirectly but really — heavy pages load slowly, and page speed (Core Web Vitals) is a Google ranking signal. Beyond ranking, slow pages lose visitors: over half of mobile users abandon a page that takes more than 3 seconds.
Mobile connections are slower and less reliable than wifi, and mobile CPUs parse JavaScript more slowly. A 4 MB page that's tolerable on your desktop is a painful wait on a phone on cellular — where most of your traffic actually is.
In impact order: compress and properly size images (our Image Compressor), minify and defer non-critical JavaScript, subset/limit fonts, lazy-load below-the-fold images, and remove unused CSS and unnecessary third-party scripts.

We use cookies for analytics and to keep the tools free via ads. See our Privacy Policy.