analytics.usa.gov VS firefox-performance-dashboards

They actually have an in-house solution for this: https://analytics.usa.gov/ (though based on Google Analytics)

Details here: https://digital.gov/guides/dap/common-questions-about-dap/

Data from analytics.usa.gov [1] reveals that Chrome leads browser usage at 48%, closely followed by Safari at 35.7%, highlighting the competitive proximity of Safari to Chrome. Definitely much higher share than I thought.

[1] https://analytics.usa.gov/

Firefox has 2.2% usage on US government websites according to https://analytics.usa.gov/

If it falls below 2% it may lose official support on .gov websites according to https://designsystem.digital.gov/documentation/developers/#b...

Government Web Traffic Statistics

Also on access to US Gov websites, IE is now part of "other", https://analytics.usa.gov/

(Off topic): this page linked at the bottom of cloud.gov is quite interesting. Visitor analytics for government sites.

https://analytics.usa.gov/

https://analytics.usa.gov/ reports linux as 1% and chromeos as 1.5%

> 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.