@Jdlrobson: What's it used for? What do we need it for? How do we stop it from loading in MobileFrontend?

@Tgr I hear you wrote this. Was enabling it on mobile an oversight or is it serving a purpose?

It's collecting image loading times for the big images on file pages, and information about CORS support. The latter needed to be done on mobile as well, but we probably already collected enough data so I'll disable it once I have the time to go through the data and verify it is valid. If you feel the image loading times are not useful on mobile, I can disable that as well. (Mind you, the file is ~200B minified+gzipped, so removing it would change the size of the head scripts by about 0.2%.)

@Tgr despite the size the concern is about whether it needs to be loaded in the head.

Thanks for looking into this.

It is top-loaded so that it can capture the load event of the image, which can happen before normal scripts are loaded.

I think the main concern will go away as soon as you make it restricted to the file pages again.

@Tgr @Gilles I've edited title based on your comment. Could it be reasonable?

Do you want us to help with this next week?

cc/ @Jdlrobson (what do you think about this?)

Fixed in https://gerrit.wikimedia.org/r/#/c/230982/.

Awesome, thanks @Tgr