Tool

Reaction time test

Wait for the box to turn green, then react as fast as you can: click it, press any key, or press any button on a controller. Each try shows your time in milliseconds, and the table keeps an average for each device, so five tries with a mouse and five with a controller show how much delay the controller adds.

Take the test

  1. Click the box, press a key or press a controller button to start. A controller needs one press first so the browser shows it to the page.
  2. Wait while the box is red. Pressing early shows Too soon and does not count.
  3. React the moment it turns green.
  4. Repeat at least five times with each device you want to compare.

Read your result

  • Your time. From the frame that showed green to your press, in milliseconds.
  • Average and best. Kept for each device separately. The average says more than one lucky try.
  • The comparison. After five tries on two devices, the page shows how much slower the slower one is.

Most people react in about 200 to 300 ms, which is my rule of thumb rather than a standard. The comparison between devices is the useful number, because your own reaction is the same on each.

Use it to measure controller lag

Take five tries with a mouse or a key, then five with the controller. Then run the controller again on a cable and over Bluetooth. The differences between those averages are mostly the device and its connection, since you and the screen stay the same. On a Mac, controller input lag on a Mac covers what to do when the gap is large.

If a press does not count

Climb this ladder, smallest step first:

  1. Click the page first. Keys only reach the page while it is the front window.
  2. Press a controller button before you start. A browser shows a controller to a page only after a press.
  3. Wait for green. A press while the box is red is too soon and does not count.

What every result includes

Each time includes the screen's own delay, since a 60 Hz screen draws a new picture only every 16.7 ms, and the browser's, on top of your reaction and the device's. That is the same for every device on one computer, which is why comparing devices works. It is not a medical or a clinical test.

Questions

What is a good reaction time?

Most people react to something they see in about 200 to 300 milliseconds, and practiced players often land near the low end. That range is a rule of thumb, and every result here includes the screen's and the device's own delay.

Can I test my reaction time with a controller?

Yes. Connect it, press a button once so the browser shows it to the page, then use any button to react. The page times the controller's own report, so the result is comparable with a mouse or a key.

How do I measure controller input lag with this?

Take five tries with a mouse or a key and five with the controller. Your reaction is the same on both, so the difference between the two averages is mostly the controller and its connection. Repeat with a cable and with Bluetooth to compare them.

Related

Download InputConfig on the Mac App StoreFree. macOS 14 or later. No account, nothing leaves your Mac. Open source on GitHub.