Set ceilings per resource type

Web teams set limits before a release so every new asset is judged against the same shared performance target.

Set ceilings per resource type. The result stays in your browser, ready to review, copy and adapt without an account or any transfer of your input.

How to use

Enter the target total weight in kilobytes in the first field.
State whether the target is for mobile or desktop.
Run the calculation to split the budget across resource types.
Record the ceilings and use them to guide the next release.

Example

A team is rebuilding a small business website. They set a total budget of 1500 kilobytes for mobile and run the calculation. The category ceilings then help designers and developers discuss image sizes before new assets are added. The team also checks the desktop target to keep priorities consistent.

Input

1500
mobile

Limits and formats

The budget is a planning target, not a live measurement of a published page.
The ceilings do not account for compression already applied by hosting or a CDN.
Mobile and desktop targets can produce different splits.
Check the units, because mixing kilobytes and megabytes distorts the result.
The output should be revisited when the content strategy changes.

Where processing happens

The budget is calculated inside your browser from the numbers you provide. Nothing is uploaded or stored outside the page, and no external service is contacted. You can change the inputs and recalculate as often as you like.

Frequently asked questions

Where do the suggested ceilings come from?

They are derived from the total weight and the device target you enter. The tool does not inspect your live site. Treat the split as a starting point that you can adjust to your own priorities.

Should I use compressed sizes?

Use the weights you trust for your planning. If you know the compressed size of an asset, enter that figure. Otherwise the result is an estimate that should be checked against real measurements.

Can I use this for a web application?

The idea works for any web page, but complex applications may need different categories. Change the budget and the resource mix to match your product. Recalculate after major front-end changes.