Menu
All tools/ Page-weight budget
The page-weight budget

Give every byte a purpose.

Set a size budget, explore what takes up space, and plan a lighter page. A small calculator for a more deliberate website.

Free to useNo signupMade for a better web.

Starts with an illustrative example, not a measured page or universal target. Replace the numbers with compressed transfer sizes from your report or browser Network panel. No data is uploaded or stored.

Make room for what matters.

Page weight and connection settings

1 KB = 1,000 bytes. Mbps means megabits per second. The example budget of 1,500 KB is yours to change.

Transferred size by resource

Use transferred sizes after compression. Zero means no transfer; a blank field stays unknown.

Preparing calculator…

Your entered plan

The weight of your page.

1,400 KBtotal transferred size
100 KB left in your budget

93% of your 1,500 KB budget

1.12 sidealized transfer lower bound
at 10 Mbps

A network-only estimate. It does not predict page-load time, LCP, or your Lighthouse score.

Where the bytes go.

HTML
20 KB 1.4%
CSS
80 KB 5.7%
JavaScript
300 KB 21.4%
Images
800 KB 57.1%
Fonts
100 KB 7.1%
Other
100 KB 7.1%
Try a local scenario

What if your images were lighter?

Move the slider to model a smaller image transfer. Your entered plan stays unchanged. This is a scenario, not an image-quality promise or a Lighthouse score.

77%
Chosen budget usedRing fills at 100%; the number also shows an over-budget plan.
Current entered plan
1,400 KB
Illustrative lighter plan
1,160 KB

Idealized transfer: 1.12 s → 0.93 s at 10 Mbps. Excludes latency, server and browser work.

Use the estimate in context.

The calculation is entered kilobytes × 1,000 × 8 ÷ bits per second. It assumes the full connection rate is continuously available. Real pages also depend on latency, DNS and connection setup, server response, resource discovery, shared bandwidth, caching, JavaScript, and rendering. Some resources load after the page becomes useful.

Start with the largest categories, preserve necessary content and features, and measure the same page after each change.

Read more: web.dev on performance budgets and what makes up LCP.

A LITTLE MORE PROGRESS

One detail better.
What’s next?

Explore all tools