There are two things that contribute to this behavior: By default, GSAP uses the requestAnimationFrame API to drive its "ticks". This is widely considered the best way to do it because it delivers the best performance and synchronizes updates with screen refreshes/repaints. In most browsers, requestAnimationFrame fires about 60 times per second EXCEPT on inactive tabs which typically run at around 2fps or less. This is a feature, not a bug - the browser vendors are essentially "powering down"
    • Like