: What is "blocking time" in Chrome browser? According to the answer of https://stackoverflow.com/questions/15597936/blocking-time-in-google-chrome: "Blocking" is the time the request spent waiting
According to the answer of stackoverflow.com/questions/15597936/blocking-time-in-google-chrome:
"Blocking" is the time the request spent waiting for an already
established connection to become available (i.e. we're reusing a
connection that may be used to transfer another resource at the time
the request was started).
But why is it that when I refresh a page, the very first request is blocked?
refer to the screen shot:
More posts by @Si4351233
2 Comments
Sorted by latest first Latest Oldest Best
Blocking time is basically a "buffer" in browsers. Upon startup, especially, Chrome blocks most connections to decrease loading time. Eventually, the blocking time is completely removed after browsing many pages because it become impractical with Chrome fully "warmed up" on your computer. The blocking time settings are reset upon Chrome restart.
The milliseconds shown is the amount of time blocked. It usually appears at the top because the top is usually the most intensive process so it seems more reasonable to block for buffering.
I ponder this is the reason why they added a feature to run Chrome in the background for intensive users.
Browsers keep a connection to the server open for some amount of time after the page is fetched. This is so that if the page requests any additional resources (images, JS, CSS, etc), the connection does not need to be re-established. This window is generally about 10 seconds long.
If you refresh a page within this window, the refresh will use the existing open connection.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.