firefox-performance-dashboards VS web-bugs

> Show me these pages that Firefox doesn't render well.

I'm not doing homework for you. Lots of pages don't render well in Firefox, it's a well known issue which is why it comes up in every thread about Firefox.

> Show me pages that tank Firefox performance.

Firefox in general performs poorly. Again, known long-term ongoing issue. Look at this thread where almost every top-level comment is sceptical that Firefox is even close to Chrome in performance: https://news.ycombinator.com/item?id=36770883

You can find ongoing performance benchmarks between Chrome and Firefox here, and it's not flattering for FF: https://arewefastyet.com

> How many of them will have -webkit-* and other engine-exclusive markup/CSS?

I don't care, at all. It's not my job, as a user, to debug performance problems.

> Firefox updates every 6 weeks, just like Chrome.

Ok? I didn't say anything about update cadence.

The link is terrible. Maybe the article should link to https://arewefastyet.com or maybe the Speedometer selection at https://arewefastyet.com/win10/benchmarks/raptor-desktop-spe...

Well I would wager a guess it's due to consistency. The full site includes a bunch of different benchmarks, with a lot of them having the y axis as execution time in milliseconds. Meaning, lower is better. They probably just wanted to keep that consistency even with tests that use scores. Definitely a bit misleading without the full context. The full site is arewefastyet.com

They do... They just don't have the resources Google does. If you see https://arewefastyet.com you can see that Firefox has been steadily improving in speed, and they have actually recently been working to make react faster.

I filed a bug for that.

The thread is very long, here is the relevant comment:

https://github.com/webcompat/web-bugs/issues/131916#issuecom...

https://github.com/webcompat/web-bugs/issues?q=is%3Aopen+is%...

Microsoft Teams (which I don't think many people use voluntarily) in particular breaks in stupid ways - and then in others if you spoof your user agent.

a link to the video would help with troubleshooting, seems like another case of "this site or this particular feature doesn't support firefox" otherwise report to https://webcompat.com/

Have any of you faced this? If the website is made to open only in chromium-based browsers, I am planning to report to Webcompat. But before that, I thought I would make sure from others. Any experience or quick fix would be appreciated.

Teams was a classic hellhole for me when I was using Linux. Nowadays it lets you in but Firefox genuinely doesn't support all of the features the Teams site uses. This means certain features are made unavailable to Firefox users. Forcing the user agent makes some of these partially work but they are also still broken so Mozilla doesn't want to enable a user agent override by default and Microsoft doesn't want to enable a feature that only half works.

This GitHub WebCompat issue serves as a good example history https://github.com/webcompat/web-bugs/issues/77892

https://github.com/webcompat/web-bugs/issues/125920#issuecom...

having recently looked at a firefox performance regression for filing a bugreport, tooling that tracks performance (quite publicly) sees attention, easy upload to share tracing profiles also helps: https://firefox-source-docs.mozilla.org/testing/perfdocs/ind...

Their dedicated blog keeps you posted if firefox perf is your interest https://blog.mozilla.org/performance/

If you have a particular website you notice chromium being significantly faster with, for an easy report, there's https://webcompat.com/ - though bugzilla is better than it seems when coming from github issues