
Total Blocking Time: How to Diagnose and Improve TBT
Total Blocking Time measures how much long tasks block the browser’s main thread during a lab page load. It adds up the portions of relevant tasks that run beyond 50 milliseconds. A high value can point to JavaScript or other work that leaves the page slow to respond while it is loading.
Find what occupies the main thread
Run Lighthouse on a representative page, then record a Chrome DevTools performance trace. Examine the longest tasks and which script or activity caused them. Compare a simpler page on the same site to distinguish shared work from code tied to one page, such as a large interactive map.
Make less work happen during startup
Remove code the page does not need. Split large bundles when that makes it possible to load only what the first screen uses. Defer nonessential third-party scripts or load features when users need them. Break up expensive work if one task still monopolises the main thread. Test that the new loading order keeps critical features usable.
Compare lab and real-user measurements
Rerun the same test under the same conditions, then try the page’s main interactions on a real phone. TBT is a lab metric. Use available field data for Interaction to Next Paint to understand responsiveness for actual visitors, including after initial load.