How does google calculate waiting time and receiving time in chrome network panel?
There are 4 timing categories in google chrome network panel 1.) Blocking 2.) Sending 3.) Waiting 4.) Receiving
I would like to know what all factors are included while calculating these options.
From this link
High "Receiving Time" for HTTP Responses below 500 bytes in Chrome Devtools
an explanation is there for receiving, but I would like to know about all the options in a bit more detail. Can anyone please help me out here ?
To check what's slowing down your page, open Chrome DevTools by right-clicking on the page and selecting Inspect. Then select the Performance tab and click the Start profiling and reload page button.
"Content Download" measures how long it took to download the response to the HTTP request after the latency is over. There is more information available in the documentation.
To access the Performance tab, navigate to the website you want to profile, then open Chrome DevTools by right-clicking and selecting Inspect. Select the Performance tab inside Chrome DevTools. The easiest way to capture a performance profile is by clicking the Start profiling and reload page icon.
The Finish time in Chrome Devtools includes the asynchronously loading (non blocking) objects/elements on the page which may continue downloading way after the onLoad event for the page has fired.
It appears that the timing functions may be platform related.
I have an internal web site and the access times reported for the same transactions appear vastly different. For example, my Windows 7 (latest Chrome) shows total response times as 200ms (almost 190ms of receiving) while my Ubuntu laptop shows a total of 4ms on the Chrome Network tab.
I also put timers on my server side first, just to make sure that it was not a delay in my node.js server (running on a different ubuntu box - not the one that has the Chrome client).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With