- Shipped
- August 20, 2026 at 8:49 PM UTC
- Author
- Kamo
- Commit
- eb29030
Restored exactly as it was — same two-layer gradient, same 120deg band, same 9s/1.1s timing and easing — after removing it in the compositing pass. The cost is precise and worth stating rather than leaving to be rediscovered: it is the one animation on this page that cannot be composited, because a text-clipped sweep is moving paint inside glyph shapes and no transform or opacity expresses it. Measured with getAnimations(): desktop 2 -> 3 (the extra one is this) mobile 1 -> 1 (unchanged) Mobile is unchanged because the =<767px kill-switch already sets `animation: none` here, and mobile is where the performance score is measured. A phone renders the resting fill and nothing loops. The other 25 elements from the original audit stay on the compositor. The comment on the rule now says all of that, including that the masked-overlay workaround was tried in this codebase and measured worse (34 -> 41), so nobody re-derives that the hard way. Verified by scrubbing the animation to the frame where the band crosses — solved for it rather than guessing, since the easing is front-loaded and eyeballed timings kept landing after the pass — and screenshotting at 2x: the olive band is on the leading edge of the headline, absent in the parked frame.