Perceived latency is a story, not a timer
Research on perceived responsiveness keeps landing on the same numbers: under 100ms the response feels instant. Between 100 and 300ms the user notices the wait but credits the interface with intent. Past 300ms the user starts to doubt whether the click registered at all — and that doubt is the expensive one, because doubt produces re-clicks, and re-clicks produce double-submits, and double-submits produce duplicates, and duplicates produce tickets.
The trick of the 200ms window: the user does not need the *result* in 200ms — they need *evidence* in 200ms. A button that compresses the instant it is pressed buys the slow network call that follows. The click window is filled by confirmation, and confirmation is motion's job.
0–60ms: press feedback (scale, fill). 60–200ms: state change (spinner, optimistic update, 'Saving…'). 200ms+: if the real result is late, the UI must already look busy — a calm spinner beats a frozen button.
Optimistic updates are the professional move
The interface that feels fastest is the one that acts as if the network does not exist and corrects itself if it turns out to be wrong. Toggling a switch flips it instantly and shows 'syncing'; only on failure does it flip back with a reason. That is filling the click window with the product's own confidence.
The rule for optimism: only optimistic-update actions that are reversible or low-cost. A like, a toggle, a reorder — yes. A payment — never. Optimism is a design decision about who apologises when the network disagrees.
What steals the window
- No press state at all: the button sits still for 300ms, then the result arrives — the user cannot tell when the click registered.
- Disabled-looking buttons: grey until the handler runs, making the user wonder whether they may click at all.
- Double-submit traps: a slow submit that lets a second click through; the second click is the click window's revenge.
- Spinner-only feedback on fast actions: a 40ms action that shows a spinner for 300ms feels slower than the same action with no feedback at all.
- Navigation without a hint: clicking a card that takes 400ms to navigate with zero feedback in between.
The motion recipe for the window
button:active { transform: scale(.97); }
/* instant, 60ms, then the state change takes over */
.card[data-pending] .spinner { opacity: 1; }
/* the 200ms window stays honest: pressed -> busy -> done */