A Shopify page can show its products while still feeling slow when a shopper tries to open a menu or select a variant. Total Blocking Time (TBT) is a lab measurement that helps investigate work happening during loading. Use it to find bottlenecks, then check whether the changes improve actual shopping interactions.
What is Total Blocking Time?
When a browser task runs for more than 50 milliseconds, the portion beyond that threshold counts as blocking time. TBT adds those blocking portions over the test’s measurement window. For example, a 140-millisecond task contributes 90 milliseconds. A 40-millisecond task contributes none. These figures explain the calculation; they are not results from a customer store.
TBT is useful for diagnosing loading responsiveness. It is not a Core Web Vital and does not directly measure the experience of every visitor. Google’s TBT documentation explains the metric and its limitations.
TBT versus INP: what should Shopify merchants watch?
Interaction to Next Paint (INP) measures responsiveness to interactions. TBT can reveal work that may interfere with those interactions, but a lower TBT does not guarantee a good INP. Treat a Lighthouse report as a diagnosis and use real-user performance data, where available, to assess customer experience.
See our guide to Shopify Core Web Vitals for the wider picture, including loading speed and visual stability.
How to investigate a high TBT result
- Choose a representative page. Start with a product page that customers actually visit, then check the home page and an important collection.
- Run a repeatable test. Use the same mobile or desktop test settings and run several measurements. Record the page, date and configuration rather than comparing unrelated scores.
- Inspect the work behind the result. Look at JavaScript execution and long tasks. Identify which resources belong to the theme, an app or an external service.
- Test a specific hypothesis. On a duplicate theme, change one identified source of overhead. Repeat the measurements and compare the shopping journey.
Our Shopify speed testing guide explains how to read lab results alongside real-user data.
Where to look in a Shopify storefront
Begin with functionality that appears on the affected page: review widgets, product recommendations, tracking integrations, popups and custom theme interactions. An app’s presence does not prove it causes the problem. Compare behavior with and without the suspected component in a controlled working theme.
Check whether scripts are needed on every page, whether two integrations provide the same feature, and whether removed apps left unused theme code. Keep essential storefront features, consent handling and purchase tracking working throughout the investigation.
Make changes safely and check the result
Use a duplicate theme and keep a record of each change. After optimization, test navigation, search where available, product options, add to cart, the cart drawer and the checkout handoff. Check mobile interactions as well as desktop clicks.
Do not apply a blanket script delay to everything. Loading dependencies and customer actions differ between stores. A better lab result is useful only when the storefront still behaves correctly.
When to choose hands-on help
If multiple apps and custom theme features interact, a technical review can help identify what to change. ChopChopify’s manual optimization plans include analysis, implementation, validation, a private project dashboard and a personalized Speed Report.
Compare STARTER, PRO and BLACK BELT optimization plans. Delivery is 7 working days once required store access is available. For ongoing loading-priority optimization, explore the ChopChopify Shopify App.
Common questions
Does a high TBT mean every customer has a slow experience?
No. It identifies blocking work under the conditions of a lab test. The effect on customers depends on their device, page and interaction timing.
Will deleting an app always improve TBT?
No. First establish whether that app contributes to the measured work. Removing useful functionality without evidence can create a worse shopping experience.
Should I chase a perfect Lighthouse score?
Use the report to prioritize problems, then verify that customers can browse and buy smoothly. A score is one part of that assessment.
