Reaction results

How to Read Your Reaction Time Result

A browser test records one specific task: the delay between an on-screen signal and your response event. The report is useful when you understand what each number says—and what it cannot say.

Start with the median

FPSReaction uses the median of five valid rounds as its headline result. Sort the five times from lowest to highest and take the middle one. Because the median does not move as strongly when one round is unusually slow or fast, it is a more stable session summary than treating one click as your ability.

It still describes only that short session. Repeat the complete test before drawing a conclusion about a trend.

Use every metric for a different question

MetricWhat it helps you inspect
MedianThe central completed round and main session score.
AverageThe arithmetic mean, which reflects every fast and slow round.
Best roundYour lowest recorded time, not your typical result.
ConsistencyHow tightly the five rounds group, using standard deviation.
False startsHow often you responded before the signal instead of reacting to it.

Reference bands are labels, not population norms

In this test, under 200 ms is labeled Excellent, 200–300 ms Good, 301–400 ms Average, and over 400 ms Slow. These labels are internal FPSReaction browser-test references. They are not clinical cutoffs and are not derived from a FPSReaction population dataset.

Why complete sessions vary

Your visual attention and readiness can change between rounds. Display refresh rate and scan-out affect when the red state becomes visible. A mouse, touchscreen, or keyboard has its own reporting path. The operating system and browser must deliver the input event, and system load can delay scheduled work.

Fatigue, interruption, anticipation, and a false start can change behavior even when the hardware stays the same. A small difference between two sessions is therefore not automatically a meaningful improvement or decline.

A repeatable same device comparison

  1. Use the same device, display mode, browser, input method, and page zoom.
  2. Close avoidable background work and keep the tab visible and focused.
  3. Complete the same number of five-round tests rather than comparing one click with a full session.
  4. Take breaks between groups so fatigue does not become the main variable.
  5. Compare medians and consistency across several sessions; keep the conditions in your notes.

This protocol reduces obvious variation. It does not turn a browser tool into laboratory equipment.

What you should not conclude

The result cannot diagnose a neurological, visual, attention, or medical condition. FPSReaction is not a medical or diagnostic test, an occupational fitness assessment, or a certification for esports. Do not compare tiny cross-device differences as though the devices had identical end-to-end latency.