2 ms·
By definition a browser can't see what's happening on the server side. There's a lot of things that can block loading (io, database, network ...). Pointing the
by tangue 14y ago
By definition a browser can't see what's happening on the server side. There's a lot of things that can block loading (io, database, network ...). Pointing the finger at an architectural pattern using data collected via a browser extension is pure speculation.
- sallamar 14y agoWhat you can infer from such testing is that the server is not writing any response for a while, and then quickly writing all the response. There could be two reasons - the server may be busy doing some blocking activity, or the server or some intermediary is buffering all the response in memory and emitting it when the complete response is available. Experience tells me that it is usually the former. I'm the author of this post.