I've seen things go the other way around. As an example, use Chrome Canary to browse https://motherboard.vice.com/en_us/article/its-like-tweeting... and then use Firefox Nightly. Chrome can barely manage to keep up with scrolling while Firefox chugs along nicely.
The only issues Firefox has are when you get to media handling and non-standard APIs from Chrome. 99.9% of websites "work" on all browsers though and I haven't seen any need to run Chrome for a specific website (Google Docs used to be a case but not anymore).
This is a behavioral difference with Firefox. Chrome is currently blocking scrolling on the JS inside the wheel event handler which appears to be very slow on the linked website. Firefox is only blocking on the JS for the first event inside the scroll gesture and asynchronously scrolling after which hides the very slow JS handlers.
This is an interesting case because the Chrome behavior lets sites implement certain effects without lagging behind scrolling while the Firefox behavior favors smoothness of scrolling over JS effects synchronized with wheel handlers. In any case, Chrome is currently working towards switching to the Firefox behavior which will make sites like this scroll much more smoothly.
The only issues Firefox has are when you get to media handling and non-standard APIs from Chrome. 99.9% of websites "work" on all browsers though and I haven't seen any need to run Chrome for a specific website (Google Docs used to be a case but not anymore).