It seems that the main demo is a bit too busy for Chrome. I had similar issues trying to spice up a presentation website with transitions and animations. The s

It seems that the main demo is a bit too busy for Chrome. I had similar issues trying to spice up a presentation website with transitions and animations. The simpler examples[x] seem to be working much better. In my experience, Firefox and Chrome tend to perform very flakey when CSS3 transitions/animations are in question. It's like a random performance profile is chosen every time the document loads. More often than not, the second time to load the transitions/animations work great, as if the browser performed some CSS JIT, but performance often drops again on consecutive loads. I hope these features mature performance-wise, so we can start using them in meaningful ways (and also survive the 2001-style abominations that are bound to happen). I think it's sensible to use requestAnimationFrame[r] to determine if the animations aren't performing well, and disable them accordingly. [x]: https://github.com/Prinzhorn/skrollr/tree/master/examples#examples https://github.com/Prinzhorn/skrollr/tree/master/examples#ex... [r]: https://developer.mozilla.org/en/DOM/window.requestAnimationFrame https://developer.mozilla.org/en/DOM/window.requestAnimation...