Total Blocking Time Estimator from JavaScript Bundle Sizes

Models Total Blocking Time from script sizes, a CPU slowdown and task splitting.

Use the tool

Why this tool exists

TBT depends on long tasks. Bundle size is a rough proxy that helps you compare options.

Each script is treated as one or more tasks that take size times a ms-per-KB value times a CPU slowdown. The part of each task over 50 ms counts as blocking. The default ms per KB is an assumption you should calibrate with one real trace. Use the tool to see how splitting or removing a script changes the total, then verify in Lighthouse.

How to use it

  1. List scripts with their compressed size in KB.
  2. Choose the device slowdown.
  3. Enter your own ms per KB if you have a trace.
  4. Try more tasks per script to see the effect.

Frequently asked questions

Is the result my real TBT?

No. It is a model. Real cost depends on the code and the device.

Where do 4x and 6x come from?

They are the DevTools mid-tier and low-tier mobile CPU throttling presets; Lighthouse simulates 4x.

How do I calibrate ms per KB?

Divide a bundle task time in the Performance panel by its compressed size.

Is data sent?

No.