Look beyond one fast response: can you repeat that speed under the same conditions?
Loading dimension detail data…
UNDERSTAND YOUR RESULTS
A visual reaction task observes the response from a visual cue to an input event. Scores are usually recorded in milliseconds; lower means faster on that task. Human performance, equipment and browser conditions can all matter, so the result is not a direct measure of brain-only reaction time.
A ClickReflex standard reaction session contains seven valid responses. The fastest and slowest are removed, and the middle five are averaged. Interpret the session score using that protocol, separately from the single fastest click.
Repeated sessions help show whether results are close under matching conditions. A difference alone does not establish system stutter, fatigue or a training effect.
Valorant, CS2 and F1 tasks change the visual setting or task demands. They offer supplementary experiences, but should not replace a standard reaction best or guarantee real-game performance.
| Observation | What it describes | What it does not establish |
|---|---|---|
| Standard score (ms) | This session under a defined protocol | Brain-only reaction time or full click-to-photon latency |
| Same-condition personal best | A stronger saved observation | Stable ability or a verified global rank |
| Changes across sessions | Repeat performance under matching conditions | A proven cause such as training, hardware or fatigue |
First check that the protocol, input method and comparison group match. Different tasks and devices should not be ranked together without evidence. Without a validated matching sample, use your history to observe changes and treat reference scores as supplementary.
The standard test averages the middle five of seven valid responses to reduce the influence of a single extreme value. Your fastest click is still one observation, not the whole session.
Yes. Display presentation, input devices and browser processing can affect test conditions. Refresh and polling rates describe only part of the chain; they cannot precisely reveal brain-only reaction time by subtraction.
Keep the task, device, connection and input method consistent, and avoid anticipating the signal. Consider several sessions together; one faster result after practice does not prove a lasting training benefit.
Start with recorded scores. Historical coverage and comparable results may count different records.
Milliseconds, levels and item counts come from test records saved in this browser. Latest and personal-best scores are different observations, not fixed abilities.
Current reference scales use provisional project rules, not validated population norms. Estimated Top does not describe an observed population proportion; combining reference scores does not establish an overall population percentile.
The ordinary Profile overview and dimension details use the same production record-eligibility rules. Historical records remain visible, but records without comparable conditions do not contribute to reference scores. Saved history is not automatically a valid same-condition result. Distinguish all linked tests from the core tests contributing to a dimension.
Prefer the same task, mode, version and input method. Similar dates or scores alone cannot establish comparability when these conditions were not saved.
These notes do not read personal scores. Public HTML and page structured data contain no personal records. Sharing the page URL does not transfer your locally saved results.
Keep the existing mapping from standard reaction scores to a provisional task curve. Game scenarios remain separate; estimated Top does not describe an observed population proportion.
Notes reviewed: 2026-10-21 · public-method-v1 (notes version, not a calculation model version)