SEO

TBT

Also called Total Blocking Time

A laboratory measure of how long heavy scripts keep the browser too busy to respond to taps and clicks.

Quick facts: TBT

Category
SEO
Also called
Total Blocking Time
Level
Advanced
Affects
Responsiveness, INP, Lighthouse performance score, JavaScript budget
Where to see it
Lighthouse, PageSpeed Insights, Chrome DevTools Performance panel
In this article4
  1. What TBT measures
  2. Why TBT matters
  3. Where TBT goes wrong
  4. How to act on it

What TBT measures

A browser does most of its work on a single thread. While that thread is running a piece of JavaScript it cannot respond to anything else, so a tap, a scroll or a click on a menu simply waits in a queue until the work finishes. Any piece of work that holds the thread beyond a short threshold is called a long task.

Total Blocking Time takes every long task between the first paint and the point where the page settles, and adds up only the part of each that went past the threshold. A page running plenty of code in small pieces scores well. A page with a few enormous tasks scores badly, because those are the ones a visitor actually notices.

Why TBT matters

It is the closest thing a synthetic test has to a responsiveness score. Real responsiveness is measured by Interaction to Next Paint, which needs a real person to touch the page — something no automated test can supply. TBT fills the gap by measuring the conditions that make interactions slow, rather than the interactions themselves.

That makes it the metric to watch while you are still building. It can be run on every deployment, before any visitor is exposed to the change, which catches a heavy script on the day it lands rather than a month later when real-user reporting finally reflects it.

Where TBT goes wrong

The most common misreading is treating it as a verdict. It comes from lab data: one simulated device, one throttled connection, one run. Real visitors arrive on many devices, and the phones in a typical Nepali audience are slower than the machine most tests are run on, so the true blocking cost is often worse than the report suggests.

The other problem is where the blocking comes from. On most small business sites it is not the site’s own code but the tags bolted onto it: chat widgets, review carousels, analytics, remarketing pixels, a slider plugin nobody uses any more. Each one is defended by somebody, and none of them are measured.

How to act on it

Open the performance timeline and find the longest tasks by name, because guessing wastes days. Then work in order: delete scripts nothing depends on, load the rest only on the pages that need them, and defer anything not required for the first view. Third-party tags should each earn their place, with the ones that only matter after an interaction loaded at that point instead of on arrival.

For code you own, splitting large bundles and breaking long jobs into smaller pieces lets the browser answer the visitor in between. Once the obvious weight is gone, judge the result on the real-user figures rather than the lab score, because that is what the visitor and the search engine both see. If the blocking is baked into a theme or a page builder, it becomes a page speed rebuild question rather than a settings change.

Do and do not

Do

  • Remove JavaScript the page does not use
  • Break long tasks into smaller pieces
  • Audit third-party tags for main-thread cost

Do not

  • Report it as if it were real visitor data
  • Add another container to solve a tag problem
  • Ignore it because the page feels fast on a laptop

Questions people ask about this

Is Total Blocking Time the same as Interaction to Next Paint?

No. Interaction to Next Paint records how long real visitors waited after a real tap or click, and it comes from field data. Total Blocking Time is a synthetic estimate of how busy the main thread was during loading, produced by a controlled test. They usually move in the same direction, but only one of them is what Google grades.

Why does my page feel fast but score badly on TBT?

Because feeling fast and being responsive are different things. A page can paint quickly and still lock up the moment you touch it, and you are unlikely to notice that on a powerful computer with a fast connection. Try the same page on an ordinary mid-range phone and tap something immediately after it appears.

Which scripts usually cause a high Total Blocking Time?

Third-party additions more often than a site's own code: chat widgets, review and social feeds, heavy sliders, testing tools, and several advertising or analytics tags loaded at once. Page builders that ship one large bundle for every page are another frequent cause. The performance timeline names them, so you do not have to guess.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.