The short answer
Give each animation a job, use the lightest tool that can do it, and write down what it does on a phone and with reduced motion turned on. Animate transform and opacity where you can, never hide the main content while a page loads, and test with real numbers on a real phone.
Our post on keeping Webflow interactions fast explains the performance rules, and why they matter. This chapter is how to decide and document motion during a build, so it stays under control as the site grows.
Spend motion where it helps
A site with motion everywhere has no focus, and it costs more to test. Decide where it goes before you build it.
| Good reasons | Weak reasons |
|---|---|
| It explains how something works | The design felt a bit plain |
| It shows a change of state: open, loading, sent | Every section fades in because the first one did |
| It draws the eye to one product moment | A competitor has it |
| It carries the brand, on a site where motion is the work | A library was already loaded |
On a content-heavy site, keep custom animation to the moments that help, such as the hero, the proof cards and the product visuals, and leave the rest as plain CSS. Bailey is the other end of the scale. A creative studio sells motion, so the works page has page transitions, a custom cursor and smooth scrolling. Both are right for what the site is for.
The tool ladder
Start at the top. Move down only when the step above cannot do the job.
| Step | Tool | Good for | Cost |
|---|---|---|---|
| 1 | CSS transitions | Hover, focus, simple state changes | Lowest. No script of your own. |
| 2 | Webflow interactions | Reveals, tabs, menus, scroll effects editors can see in the Designer | Low to medium. Stays editable without code. |
| 3 | Custom GSAP in your own script | Sequences and timing that the visual tools cannot express | Medium. Someone has to maintain the code. |
| 4 | Heavier plugins, Lottie, video or 3D | One moment that is the point of the page | High. Needs a size limit and a fallback. |
Webflow also offers Interactions with GSAP in the Designer. Its update note lists support for breakpoints, prefers reduced motion settings, and page scoping, which controls the pages an interaction loads on. For most new work, check the current docs and compare this with Classic interactions before choosing.
Decision rule If the team will need to change it without a developer, keep it in the Designer. On CUBE, copy, logos and steps in the home page interactions change in the Designer without touching code. That was a build requirement, not a nice extra.
A one-line motion spec
For each interaction, write one row. It takes a minute, and it means the designer, developer and tester are all checking the same thing.
| Field | Example: home page tabs |
|---|---|
| Job | Show four product areas without a long page |
| Trigger | Auto-advance, with a timer bar. Stops on click. |
| What moves | Panel opacity and a small transform, timer bar scale |
| Tool | Webflow interaction, or a small script if timing needs it |
| On phones | Same logic, swipe enabled, no hover |
| Reduced motion | No auto-advance. Tabs change on click, with no slide. |
| JS off or failed | First panel visible, with its text readable |
| Done when | Keyboard works, no layout shift, smooth on a mid-range phone |
The example is made up, though auto-playing tabs with timer bars are a real thing on the CUBE home page. Keep all rows in one place, such as the handover document in chapter 5.
Standards for every interaction
| Standard | Why | Source |
|---|---|---|
| Prefer transform and opacity | They are the compositor-only properties, so they skip layout and paint | web.dev |
Use will-change sparingly | Each layer uses memory, which hurts low-memory devices | web.dev |
| Keep the main heading and hero image visible at load | An element hidden until scripts finish adds render delay | web.dev |
| Never lazy-load the LCP image | It starts the request later than needed | web.dev |
| Reserve space for anything that animates in | Late content shifts the layout | Our rule |
| Load heavy scripts only on pages that use them | Other pages should not pay for one effect | Our rule |
| Offer a non-gesture route | On the CUBE calculator, seat counts can be typed as well as dragged | Our rule |
Reduced motion is part of the build
The prefers-reduced-motion setting tells a site that a visitor wants less non-essential motion, for example because of a vestibular disorder. Decide per type, up front.
| Type of motion | With reduced motion on |
|---|---|
| Fade or slide on scroll | Show content in place, with no movement |
| Auto-playing tabs or sliders | No auto-advance. Keep user controls. |
| Looping background video | Show a still poster, with a control to play |
| Page transitions | A plain page change |
| Smooth scrolling libraries | Turn off, and use native scrolling |
| Hover colour changes | Keep. These are fine. |
In Interactions with GSAP, use the reduced motion settings. In custom scripts, check the media query in code before you start any timeline. Then test it for real, by turning the setting on in your device or browser.
Heavy media and custom code
On Bailey, every page is full of large video, so the pages needed a plan for it. Video and images are served from Bunny CDN, video plays on hover, and animation runs on GSAP with ScrollTrigger and SplitText, plus Lenis for scrolling. Your site may not need any of that, but the same questions apply.
- Why is it here? Name the job, using the one-line spec.
- What is the fallback? Every video has a poster. Every 3D scene has a still.
- When does it load? Off-screen media waits. The one hero element does not.
- Who hosts it? Large video does not belong in a plain background upload if a proper host would serve it better.
- Who maintains the script? Keep custom code in one known place, with comments and a named owner.
- What is the licence? Check the terms for any library or plugin, and check again when you add one.
If animation still matters after launch, a short note in the handover saying which script drives which effect will save your next developer a day.
Test against numbers
Google's Core Web Vitals have published targets, and web.dev says to measure them at the 75th percentile of page loads, split by mobile and desktop.
| Metric | Good is | How motion hurts it |
|---|---|---|
| LCP | 2.5 seconds or less | A hero hidden by an interaction |
| INP | 200 milliseconds or less | Heavy scripts during taps and scrolling |
| CLS | 0.1 or less | Elements that move others as they appear |
- Run Lighthouse on mobile on each template. Our build target is 95 or above. That is a target, not a promise.
- Run it with and without the animated sections, if you are unsure what the effect costs.
- Scroll the page on a real mid-range phone, with no cache.
- Turn on reduced motion, and check again.
- Use the keyboard to reach each control, and see it in focus.
- Publish, and test on the published site. Field data takes time to arrive, so keep checking after launch.
Decision rule If an effect is the reason the page misses its target, it gets simpler, or it goes. Nothing is exempt. The site has to work first. Our Webflow speed guide and Core Web Vitals on Webflow cover what to try.


