Interactive Feedback ms

Interactive Feedback Time

Interactive feedback time measures how long it takes for a visible response to follow a user action. Most teams still lean on Jakob Nielsen’s old thresholds. A response under < 0.1 s reads as instant. Stay under < 1 s and the person never loses their train of thought. Push past that and you have until roughly < 10 s to keep them engaged before you really need to show what is going on.

Once you cross ~1000 ms, put up a spinner, a skeleton, or a progress bar. WCAG 2.1 SC 2.2 deals with timing accessibility, which means letting people adjust or turn off time limits. With screen readers, fire updates through aria-live="polite" so the change gets read out after whatever is currently being spoken. Material Design pins its ripple at 100 ms, while React 18’s useTransition lets the UI stay responsive as heavier updates render in the background.

Applications

It helps when you are tuning button states, deciding how a form should react on submit, setting debounce delays for search-as-you-type, working out optimistic UI updates, timing the animation on a micro-interaction, or fixing SLO targets for how fast the client side feels (FID, INP).

FAQ

What is the “instant” threshold? Around 100 ms. Below it, cause and effect feel like the same moment. Above it, people register a delay, even if they could not tell you why.

When should I show a loading indicator? Any time you expect > 1 s. In the 0.1–1 s range a quiet state change does the job, like a color shift or a ripple. Under 0.1 s you can skip the extra feedback entirely.

How does this relate to Core Web Vitals? INP (Interaction to Next Paint) wants you under < 200 ms to earn a “Good” rating. Get anywhere near 1 s and both your Google ranking and your retention take a hit.