A page that moves, not a page that fidgets.
Motion exists to guide the eye and make things understood. Used badly it tires and slows. Used well it is the difference between a site people visit and a site people remember.
What it solves
Your animations are pretty and expensive
Effects stacked plugin after plugin, calculations on every scroll, a phone getting warm. A badly built animation is paid for in performance, and therefore in lost visitors.
The motion tells no story
Everything fades in, in the same direction, at the same speed. When everything moves alike, nothing draws the eye — and animation becomes decoration people endure.
It stutters on mobile
What runs at sixty frames per second on your screen crawls on a mid-range phone. An animated site is judged on the slowest device, not on yours.
What you get
- Scroll storytelling: the page unfolds as you go down (GSAP ScrollTrigger)
- Page transitions: navigation becomes continuous, with no white reload
- Text animation, letter by letter or word by word (SplitText)
- Micro-interactions: hovers, cursor, buttons, visual feedback
- Light WebGL: animated backgrounds, image distortion, 3D objects, cleanly degradable
- Performance budget held: 60 frames per second, and prefers-reduced-motion respected
How it works
We define the intent
What is the motion meant to make clear? Without an answer to that, you are producing expensive decoration.
We prototype early
Animation cannot be judged from a still image. I build a playable version in the browser very quickly, so decisions are made on the real thing.
We build on a timeline
GSAP rather than stacked CSS effects: sequences stay controlled, adjustable to the hundredth, and switchable off as a block.
We measure on real hardware
Frame rates checked on mid-range mobiles, and clean removal of whatever does not hold. A site that stutters cancels every benefit the animation brought.
Frequently asked questions
Will it slow my site down?
Done badly, very much so. Done well, the difference is invisible: animations rely on the properties browsers can accelerate, and the performance budget is part of the brief, not of good intentions.
What about mobile?
Everything is tested on real devices, not just emulated. Anything that will not hold sixty frames per second is simplified or dropped on small screens — a degraded effect always beats a stuttering one.
Some people are sensitive to motion. Do you account for that?
Always. Operating systems expose a « reduce motion » preference; when it is on, the site honours it and removes movement without losing any content. That is an accessibility requirement, not an option.
A project worth moving?
Show me your designs or your current site. I will tell you what is feasible, what it costs in performance, and what is not worth doing.