[124816]

Yep, GA used to have the occasional problem with that, though I've been told some of it was due to a bug in the browser (Firefox's) code that decided what to put in the "Waiting for xyz..." spot -- if that's what you're referring to.

(Something about that bar not being updated until the first byte of the stream was read -- so if a static.foo.com was hanging connections, it would get stuck blaming whatever loaded right before it.)

GA now has asynchronous tracking though, which solves this pretty nicely. Though I'm not a JS guy, my understanding of it is that instead of sourcing the script and then issuing the tracking calls, you put some instructions into a global variable, and then source the script. Nothing blocks on the script's loading, so even if GA is down the rest of the page is supposed to load correctly. Once the GA script loads, it looks at the global and runs the tracking commands.

[loup-vaillant]

I do use Firefox, so I probably hit that bug. Also, with NoScript, forbidding GA causes no problem.

But still, I would have liked the analysis process to be completely invisible from the client.