Expressive sites rarely get slow from one decision. A smooth-scroll library, a split-text heading, a hero video, a WebGL layer and a tag manager each pass review alone.
A budget makes the pile visible. Ours covers field thresholds, motion per page type, and frame time for ambient animation.
The floor: Core Web Vitals at the 75th percentile
Google publishes the thresholds on web.dev (opens in a new tab) and assesses them at the 75th percentile of real page loads, mobile and desktop separately. A fast run on a studio laptop says little about that.
| Metric | “Good” | How motion usually breaks it |
|---|---|---|
| LCP (Largest Contentful Paint) | 2.5 s or less | The hero waits for a script, a video or a canvas before it paints |
| INP (Interaction to Next Paint) | 200 ms or less | Scroll and animation work holds the main thread when a tap arrives |
| CLS (Cumulative Layout Shift) | 0.1 or less | Animated layout properties; media that loads without reserved space |
We treat these as a floor and aim well below, so the next banner or tracking script has room.
A motion level for every template
Our most useful budget decision has nothing to do with milliseconds. Every template has a motion level, set in one line of layout code:
const MOTION = { legal: 0, sitemap: 0, 'not-found': 0, thanks: 0,
service: 2, solution: 2, industry: 2, campaign: 2, lab: 2,
home: 3, 'case-study': 3 };
// anything not listed, articles included, gets level 1
| Level | Pages | Motion allowed |
|---|---|---|
| 0 Utility | Legal, sitemap, 404, thank-you | State changes only |
| 1 Standard | Company pages, FAQ, articles | Fades and feedback |
| 2 Editorial | Services, solutions, campaigns, Lab | Adds split headings, timelines and hero art |
| 3 Flagship | Home, Work, case studies | Adds scroll narratives and the signature layer |
A motion-led site earns its character on a handful of pages; the rest should get out of the way. A thank-you page that stalls on a script is the worst place to lose someone.
This article is level 1: it fades in and responds to input, nothing more.
Levels also settle review arguments. A proposed effect gets a level first; if that doesn't match its page, it moves or it goes.
Ambient loops get 30 frames per second
At 60 fps a frame lasts about 16.7 ms, and the browser needs part of that for style, layout and paint. A task over 50 ms is a long task, and input landing during one waits.
The canvas art on our service pages redraws at most every 33 ms, and only the first two visible canvases animate:
const loop = (ms) => {
raf = 0;
const visible = items.filter((it) => it.visible);
if (!visible.length || document.hidden || reduce()) return;
raf = requestAnimationFrame(loop);
if (ms - lastFrame < 33) return; // about 30 fps
lastFrame = ms;
visible.slice(0, 2).forEach((it) => draw(it, ms / 1000));
};
That halves the drawing work for a barely visible difference. Input-driven motion is exempt: a drag or hover at 30 fps feels late, so it runs at full rate or not at all.
Animate transform and opacity, and write it down
transform and opacity can animate on the compositor without layout or paint; filter often can too. Animating top, width, margin or box-shadow forces layout or paint every frame.
When layout must change, animate a transform between the old box and the new one (the FLIP technique), and let layout change once.
For scroll effects, cache layout reads, recompute on resize, and drive everything from one requestAnimationFrame loop.
will-change can cost a GPU layer. Add it just before an animation and remove it afterwards.
Keep heavy modules out of the first download
The colophon reports this site's build: 18.6 KB of JavaScript and 15.0 KB of CSS, gzipped, for the whole site. The orb and the canvas art arrive by dynamic import() once the page is idle.
Write a ceiling like that into the brief, so a new library argues for its kilobytes when its effect is proposed.
A budget you can paste into a brief
- LCP, INP and CLS targets below the web.dev thresholds, checked in field data after launch.
- A motion level for every template, with the effects each level allows.
- A frame-rate cap for ambient loops (ours is 30 fps) and a limit on how many run at once.
- Input-driven motion at full frame rate, or none.
- Animated properties:
transformandopacityby default; anything else needs a reason in the pull request. - Scenes and other heavy modules loaded by dynamic
import()after first paint. - A ceiling for JavaScript shipped before first interaction, in compressed kilobytes.
- Reduced-motion and paused behaviour defined for every self-moving component.
Setting and enforcing this is part of our frontend engineering work. Load order is covered in The canvas loads last.


