Some of those guidelines (avoid style recalculation and use only &quot;GPU-accelerated&quot; animations) are specific to Chrome (and to other browsers of today). Style recalculation is needlessly slow today due to the lack of parallelism and typed CSSOM. And there&#x27;s no such thing as a &quot;GPU-accelerated&quot; animation, either in the spec or technically: all animations can be run on the GPU with minimal state changes. It&#x27;s just that browsers found it easiest to only optimize a small subset of cases (in the case of CSS animations, <i>really</i> small--transform and opacity), so as to keep around their legacy, originally-CPU-based, painting infrastructure. It&#x27;s good that they did that, because it let us get to <i>some</i> degree of graphics acceleration quicker, but we can do so much better.<p>I&#x27;d prefer to just improve the browsers instead of putting the burden on Web authors.