ReflexTimer

Reaction Time Guides

By oogwaaay (ReflexTimer operator) · Last updated: November 7, 2026

Every guide below is written to answer a specific question about reaction time, not to fill a keyword. Start with the basics if you are new, or jump to the section that matches your question.

Start with the basics

If you just want context for your score, these five pages cover the foundations. They are the right place to begin before reading the deeper guides.

Measurement, devices, and accuracy

These guides explain what a millisecond score actually contains and why two devices can disagree without either being "wrong".

State, sleep, caffeine, and training

Your score is not fixed. These guides separate what changes your state from what changes your skill.

Comparing tools and tasks

Different tests measure different skills. These comparisons explain why the numbers are not interchangeable and when to use which test.

A two-minute path through the guides

If you have one question, start there rather than reading everything. Want to know whether your score is normal? Read Average Reaction Time and Reaction Time by Age. Want to know why your phone and laptop disagree? Read Mouse vs Touchscreen and the accuracy guide. Want to know whether a bad night's sleep or a coffee changed your result? Read the sleep and caffeine guides. Want to know whether practice will carry over? Read the training-transfer guide.

If you are setting up a personal benchmark, read the accuracy guide and the latency calibration guide first. They will save you from chasing noise: once you know what your measurement includes, you can decide which variables are worth controlling and which ones are not.

What actually moves a score

The variables fall into three groups, and it helps to keep them separate. Measurement conditions include the display, input device, browser, and test rules; changing them changes the number without changing you. State includes sleep, caffeine, fatigue, attention, and time of day; these are real changes in your performance but they are temporary. Skill includes task-specific practice and technique; this is the part that training can move, and it tends to be narrower than people hope.

Most confusing score changes come from mixing these groups. A new mouse is a measurement change; a bad night is a state change; a week of practice is a skill change. If you change all three at once, you cannot attribute the result to any of them. The guides in this hub are organised around that distinction because it is the one that makes personal tracking useful.

How to read a claim in these guides

When a guide cites a study, the useful questions are: what task did the study use, who were the participants, how large was the effect, and does the task resemble the one you care about? A finding from a controlled laboratory task may not transfer to a browser test; an average effect across a group may not describe your individual response. The guides try to state those limits rather than hiding them behind a single number.

Effect sizes are averages, not guarantees. A "small average effect" can still be meaningful for an individual, and a "large average effect" in a narrow task can be irrelevant to a different task. Read the method before the headline.

Classroom and teaching

Accessibility and use

Test yourself

The guides are most useful alongside a measurement. Each test below measures a different component; use the one that matches your question rather than treating them as interchangeable.

How these guides are written

Guides are written and reviewed by the ReflexTimer editorial team. Numerical claims are linked to a source where one exists; where the evidence is mixed, the guide says so. The pages are updated when the underlying evidence or the test changes, and the date at the top of each guide shows the latest revision.

We do not publish invented statistics about our own audience. When a page references site-wide results, it is showing a real server-side count, and when there is not enough data, the page says that instead of presenting an empty sample as a distribution. This is the same standard described in our editorial policy.

What this site does not publish

We do not publish miracle claims, fabricated percentiles, or "reaction time" advice that outruns the evidence. If a product promises a dramatic general improvement from a single trick, that is a marketing claim, not a finding from the research literature. The guides above are deliberately more cautious than that.

Suggest a guide

If you have a question the existing guides do not answer, email hello@reflextimer.com with the topic. We add guides when there is a real question to answer and enough evidence to answer it responsibly.