Course contentsShow
← Web Development
Lesson 1908 of 2,98235. Web Performance FundamentalsFree lesson

Total Blocking Time (TBT)

Sum of all long tasks blocking the main thread between FCP and Time to Interactive.

What You'll Learn

You'll learn how Total Blocking Time measures the sum of all periods when the main thread was blocked long enough to prevent user input during page load.

What Is Total Blocking Time?

Total Blocking Time (TBT) is a lab metric that quantifies how much time the browser's main thread was "blocked" by long tasks between First Contentful Paint (FCP) and Time to Interactive.

Think of it like waiting at a busy restaurant. From the moment you see your table (FCP) until you can actually sit down and order (Time to Interactive), there might be several moments when the staff is too busy to acknowledge you. TBT measures the total time you spent waiting during those awkward "blocked" moments.

How TBT Is Calculated

The browser tracks every long task (any task taking longer than 50ms) during the critical loading window. For each long task, TBT adds the blocking portion—the time beyond the initial 50ms—to the total.

For example:

  • A task taking 80ms contributes 30ms to TBT (80ms - 50ms)
  • A task taking 120ms contributes 70ms to TBT (120ms - 50ms)
  • A task taking 45ms contributes 0ms (below threshold)

Sum all these blocking portions together, and you have your Total Blocking Time.

Why TBT Matters

TBT strongly correlates with First Input Delay (FID) in real-world conditions. While FID measures actual user experience, TBT gives you actionable lab data during development—you can measure it repeatedly without waiting for real users.

Lower TBT means users can interact with your page sooner, leading to a more responsive experience during load.

Key Takeaway: Total Blocking Time measures the cumulative duration that the main thread was blocked by long tasks between FCP and Time to Interactive, serving as a reliable lab proxy for interactivity issues.