Controller Latency Test — measure input lag in ms
A controller latency test measures the time between physical input on your gamepad and the input registering in software. Our browser-based test uses microsecond-precision timing to report minimum, average, and 95th-percentile polling latency in milliseconds. Works with any standard USB or Bluetooth controller — no download required.
How the latency test works
Connect your controller
Plug in your controller via USB or pair it via Bluetooth. Press any button to wake the controller — browsers require this before exposing gamepad input for privacy reasons.
Start the 10-second sample
Click Start. The test begins capturing input state changes from the Gamepad API immediately, using performance.now() for microsecond-precision timing.
Provide continuous input
Move both analog sticks in continuous circles and tap buttons throughout the 10-second window. The more varied input you provide, the more accurate the measurement.
Read your results
The test reports minimum, average, 95th percentile, and maximum latency in milliseconds. The average is the primary metric. The histogram shows the distribution of intervals.
What the numbers mean
Compare your average latency to the thresholds below. These ranges reflect real-world performance from wired controllers, wireless dongles, and Bluetooth gamepads under typical conditions.
| Average Latency | Verdict | What It Means |
|---|---|---|
| < 5ms | Excellent | Tournament-grade response. Equivalent to wired competitive controllers. |
| 5 – 10ms | Good | Typical for wired controllers and high-quality wireless. Imperceptible in normal play. |
| 10 – 20ms | Acceptable | Normal Bluetooth range. Fine for most games. Competitive FPS players may notice. |
| 20 – 40ms | Degraded | Detectable lag. Check for wireless interference, low battery, or distance from receiver. |
| > 40ms | Problematic | Significant lag. Switch to wired, change connection, or check for controller issues. |
Compatible devices
The latency test works with any controller your operating system recognizes as a standard gamepad — wired, Bluetooth, or proprietary wireless. Verified models:
Latency repair guides
Related diagnostics
Latency questions
Controller latency is the total time between a physical button press or stick movement and the input registering in software. It is measured in milliseconds. Lower latency means more responsive gameplay — a critical factor in competitive shooters, fighting games, and rhythm games where individual frames matter.
Our test measures the polling latency between consecutive input state changes as observed by the browser. This captures the time spent in the operating system’s HID driver, the browser’s Gamepad API, and the JavaScript event loop. It does not include the wireless transmission time from controller to receiver, which is typically 1–4 milliseconds for modern wireless protocols.
Under 5 milliseconds is excellent — tournament-grade response equivalent to wired competitive controllers. Five to 10 milliseconds is good and typical for high-quality wireless or wired gamepads. Ten to 20 milliseconds is acceptable for casual play and normal for Bluetooth controllers. Above 20 milliseconds indicates wireless interference, low battery, or driver issues.
The most common causes are Bluetooth interference from Wi-Fi networks on the 2.4GHz band, low battery levels triggering power-saving modes, distance from the wireless receiver, outdated drivers, and CPU contention on the host machine. Switching to a USB-wired connection eliminates most wireless-related latency.
Wired connections consistently produce lower and more stable latency than wireless. Wired controllers typically poll at 1000Hz (1ms) with no transmission overhead. Bluetooth controllers poll at 125Hz (8ms) on average with additional variance from radio scheduling. Proprietary wireless dongles like Xbox’s 2.4GHz adapter approach wired performance.
We use the browser’s high-resolution performance.now() timer, which provides microsecond precision under normal conditions (modern browsers clamp this to 100 microseconds in some security contexts). Sampling for 10 seconds across many input transitions averages out single-frame noise and produces a reliable mean and 95th percentile.
Yes. The test works identically across USB-wired and Bluetooth controllers. For the most reliable Bluetooth measurement, run the test with the controller close to the receiver and confirm no other 2.4GHz devices are actively transmitting. Run multiple times to confirm consistency — Bluetooth latency naturally varies more than wired.
No. High latency is a symptom of communication overhead, not hardware damage. The controller itself is not stressed by higher latency. However, persistently high latency can indicate failing batteries, worn USB cables, or interference issues worth addressing for gameplay quality.
How we measure latency
Built on the Gamepad API specification with microsecond-precision performance.now() timing. Measures polling interval, not end-to-end latency. Methodology published by GPADLAB Engineering.
Run the full Controller Health Score
This test is one of six diagnostics in the composite score. See how your controller stacks up overall.
Run the Benchmark