For me a good example have always been https://kangax.github.io/compat-table/es6/ which rendered very poorly on Firefox. I see it's better now, but still, try to hover over the table (do couple of mouse movement, some circles or something) and see that it's not as responsive as Chrome is.

Another example is iD[0] Editor on https://www.openstreetmap.org/. But there, to be fair, it's also slow on Chrome but I feel it's a bit slower on Firefox.

[0] https://github.com/openstreetmap/iD

> https://kangax.github.io/compat-table/es6/

Oh man this was a rough one both for FF and Chrome but Chrome did perform better slightly on cursory glance.

Thanks for providing these links, they're definitely a good rule of thumb benchmarks to test new browsers

That 3D website ( https://bruno-simon.com/) ran well enough though it did cause my laptop's fans to run but I believe that happens in Chrome too.

So far, I haven't found much of a difference in performance of websites but it's still early times for me.

I tested this on FF/Chrome/Safari on an M1 Max, couldn't see any difference at all between FF and Chrome but on Safari it was incredibly slow (which actually let me drive the car, that thing turns fast). I also wasn't aware prior to clicking that it was even possible to create web apps like this.

That person (Bruno Simon) is fantastic at creating 3D experiences on the web. He has a course on three.js too that I hope to buy and go through hopefully within this year.

Doppio (JVM implemented in JS) is absurdly slower for running java programs in Firefox compared to Chrome.