Reaction Time Test
Click the moment the screen turns green
Five rounds, averaged. Clicking while it is still red counts as a false start and voids that round.
Reaction Time Test
Click the moment the screen turns green
Number Memory Test
How many digits can you hold at a glance
Chimp Test
The numbers hide — can you still find them
Typing Speed Test
Sixty seconds — how much can you type
Visual Memory Test
The tiles flash once — did you catch where
Aim Trainer Test
Thirty targets — how long does each one take
Color Vision Test
Find the one square that does not match
Stroop Test
The word says red, the ink says blue
Verbal Memory Test
Have you seen this word before
Sequence Memory Test
Repeat the order the tiles lit up
Click Speed Test
Fifteen seconds — how many clicks
Time Perception Test
No clock — stop when you think time is up
Hand-Eye Coordination Test
Land both balls inside the ring
Mental Math Test
Sixty seconds of arithmetic
Schulte Table Test
One to twenty-five, in order
Dynamic Visual Acuity Test
Count the balls bouncing on screen
What is the reaction time test?
The reaction time test measures how long it takes you to click the instant the screen changes from red to green. Your score is the average of five rounds, reported in milliseconds. Its value is that it turns a vague sense of "am I fast?" into a number you can watch, compare against your own history, or use to check how much lag a device adds.
It is not only for gamers. Driving, catching a ball, keyboard work, buying tickets online, even turning your head when you hear something — all of these involve sensing a signal, deciding, and acting. This test isolates the visual-signal-to-click segment, which makes it a reasonable baseline. Keep in mind that it measures performance inside a browser, and it is not a medical assessment or a full measure of real-world reaction ability.
What are the rules?
Each round begins in a waiting state. The screen turns green after a random delay, and you click as soon as it does. After five rounds the average is reported. Clicking while the screen is still red counts as a false start, and that round is voided. The design exists to stop you from predicting the change or spamming clicks, so the number reflects genuine signal detection.
Do not fix your gaze on one spot and rehearse a rhythm, and do not lift your finger in anticipation of green. The wait length is randomised to defeat silent counting. When the five rounds end you will see the average, the fastest and slowest single rounds, and your personal best, plus a rating. For a more dependable figure, complete one set of five, then repeat the set later under similar conditions.
What is a normal reaction time?
Most people fall between 200 and 300 ms for a visual reaction. Below 200 ms is quick, and near 150 ms is rare. Above 300 ms is not necessarily abnormal — fatigue, distraction, poor sleep, or a high-latency display and input device all push the number up. Age, attention, screen brightness, how the mouse feels, browser performance and your current state each shift the result for the same person.
So do not draw conclusions from a single run. Test three sets of five under similar conditions and look at whether the average is stable before comparing against your history. If you are using this to assess FPS performance, remember that in-game reaction also involves reading the scene, anticipating enemy positions, sound cues, tactical decisions, aiming and network latency. This test covers only a slice of that.
Does practice improve reaction speed?
Regular use helps you get used to the rhythm and reduces variance caused by anticipation or misclicks, so scores become more stable. Most of that gain is "getting better at this test" rather than a general improvement in real-world reaction. What actually moves reaction speed is sleep quality, exercise habits, attention training, hardware performance and motor skill.
If you use it as a daily drill, keep the volume low instead of grinding dozens of rounds. Testing while fatigued tends to produce worse scores and can bake in sloppy habits. Three to five rounds per session, with the average and your state noted, compared across weeks, is far more informative. Gamers can treat it as a warm-up and a baseline check, but it does not replace in-game practice, aim training or reviewing actual matches.
How does it relate to a reflex test?
A reaction time test times the whole chain from seeing a signal to the finger completing a click, including perception, decision and motor execution. A reflex test looks at the neural pathway itself, such as the knee-jerk response, which bypasses deliberate judgement. Both involve responding to a stimulus, but they measure different levels of the system.
So a fast score here does not mean your reflex arc is shorter, and you should not use this test to diagnose anything neurological. Treat the reaction time test as a simplified behavioral measurement and the reflex test as a more physiological concept. For general use, the result here is best for self-comparison and curiosity; if something looks clearly abnormal or persists, consult a doctor rather than an online test.
Can it measure FPS gaming reaction speed?
It gives a useful baseline but does not fully represent FPS reaction speed. In-game performance also depends on reading the scene, judging where enemies appear, locating sounds, making tactical decisions, mouse aim, keyboard control and network latency. This test covers only "see a color change, then click", so it is best used to observe your visual reaction baseline or as supporting evidence alongside real gameplay.
If you want to use the result for training, treat it as a warm-up and a state log rather than a single metric. Test periodically on the same hardware, refresh rate and connection, and compare how you do when rested versus fatigued. Genuine improvement comes from aim practice, map knowledge, crosshair placement habits and reviewing your matches. The value of a tool like this is a comparable baseline, not a substitute for full practice.
How should you take the test properly?
Use the same device, the same mouse or the same touchscreen for every run. Close background programs that compete for resources, keep screen brightness constant, and start while relaxed and focused. Do not spend the waiting period trying to predict the change; let your finger rest and click only after green appears. If you run several sets, take a short break between them so fatigue does not make each one slower than the last.
For results with more reference value, fix the conditions: same time of day, same browser, same connection, same peripheral. Complete three sets of five and record the averages rather than the single best round. Do not compare directly against history after switching devices, because display lag, refresh rate and input hardware all shift the number. Repeatable conditions matter more than one fast run.
How scientifically sound is it?
The test uses the browser performance.now clock and waits until the green frame has actually been painted before starting the timer, which removes the error you get from timing before green reaches your eyes. That is closer to the moment you actually see the signal than a plain setTimeout. It is still affected by device performance, browser scheduling, refresh rate, input latency and environmental distractions.
In practical terms it is well suited to self-comparison, state tracking and casual reference, and unsuitable as a medical diagnosis, a hiring criterion or a competitive rating. Absolute values are not comparable across devices, and variation within one person is normal. Use it as a convenient online baseline and combine it with repeated runs and real-world performance rather than trusting a single number.