controller-test.com · Timing

Latency Test

Measure controller input latency and reaction time in milliseconds. Compare wired vs wireless response over multiple runs.

Reaction + input latency

Click Start

Best

Average

Attempts

Valid

Measures the round trip of human reaction plus controller and browser latency. Typical human reaction is 200 to 300 ms; anything above that reveals input lag.

Overview

What the Latency Test does

This test measures the round trip of human reaction plus controller, browser, and display latency. A cue turns green after a random delay and you press any button as fast as you can. The tester logs each attempt so you can see your average, your best, and the exact millisecond delta between wired and wireless.

Steps

How to run the test

Click Start test.
Wait for the panel to turn green. Do not press early or the attempt is voided.
Press any controller button the instant the panel turns green.
Run 5 to 10 attempts and read your average.
Switch transports (wired or Bluetooth) and run the same 5 to 10 attempts to compare.

What this test can and cannot measure

There is no way a browser can precisely time the electrical moment your controller button was pressed. The best any web tester can do is measure the human plus system round trip: cue rendered, retina to brain, brain to thumb, thumb to switch, switch to controller MCU, MCU to host, host to browser, browser to result. That total is what matters for how the game feels to you. To isolate the controller portion, keep everything else constant and only change the transport.

How to run a controlled comparison

Sit in the same seat, use the same monitor at the same refresh, keep the same lighting. Run 10 attempts wired, take a two minute break, then run 10 attempts on Bluetooth. Compare medians rather than averages because your best and worst runs skew both. A 15 to 30 ms difference wired-to-wireless is normal on modern Bluetooth. A 60 ms or larger difference usually means a bad Bluetooth stack or interference from other radios on your desk.

What actually contributes to input lag

Display response is usually the largest contributor. A 60 Hz LCD without game mode can add 30 to 60 ms of buffered lag. Enabling game mode drops that dramatically. Controller polling and transport are next. Wired USB adds 1 to 2 ms. Xbox Wireless adds 4 to 8 ms. Bluetooth adds 8 to 20 ms. Software layers like Steam Input, DS4Windows, or the browser itself add another 5 to 15 ms. Every layer stacks.

How to actually reduce your input lag

Turn on game mode on your monitor or TV. Prefer wired for competitive play. If you must be wireless, use a 2.4 GHz dongle instead of Bluetooth. Close any controller translation software you do not need. Disable browser extensions that hook input like screenshot tools. If you are on a laptop, plug in for power so the CPU is not throttling. Re-run this test after each change to see the delta.

When to blame the display, not the pad

If your times are consistently over 320 ms across multiple controllers, the bottleneck is not your controller. It is your monitor or the render pipeline. Look up your specific monitor model on rtings.com for its measured input lag. A cheap 60 Hz TV in movie mode can add 100 ms all by itself, and no controller upgrade will fix that.

Fix it

Common problems and quick fixes

Reaction times over 350 ms even after warmup

Display lag is likely the culprit. Enable game mode on your monitor and disable any post-processing.

Bluetooth is 50 ms slower than wired

Move other 2.4 GHz devices away from the pad. Wi-Fi routers, wireless mice, and USB 3.0 ports all interfere.

Times vary wildly attempt to attempt

Background processes are contending for CPU. Close browsers tabs and disable recording software before testing.

FAQ

Common questions

What is a good reaction time?+

220 to 280 ms is typical for adult gamers. Under 200 ms is exceptional. Over 320 ms suggests either display lag, controller lag, or fatigue.

Does this measure controller latency alone?+

No. It measures human plus system latency. To isolate controller lag, run wired and Bluetooth back to back on the same setup and take the delta.

Why does my time get worse over 10 attempts?+

Fatigue and anticipation. The first 3 attempts are the least contaminated. Take a break between runs.

Run 10 attempts wired, then 10 on Bluetooth, and see the real millisecond gap on your exact setup. Then pick the transport that feels best.

Every diagnostic here runs locally in your browser. Nothing is uploaded.

Browse all tools

More tools

Related diagnostics

Pair this test with any of the below for a full controller health check.

Timing