A hand releases a card, its path shown as a series of frames, the last frame blue

Website Animation: When It Helps and When It Hurts

A button that subtly responds under your finger, a panel that slides out from where you tapped, new rows easing into a list: animation like this barely gets noticed, but without it an interface feels unresponsive. A five-second intro, blocks that float in with every turn of the scroll wheel, and a background with a life of its own get noticed by everyone. And often they make people close the tab.

The difference isn't the designer's taste. It's whether the motion serves what the person is trying to do. Let's look at why web design needs animation, where it helps and where it gets in the way, how to protect speed and accessibility, and how to spec motion design so developers build exactly what was intended.

Why interfaces need animation

In an interface, motion does four useful jobs. If an animation does none of them, simplify it or remove it.

Here's a good test: turn the animation off and walk through the main user flow. If it becomes unclear what's happening, the animation was useful. If nothing changes except a feeling that things got plainer, it was decoration, and its cost is worth weighing.

Micro-interactions vs. "wow" effects

Micro-interactions are small movements in response to actions: hover, tap, toggle, loading, error. They're short, repeat hundreds of times and are almost invisible. "Wow" effects are big scenes: an animated hero section, 3D objects, elaborate page transitions, scroll-driven storytelling. They're designed to be seen and remembered.

Micro-interactions"Wow" effects
PurposeFeedback and clarityImpression and brand image
WhereButtons, forms, menus, lists, cartHero section, promo, product showcase
How often seenWith every actionOnce or twice per visit
DurationFractions of a secondSeconds
Page weightAlmost none, CSS is enoughOften libraries, video, WebGL
RiskLow, if they're shortSlow loading, distraction, trouble on low-end phones

On a commercial site, the usual balance is careful micro-interactions wherever there's an action, plus one or two showpiece moments where people are still getting to know the brand. In the catalog, the cart, the contact form and the customer account, "wow" gets in the way: people came to get something done, not to watch.

The more often someone sees an animation, the shorter and quieter it should be.

Scroll animation and parallax: where the risks are

Scroll animation is when blocks appear, slide in or change as you scroll. In moderate doses it helps: it marks the start of a new section and brings a long page to life. Problems start when every paragraph appears this way.

The safe option is content visible by default, with animation only as decoration. The reveal fires once, it's short, with a small offset, and the text itself is in the markup and accessible without JavaScript. To track when elements enter the viewport, browsers offer IntersectionObserver, which doesn't load the page the way listening to every scroll event does.

Duration and easing

For interface transitions, the generally accepted benchmarks are in the range of a few hundred milliseconds. Feedback on hover and tap is made nearly instant, tens of milliseconds. Showing a tooltip, switching a tab or expanding an element takes roughly 150–300 ms. Larger movements, such as a full-screen panel, can take a little longer, but if people get bored waiting, the transition is too long.

A few rules that work almost every time:

Animation and site speed

The browser renders a page in several steps: it calculates where elements go (layout), fills them in (paint) and assembles the layers (composite). If you animate width, height, margins or position via top and left, the browser recalculates the layout on every frame. On a powerful laptop you won't notice; on a budget phone you'll see stutter.

So the rule is simple: animate transform and opacity, not layout. The browser usually handles translation, scaling, rotation and opacity at the compositing stage, without recalculating the page. Expanding a block by height can also be done with transform, or carefully limited to a single element.

Video, Lottie and heavy libraries

A background video in the hero section is a common cause of slow loading. If you really need it, compress it, add a poster image, and skip it on mobile or load it after the main content. Lottie and similar formats are convenient for designers, but both the animation file and the player add weight, and complex scenes tax the CPU. Animation libraries are worth adding when you can't do without them, not for a couple of reveals that CSS can handle.

Core Web Vitals: CLS and INP

Animation affects the metrics Google uses to assess user experience, and you can measure it. CLS (Cumulative Layout Shift) counts unexpected content shifts. If a block changes size as it appears and pushes its neighbors, that shift goes into the metric; movement via transform doesn't count as a layout shift. INP (Interaction to Next Paint) shows how quickly the page responds to an action. Heavy animation scripts that hog the main thread delay the response to a click.

Accessibility: prefers-reduced-motion, flashing, autoplay

iOS, Android, Windows and macOS all have a "reduce motion" setting. It's used by people who get motion sick from animation, who get headaches, or who find movement makes it hard to focus. The browser passes this setting to the site through the prefers-reduced-motion media query, and the site should respect it: remove parallax, scroll reveals and large transitions, and keep instant state changes or a gentle opacity fade.

That's how our own site works: blog post headlines appear word by word, but when "reduce motion" is on, the effect is turned off and the headline is visible in full right away. It's a few lines of CSS, not a separate version of the site.

Animation on mobile devices

The phone is the most demanding place for animation. Processors are weaker than laptops', the battery drains, the connection is unstable, and the screen is small, so a large movement takes it over entirely. What looks smooth in a Figma prototype can stutter on a budget Android.

Mobile has no hover, so hover effects are useless there: feedback has to come on tap. Gestures, such as swiping or dragging a panel, should move the element with the finger, without delay, and the animation after release continues that motion rather than starting a new one. Parallax and heavy scenes are often simplified or switched off entirely on phones.

How to spec animation for development

"The block slides in nicely" means something different to everyone. For the result to match the intent, animation is handed off to development as precisely as spacing and colors.

  1. Prototype or video. Show the motion: a clickable Figma prototype, a clip or a screen recording. You can't describe smoothness in words.
  2. Trigger. What starts the animation: hover, tap, entering the viewport, data loading, an error.
  3. Properties and values. What changes and from what to what: opacity from 0 to 1, a 16 px offset, scale from 0.96 to 1.
  4. Duration, delay and easing. Specific values in milliseconds and the name of the curve or its parameters. Better yet, a reference to a design system token.
  5. Reduced-motion behavior. What remains when the user asks for less motion: nothing, opacity only, or an instant change.
  6. Acceptance on a device. Testing on a real mid-range phone, not just on a work laptop.

We build animations into the design system from the start, alongside the components, and test them in the actual build, not just in mockups. As a web design and development agency, we've collected examples of sites we designed and built on our work page.

Common mistakes and a checklist

Other mistakes we see most often:

Before launch, run through a short list:

FAQ

Does animation affect SEO?

Not directly, but indirectly, yes. Heavy animations slow down loading and hurt Core Web Vitals, and content that stays hidden until a script fires may not get indexed. Lightweight CSS animations on content that is visible by default have no effect on SEO.

What is prefers-reduced-motion?

It's a CSS media query that tells the site the user has turned on the "reduce motion" setting in their operating system. The site uses it to turn off or simplify animations: removing parallax, scroll-triggered reveals and large transitions.

How long should a website animation last?

For interface transitions, the generally accepted benchmark is a few hundred milliseconds: feedback on a tap is almost instant, while expanding and revealing elements takes roughly 150–300 ms. If you have to wait for an animation, it's too long.

Do we need a separate library for animation?

For most micro-interactions and reveals, CSS is enough. Libraries are justified for complex scenes, chained sequences and multi-step scroll animations, but every one of them adds weight to the page.

Let’s discuss your project
Related reading