This. I did not find other comments like this in this thread. 6% M2 cpu (even single core) is a huge computing budget for such a small feature. At this point

This. I did not find other comments like this in this thread. 6% M2 cpu (even single core) is a huge computing budget for such a small feature. At this point I don't really understand why OP seems happy with this result (sorry). I think even a naive canvas implementation can really and quite easily cut most of this computing budget. Also, a pure css animated thing should use mostly gpu in a right DOM implementation. I think some issues remains in this result. Maybe OP displays it's app on a 240hz external screen which makes browser compute DOM animation at 240 fps requiring slighly more compute in a passive way (4o-mini suggests this, I am not sure browser works like this) I remember too much of my pentium 1 166Mhz let run entire age of empires 2 game in 1997