Makes you wonder what Mozilla is really doing with all their resources instead of optimizing for performance (which is hugely important in a browser!)

Weird that it's always GNOME applications experiencing this. I wonder why KDE/Qt or even other GTK applications never have to deal with this problem. /s