This could really just be that part. I have a hard time imagining explicit sabotage of FF on the gmail frontend. The likeliest explanation is that perf testing and the like only happens in Chrome
It's tricky to share a screen recording because there's personal information. But I just did two for my own curiosity. From a fresh load, once the "Loading Gmail" screen has gone away, it took 8 seconds and 11 seconds respectively from clicking 'Compose' to having a new window open.
Maybe there is variability. There are a million combinations of factors out there. I suppose as an engineer you make the trade off of "do I hope for the best case" vs "do I make something that works for a broad audience". The previous version shows that they can make something that works for my own anecdatapoint if they want to.
It's just horrible to use in firefox (in arch linux) and I'm currently looking for a new provider.
I might just go all in and use protonmail.
https://protonmail.com/support/knowledge-base/custom-domain-...
>ten seconds to load your inbox
>16 GB, i7, SSD, 100 MB/s internet etc.
>fine