The Motion Fatigue Problem
Most sites overuse motion. Parallax on everything. Constant micro-animations. Users tune out or leave. Motion fatigue is real.
Motion as Information Architecture
We use GSAP for three purposes only: guide attention to primary actions, clarify spatial relationships, signal state transitions. Everything else is static or minimal.
Motion Demo
Motion Demo
The System
ScrollTrigger for hero sections only. Max 35vh pin duration. Parallax limited to backgrounds. prefers-reduced-motion kills all motion. Performance budget: 16ms per frame.
Motion Checklist
Does this motion guide the user toward an action?
Does it clarify hierarchy or spatial relationships?
Can the experience work without it?
Is reduced motion supported?
Does it stay under 16ms per frame?
Key Takeaways
Related Insights
LCP under 1.2s, CLS < 0.1, INP < 200ms — performance budget as design constraint
Performance8 min
Performance as UX
How shipping under 1.2s LCP increased conversion by 34%
WCAG 2.2 AA minimum — accessibility debt compounds fast
Accessibility7 min
Accessibility-First UI
Building semantic, keyboard-navigable, screen-reader-optimized interfaces
