Why reaction scores need setup notes

A reaction score looks portable because it is expressed in milliseconds. A result from a laptop and one from a phone appear to share the same unit, so it is tempting to subtract them and call the difference an improvement. For a browser test, that comparison leaves out part of the experiment: the screen, input device, selected cue, and conditions under which each round was completed.
This is a practical note from the Reaction Speed Test project. Our browser tool offers five- and ten-attempt rounds, with visual, sound-assisted, and sound-only settings. Those controls make it convenient to try different conditions. They also make it easy to change several conditions at once and lose track of what a comparison actually represents.

Write down the setup before starting

Keep a short label beside each round: device, browser, mouse or touch, cue mode, and number of attempts. If you know the display refresh setting or mouse polling configuration, include it. If you do not, leave it unknown rather than guessing. A label such as “laptop, wired mouse, visual cue, ten attempts” is already more informative than an isolated best score.
The display has to present the cue, and the input device has to register the response. Changing a screen or switching from a mouse to touch changes that route. A lower reading after a hardware change can be an interesting observation, but it does not isolate a change in the person taking the test.

Change one thing you can describe

Start with a complete round, then repeat it on the same setup. For an exploratory comparison, change one option next: perhaps switch from the visual cue to sound-only while keeping the device and round length fixed. The linked page lets you measure visual and sound reaction time without changing the test interface. Keep the modes separate in your notes; they are different stimulus conditions, not interchangeable scores.
Do not discard a slower attempt merely because it spoils an attractive average. If a notification interrupted the round, write that down. If you pressed before the cue, use the test's restart behavior instead of treating anticipation as a fast response. The aim is a comparison you can explain later, including its imperfections.

Keep the interpretation narrower than the result

A useful conclusion might be “my second visual round was lower on the same laptop.” A stronger claim about permanent improvement would need more comparable observations. Equally, a phone result and a desktop result do not establish which person is faster when the setups differ.
The project keeps recent round summaries on the current device and provides a CSV export on its homepage. Saving the round values alongside your setup notes makes later review easier. Treat the file as a record of this particular browser task. Its value comes from knowing how it was collected, rather than turning one number into a verdict about overall ability.