Book a call Free rebuild
Home/Glossary/Performance/Total Blocking Time (TBT)

Total Blocking Time (TBT)

November 10, 2022 Updated November 16, 2026 2 min read

Performance glossaryTotal Blocking Time (TBT) is the total time that long tasks blocked the main thread between First Contentful Paint and Time to Interactive. It is a lab proxy for INP.

Total Blocking Time (TBT) measures how long a page is unable to respond to input while it loads, because its main thread is busy. It is a lab metric, reported by Lighthouse and PageSpeed Insights, and it carries the most weight of any metric in the Lighthouse performance score.

How it is calculated

A browser runs JavaScript, parses HTML, calculates styles, and lays out the page on a single main thread. Any piece of work that runs for more than 50 milliseconds is a long task, and while it runs, clicks and key presses have to wait.

For each long task, the blocking time is the part beyond 50 milliseconds. TBT adds those parts together for every long task between First Contentful Paint and the point where the page becomes reliably interactive (Time to Interactive). For example, tasks of 70, 30, and 120 milliseconds give a TBT of 20 + 0 + 70 = 90 milliseconds.

Google suggests aiming for a TBT under 200 milliseconds when testing on average mobile hardware.

TBT and INP

Responsiveness in the field is measured by Interaction to Next Paint, one of the Core Web Vitals. INP needs real people interacting with the page, which a lab test cannot provide, so TBT serves as the lab stand-in. The two are not the same: TBT only covers loading, while INP covers the whole visit. A good TBT makes a good INP more likely but does not guarantee it.

What causes a high TBT

  • Large JavaScript bundles that take a long time to parse, compile, and run.
  • Third-party scripts such as ad tags, chat widgets, tag managers, and trackers.
  • Page builders and plugins that load scripts on every page, whether or not they are used there.
  • Very large DOMs, which make style and layout work expensive.
  • JavaScript frameworks rebuilding content the server already sent, a step known as hydration.

How to reduce it

  • Remove unused plugins and scripts, and load the rest only on the pages that need them.
  • Defer non-critical scripts, or delay third-party ones until the visitor interacts.
  • Break long tasks in custom code into smaller pieces that yield back to the browser.
  • Move heavy computation into a web worker, off the main thread.
  • Reduce DOM size by simplifying layouts and deeply nested page builder sections.

Finding the culprits

In PageSpeed Insights, the diagnostics list long main-thread tasks and the scripts behind them, along with a breakdown of JavaScript execution time. In Chrome DevTools, record a page load in the Performance panel: long tasks are flagged with a red triangle, and selecting one shows which script was running.

Source: web.dev: Total Blocking Time.

WP Services

WordPress services at revolutionary pricing.

Productized WordPress services, from builds to care, delivered by Seahawk and tracked in one app. For the WordPress lovers.