What do I do if as a normal user I find what appear to be Javascript issues? e.g. the Deluge and SabNZBd interfaces can cause massive slowdown in Firefox where Chrome seems unaffected. Often these pages are behind logins and contain sensitive information.
Filing bugs on bugzilla.mozilla.org in the "Core::JavaScript Engine" component for performance problems should get the problems in front of the right Firefox developers. However, many site performance problems are related to DOM or animations and not necessarily JavaScript. For slow sites behind logins, there's not much that can be done other than someone creating a standalone test case or working with the site owner to get a temporary test account.
Worst thing is that a site does not work with Firefox, so that one is forced to use Chrome.
Happens for the map at Google Flights (https://www.google.de/flights/) that is the No 1 search result when googling for Flights (that's of course a clever move by Google to create a top site that only works fine with Chrome, I wonder how long it will take that YouTube or GMail only work "optimal" with Chrome)
Anyway, I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1329141 but this is only P3 priority (that is, marked a "valid" bug but nobody is working on it). Which I found really "strange" because website not working in Firefox and being force to temporally switching to Chrome (and maybe staying) are the worst that can happen. Eventually, when booking a flight I even had to tell other family members that they should use Chrome for it (who were surprised because normally I tell them to use Firefox ;)
P3 is not that bad tbh. I understand that for each one of us the bug that affects us is the most important one, but working with bugzilla is a bit like data mining. We have 1.3 million bugs reported and we track our respective components, cluster similar bugs and solutions and prioritize what is affecting most people in most crucial ways.
The fact that your bug got triaged and [gfx-noted] is a good sign. It's on their triageboard now and may soon get clustered with other Google website related graphics bugs.
You'll get an email when it happens.
If you don't, you can always contact the website author and inform him about performance problems and ask him to get in touch with us. He does have access to the whole website and could help us get a temporary account for us to investigate.
If you have more knowledge and curiosity, you can even use our performance devtools to generate a profile. It's actually fairly easy - just start recording in the performance tab and do what you would normally do that is slow.
Then file a bug and attach the profile.
This will give us an insight into what takes so much time. It may not be enough, but sometimes it is, and in those cases we are able to "peak" into what your Firefox is spending so much CPU cycles on.
