What You'll Learn
You'll learn what Total Blocking Time measures and why it's particularly important for server-rendered applications during hydration.
Understanding Total Blocking Time (TBT)
Total Blocking Time is a performance metric that measures the total amount of time the main thread was blocked during the critical period between First Contentful Paint (FCP) and Time to Interactive (TTI).
Think of TBT like waiting at traffic lights on your way to work. FCP is when you leave your house, TTI is when you arrive at your desk. TBT adds up all the time you spent stopped at red lights (blocked) during that journey. Each red light might only be 30 seconds, but if you hit ten of them, that's 5 minutes of total blocking time.
Why TBT Matters for SSR
In server-side rendering, users see the page quickly (FCP happens fast), but the page isn't fully interactive until JavaScript loads and hydration completes (TTI). During this gap, the main thread executes JavaScript in chunks. Any task that takes longer than 50ms is considered "blocking."
TBT only counts the blocking portion — if a task takes 80ms, it contributes 30ms to TBT (80ms - 50ms threshold).
For SSR applications, TBT often reflects hydration cost. Heavy hydration scripts can create long blocking tasks, making the page feel unresponsive even though users can see content.
Example scenario:
- FCP occurs at 1.2s (content visible)
- JavaScript executes: 120ms task (contributes 70ms), 90ms task (contributes 40ms), 40ms task (contributes 0ms)
- TTI occurs at 3.5s
- TBT = 110ms (70 + 40)
Lower TBT means smoother, more responsive experiences during hydration.
Key Takeaway: Total Blocking Time measures accumulated main-thread blocking between when content appears and when the page becomes interactive—critical for optimizing SSR hydration performance and user experience.