Everybody Wants the Fancy Site Until It Loads
The request comes in some version of "can you make it feel more premium." What people usually mean is motion. They have seen a site where the type assembles itself and the cards tilt under the cursor, and they want that feeling.
That feeling is real and it is worth having. It is also very easy to buy the animation and lose the sale.
The Test We Run Before Anything Moves
One question: what is this motion pointing at?
If the answer is "the quote button," build it. If the answer is "nothing, it just looks cool," it is competing with the thing you actually sell.
A few examples of motion that earns its place:
Sequenced reveals on a long page. Sections arriving as you reach them turn a wall of content into a sequence. People read further because each block gets a moment to itself.
A counter on a real number. "30,000 vehicles" landing digit by digit reads as proof. The same number sitting flat reads as filler.
A magnetic primary button. The main call to action leans a few pixels toward the cursor. It is almost subliminal, and it makes the button feel like the obvious thing to press.
Spotlight on comparison cards. When someone is choosing between three service tiers, having the card light up under the pointer keeps them oriented.
And motion that usually costs more than it returns:
A hero carousel. Nobody waits for slide two. You have split your best message into three worse ones and added a layout shift.
Full-page scroll hijacking. You have taken away the one control every visitor understands. On a phone it is worse.
Animating the whole page in on load. Every element fading up delays the moment somebody can read anything. This shows up directly in Largest Contentful Paint.
Parallax on a phone. It is janky on mid-range Android hardware, which is a large share of local traffic.
The Three Costs Nobody Mentions in the Pitch
Load time. A heavy animation library plus a WebGL scene can add hundreds of kilobytes. Google measures this and so does the person waiting on a truck's hotspot. Every effect on our own motion page pauses when it scrolls out of view, and the WebGL background is loaded separately so it never blocks the first paint.
Motion sickness. Vestibular disorders are common, and parallax and large sliding transitions can genuinely make people ill. Browsers expose a prefers-reduced-motion setting for exactly this reason. Honouring it takes a few lines. Ignoring it means some portion of your visitors close the tab and never tell you why.
Perceived slowness. An animation that takes 800ms to reveal a phone number makes your site feel slow even when it loaded instantly. Most interface motion should land between 150 and 400ms. Anything longer needs a reason.
What This Looks Like on a Real Build
On a trades site the motion budget goes almost entirely to the quote path: the button, the form steps, and the transition that confirms the message sent. The rest of the page is still and fast.
On a restaurant site it goes to the food. Images that scale slightly on hover, a menu that opens smoothly, an order button that never leaves the screen. Nothing that delays a hungry person at eleven at night.
On an events or motorsport site you can be louder, because the audience expects energy and shows up on desktop as often as mobile.
Same toolkit. Completely different budget.
The Rule
Motion should make the next step obvious. If you cannot say which step a given animation is pointing at, cut it, and spend the milliseconds on something that loads faster instead.
We keep every effect we build in one place so clients can see them running before deciding what belongs on their site. If you want to go through it, take a run through the Build Lab.