Interactive tool

Set a performance budget before the build gets away from you

Set limits for page weight, request count, and load time, then check a build against them before it ships. The result is only as good as the budget you set, so treat it as a check, not a verdict.

FreeCost
No sign-upAccess
In your browserRuns
How-To Guide

Turning a performance target into a page weight and request budget

A performance budget calculator turns a vague goal like 'keep the site fast' into hard limits for page weight, request count and load time, worked out from your target metric and connection speed. This is for whoever sets that budget: a designer scoping a new build, or a developer trying to stop a site drifting slower release by release. Work through it once and you come out with numbers you can actually hand to a team, plus a sense of where the calculator's estimate and a real device will part company.

Level: Intermediate
Best for: Front-end developers & UX designers
Performance Budget Calculator showing page weight and request limits by asset type
  1. Set your target and connection

    Pick the metric you're budgeting against, such as Largest Contentful Paint (LCP), and the connection speed you want the page to hit it on.

  2. Read the weight and request limits

    See how that target converts into a maximum page weight and request count, broken down across images, scripts, fonts and third-party code.

  3. Turn the numbers into a working budget

    Split the total budget across your asset types and check the result against a real build, since the calculator's output is a starting figure and not a fixed law.

Performance Budget Calculator

Work backwards from a target load time to a page-weight budget, then split that budget across JavaScript, images and CSS with fonts. Pick a network, set your target, and adjust the three allocation sliders.

What is a performance budget? It is a byte ceiling you set in advance for a page, worked out from how long it should take to load on a given network, so that design and engineering decisions have a concrete number to check against instead of a vague sense of "too slow".

Formula: Time = Latency + Size ÷ Bandwidth. Rearranged: Size = (Time − Latency) × Bandwidth.

We then reserve roughly 15% for HTTP and TCP protocol overhead, so the usable budget shown below is 0.85 × that raw size.

Network conditions
Target load time
Allocate your budget

These three sliders do not need to add up to 100. Whatever you set, the actual split uses each slider's normalised share of the total.

Slider: 50% Normalised share:
Slider: 35% Normalised share:
Slider: 15% Normalised share:

Results

JavaScript0 KB
Images0 KB
CSS and fonts0 KB

Teaching note: a kilobyte of JavaScript costs more CPU time than a kilobyte of images, because it must be parsed, compiled and executed rather than just decoded. Keep JavaScript budgets tight even when the total budget looks generous.

Free Tools

Set a performance budget, then hold the build to it

The calculator lets you set a hard limit on page weight, request count, or load timing, then checks a build against it before launch. It suits anyone shipping to production, from a solo front-end developer to a team briefing a client on why a hero video needs to go. Numbers on their own don't stop scope creep; a budget agreed in advance does.

No account needed, works on any device, free to use