Comment Test is pointless (Score 1) 358
Chrome is faster because it massively favors speed over customization and features. FF is slower because it favors customization, and assumes, correctly, that no one actually actually gives a flying fark if it needs slightly more than a 1/50th of a second to render a page that Chrome can do in 1/100th of a second. This isn't a problem, nor is it news. Now of course, you may do the occasional task where those milliseconds actually matter because your browser is processing something enormous, but then just install both browsers, use Chrome in those rare instances, and use FF for a primary browser.
Frame rate isn't really an issue either. You can point out that the human eye sees at roughly 60 FPS, so going under 60 is undesired, but let's be realistic. Those Flash games are usually built at 20-25 FPS, because running at 60 would make them freaking huge. Video on the web likewise runs at 60 FPS roughly never, because it needs to stream. Downloaded video WILL run at 60, but your browser isn't playing that.
This doesn't mean there isn't a couple of very specific tasks that FF is abnormally slow at and could use a code cleanup on, but for the most part, FF's speed difference vs. Chrome is utterly negligible in actual use.