Jakub Antalik has put together a page of examples showing two-state transitions, the small animations that happen when something on a website moves between one state and another. A menu opening. A panel sliding in. A button changing when you hover over it. Frontend Masters flagged it as worth bookmarking.
This is a reference for people who build websites, not an announcement that affects yours. Nothing about your site has changed, nothing has broken, and nobody is going to penalise you for having transitions that are plain or absent entirely.
What it is worth knowing is why this kind of thing gets attention among developers. The gap between a site that feels cheap and a site that feels considered is often not the layout or the colours. It is the half second when something opens or closes. A menu that snaps open abruptly reads as unfinished. A menu that eases open reads as deliberate. Neither costs meaningfully more to build, but one of them is the difference between a customer trusting your booking form and hesitating over it.
The trap runs the other way too. Animation is easy to overdo, and overdone animation is worse than none. If your site makes a customer wait while things slide and fade before they can read a phone number, that is a cost with no return. It is also a genuine accessibility problem. Some people get motion sickness from heavy animation, and some have their devices set to reduce motion for exactly that reason. A well built site respects that setting. Many do not.
There is also a speed question. Transitions done badly can make a site feel sluggish on an older phone, which is what a lot of your customers are holding.
What to do: nothing today. But next time you are looking at your own site on your phone, notice what happens when you tap the menu. If it feels jerky or slow, that is a real thing worth mentioning to whoever maintains the site. And if you are commissioning new work, ask whether reduced motion settings are being respected. It is a short question with a clear right answer.
Reported by:
