![how to reduce page size wix how to reduce page size wix](https://d2x3xhvgiqkx42.cloudfront.net/12345678-1234-1234-1234-1234567890ab/651c25b0-2d60-43c8-addf-1df2fd575568/2022/03/10/51f0af53-a0ef-4ae6-984a-80a874e4c5bd/b998a972-ca5b-406e-9352-e0a75f09a75f.gif)
Let’s examine the example below, to understand this situation, better. Without the Total Blocking Time, Time to Interactive can’t give the right User Experience situation solely.
![how to reduce page size wix how to reduce page size wix](https://d2x3xhvgiqkx42.cloudfront.net/12345678-1234-1234-1234-1234567890ab/8696077d-830a-4b1e-bd86-9df98f89994a/2020/11/04/a99e543c-8f25-4cc8-8232-0d5800e42aba/1a4ef98b-897c-4ddb-9201-0df88546da55.png)
Thus, Total Blocking Time and Time to Interactive are complementary terms to each other. Time to Interactive is a necessary metric for understanding that when the web page is “fully” and “continuously” interactive. If the main thread of the browser doesn’t encounter a long task for 5 seconds, Time to Interactive happens. Total Blocking Time (TBT) is also related to the Time to Interactive (TTI) like First Input Delay (FID) and First CPU Idle. What is the Relation Between Total Blocking Time and Time To Interactive
![how to reduce page size wix how to reduce page size wix](https://www.seoptimer.com/blog/wp-content/uploads/2018/10/image2-8.png)
6 Last Thoughts on Total Blocking Time and Holistic SEO and UX.Importance of Response Time of the Server for Total Blocking Time Optimization Decrease the Size of the Web Page Assets’ Size and Request Count to Optimize the Total Blocking Time Minimize the Browser’s Main Thread’s Work to Optimize Total Blocking Time Reduce the Size of the Third Party Scripts to Optimize the Total Blocking Time 5.1 1.Reduce the Request Count of the Third Party Scripts to Optimize Total Blocking Time.
#How to reduce page size wix how to
![how to reduce page size wix how to reduce page size wix](https://d2x3xhvgiqkx42.cloudfront.net/12345678-1234-1234-1234-1234567890ab/651c25b0-2d60-43c8-addf-1df2fd575568/2022/03/08/69771d62-144f-482a-b0eb-4f936a54d4bd/191256bd-c136-48b4-9515-a172f910dfa4.png)
And every MS after the first 50 MS for every Long Task will be counted as Total Blocking Time. Every task that longer than 50 MS is a long task. You may check the graph that shows the Total Blocking Time visually below to understand the term better.Įxample of tasks during the web page loading process for the browser’s main thread. If a web page can’t respond to the users’ input longer than 50 MS, users will notice the delay. If TBT is optimized, load-responsiveness will be better and First Input Delay, First CPU Idle also will create a better user experience. Total Blocking Time measures the total time that the browser’s main thread is blocked by tasks longer than 50 ms. First Input Delay measures when a user can interact with the web page as much as possible earlier while First CPU Idle measures when the first time that browser’s main thread is idle and can respond to the user. Total Blocking Time is closely related to First Input Delay and First CPU Idle web page performance metrics. Long Tasks are blockers because Browser can’t interrupt or stop a task and during the long task, the browser can’t respond to the users’ input. Long tasks are blockers for the Main Thread of the Browser that are longer than 50 MS. Input responsiveness or the interactivity between the web page and user during the loading are related to the “Long Tasks”. Total Blocking Time is an important user-centric performance metric that compares the time amount of non-responsive and responsive time during the rendering phase of the web page. Total Blocking Time (TBT) is a load responsiveness metric that measures the usability of the web page during the loading.