Notes

100 milliseconds

9 November 2026 2 min read

A blind test. One of two buttons answers late. Find out how small a delay you can still feel, then see why that number matters.

  • Performance
  • Perception
  • Interaction

Everyone quotes "100 milliseconds" as the line where something feels instant. Few people have felt where that line sits for them. This is a quick way to find out.

Round 1 of 10

Tap A and tap B, a few times each. One of them answers late. Which one?

Which one was slower?
Live demo. Everything runs in your browser. Now try to break it.
DelayThreshold.svelte, 153 lines

Tap A and tap B a few times each. One of them lights up late. Pick the slower one. If you are right, the next round is harder. If you are wrong, it gets easier. After ten rounds the delay hovers around the smallest lag you can still tell apart.

What the number means

Below roughly 100 ms an answer feels like a direct result of your action: you pressed, it moved. Above it you start to notice a gap, and the interface feels like something you are waiting on. Around a second you lose the thread of what you were doing. These are old rules of thumb and they hold up because they come from how perception and attention work, not from fashion.

Direct manipulation is stricter than clicking. Dragging, scrolling and typing show lag more clearly, because your eye compares the thing under your finger with the thing on screen.

Why it belongs in a design review

"It loads in 300 ms" sounds fast. It depends on what the 300 ms are spent on. A tap that answers late feels broken even if the result is correct. A page that takes longer but responds to the tap at once feels alive.

  • Acknowledge first. A pressed state, a ripple, a changed label, within one frame. Do the work after.
  • Keep the main thread free during input. A long task during a tap is a lag you can feel.
  • Measure input delay, not only load time. Interaction to Next Paint (INP) exists for this reason.

A small way to check it yourself

button.addEventListener('pointerdown', (e) => {
  const t = performance.now();
  requestAnimationFrame(() => console.log('first frame after the tap:', Math.round(performance.now() - t), 'ms'));
});

On a good device this prints about one frame, around 16 ms. If it prints more, something is blocking the thread right when a person is touching the screen.

About the test

Ten rounds are a sketch. The result moves from one try to the next, and your device already adds some lag: the display, the touch panel, the browser. That is a feature here. The point is not a perfect number but to feel what the number is about.

Related

How bright was it?

Five lamps and an optional line. Feedback, a bug, an idea, anything. I read every one and sum them up once a month.

Pick a lamp

Stored without name, address or cookie, and deleted after a year. Details in the privacy notice.