FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 4 of 6

Interactions that stay fast

Every animation should earn its place. A ladder for choosing the lightest tool, a one-line spec for each interaction, reduced motion rules, and the numbers to test against.

6 min readUpdated 2026-11-07
All chaptersChapter 4 of 6
  1. 01Brief and Figma handover
  2. 02Client-First, classes and variables
  3. 03Components and CMS model
  4. 04Interactions that stay fast
  5. 05Editor handover
  6. 06Pre-launch checks

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 reasonsWeak reasons
It explains how something worksThe design felt a bit plain
It shows a change of state: open, loading, sentEvery section fades in because the first one did
It draws the eye to one product momentA competitor has it
It carries the brand, on a site where motion is the workA 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.

StepToolGood forCost
1CSS transitionsHover, focus, simple state changesLowest. No script of your own.
2Webflow interactionsReveals, tabs, menus, scroll effects editors can see in the DesignerLow to medium. Stays editable without code.
3Custom GSAP in your own scriptSequences and timing that the visual tools cannot expressMedium. Someone has to maintain the code.
4Heavier plugins, Lottie, video or 3DOne moment that is the point of the pageHigh. 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.

FieldExample: home page tabs
JobShow four product areas without a long page
TriggerAuto-advance, with a timer bar. Stops on click.
What movesPanel opacity and a small transform, timer bar scale
ToolWebflow interaction, or a small script if timing needs it
On phonesSame logic, swipe enabled, no hover
Reduced motionNo auto-advance. Tabs change on click, with no slide.
JS off or failedFirst panel visible, with its text readable
Done whenKeyboard 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

StandardWhySource
Prefer transform and opacityThey are the compositor-only properties, so they skip layout and paintweb.dev
Use will-change sparinglyEach layer uses memory, which hurts low-memory devicesweb.dev
Keep the main heading and hero image visible at loadAn element hidden until scripts finish adds render delayweb.dev
Never lazy-load the LCP imageIt starts the request later than neededweb.dev
Reserve space for anything that animates inLate content shifts the layoutOur rule
Load heavy scripts only on pages that use themOther pages should not pay for one effectOur rule
Offer a non-gesture routeOn the CUBE calculator, seat counts can be typed as well as draggedOur 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 motionWith reduced motion on
Fade or slide on scrollShow content in place, with no movement
Auto-playing tabs or slidersNo auto-advance. Keep user controls.
Looping background videoShow a still poster, with a control to play
Page transitionsA plain page change
Smooth scrolling librariesTurn off, and use native scrolling
Hover colour changesKeep. 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.

MetricGood isHow motion hurts it
LCP2.5 seconds or lessA hero hidden by an interaction
INP200 milliseconds or lessHeavy scripts during taps and scrolling
CLS0.1 or lessElements 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.

Takeaways

What to remember from chapter 4.

  • Each animation needs a job. Write down its trigger, phone behaviour and reduced motion behaviour.
  • Use the lightest tool that can do the job. Keep what editors need to change in the Designer.
  • Prefer transform and opacity. Keep the hero visible at load, and never lazy-load the LCP image.
  • Reduced motion is a build requirement, tested on the device, not a late add-on.
  • Test with numbers on a real phone. An effect that makes a page miss its target gets simpler or goes.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.