Earlier quoted context omitted.
It's almost impossible to reliably distinguish animations required for a web site to work properly from animations and changes that can and should be disabled. For example, try to distinguish (from "definitely should be blocked" to "definitely can't be blocked without breaking things"): - An ad mascot hopping up or down telling you to click it - A loading spinner spinning - A progress bar - Information you're waiting…
Spinners are a total antipattern. If loading is interrupted by an error, the spinner just keeps spinning. And there's no need to display progress every millisecond, 0.1 Hz should be enough.
> If loading is interrupted by an error, the spinner just keeps spinning.
Only if written incompetently.