spatialmeasured

Paco Coursey

One move: the page's text enters on a plain 0.6s ease, staggered in 0.12s steps from the heading down. Links underline in 0.24s. Then nothing moves.

Tiers

Each curve was read from the browser while visiting paco.me. The demo is our own element running the same timing.

statement

ease

Scrub through the curve

The site animates a keyframe animation (enter); the demo shows the same timing as movement.

utility

ease

Scrub through the curve

The site animates text-decoration-color; the demo shows the same timing as movement.

Reduced motion: Honored
Movement (transform, position, size): 8 events in the normal run, 0 with reduced motion on (0%). All timed CSS and WAAPI motion: 8, then 0 (0%). 1 prefers-reduced-motion query in stylesheets; scripts asked matchMedia about it 0 times.
transition: all: Not seen
0 elements computed transition-property: all at the end of the visit. 0 declarations in the CSS the page loaded.
Motion in JavaScript: None seen
No motion library fingerprints in the scripts. Motion run on requestAnimationFrame isn't readable from styles, so it isn't in the tiers.
Canvas: No viewport-sized WebGL canvas
Nothing here was hidden in a canvas.
Posture: spatial
At rest, 0 transitions move things (transform, opacity) and 13 change surfaces (colour, shadow, background, filter). The glossary's quick test reads that as material. The entry says otherwise because the tell counts what sits at rest, not what moved during the visit.
Coverage: One load, 3 elements hovered
Scrolled to the bottom with the mouse wheel, hovered and left a spread sample of links and buttons. Menus, clicks, forms and other pages weren't visited.

The entrance animates opacity and transform together, with delays of 0s, 0.12s, 0.24s, 0.36s, 0.6s and 0.72s down the page.
With reduced motion on, the entrance doesn't run at all: 8 movement events became 0.
The statement is the keyword ease. Not an aggressive ease-out, and not long.