Just want to see the cases where the first byte time can be zero.
http://www.webpagetest.org/result/150129_93_13BZ/ is a weird graph where I dont see any TCP Connect/SSL Handshake/ times at all and TTFB is zero.
Beats me unless the run is reusing a previously help SPDY connection or so. Just wanted to know your thoughts on the same
Chrome + HTTPS/SPDY can sometimes cause that to happen and it’s on my todo list to see if we can get better metrics out of Chrome. It mostly stems from the fact that we have to trust Chrome to tell us about encrypted requests (other browsers we can access the byte stream directly) and sometimes at the start of a navigation Chrome has a problem accounting for things that happen while the renderer process is starting.
There are tracing hooks at the browser level (and also the netlog) that might give us the necessary information to reconstruct the timings correctly for the missing time.