You are reading a single comment by @aggi and its replies.
Click here to read the full conversation.
-
Cheers. I get the same in Private Browsing so assume it shouldn't be an extension. It's a work laptop with a few anti-virus things installed so guess that is the most likely culprit, although strange that it doesn't do the same with Chrome..
aggi-
Oooh... likely based on protocol.
Chrome will be using HTTP/3 with LFGSS which the AV may not be able to make sense of. Firefox will still be using HTTP/2 which AV will know about.
Can confirm those protocols btw, https://www.lfgss.com/cdn-cgi/trace shows the protocol used.
Velocio
Taken a look - you have something on your system that is pausing the request connections.
If I had to suspect: You have an antivirus program or something like an extension, it is only delaying .js files (hence my suspicion on antivirus -but anything that wants to interfere with JavaScript is an option, i.e. an adblocker).
The HAR file showed all of the network communication was done in milliseconds.
But a client side (Grafana Faro) trace shows me the page took 10.7 seconds, and shows me why.
The why is that every .js was frozen in the client itself for precisely 9 seconds.
I have no idea why - but the best guess is that you have antivirus or an extension or a network proxy on your side, that is ultimately choosing to hold these requests for a short time before fully releasing them to the browser.
As a consequence of them being JavaScript files, the browser cannot paint the screen and they block/delay the page load.