Gamepad Latency Test
The Gamepad Latency Test measures how fast your controller reacts when you move a stick or push a button. The time lag between your action and what appears on screen is known as latency. Games may feel sluggish or unresponsive if the delay is excessive. This test allows you to see your controller’s response time in real time, which can help you determine whether it’s operating smoothly or if there is a lag issue. No downloads are required; simply connect your gamepad and begin testing.
Test Controls
Live Readouts & Stats
Complete Guide to Gamepad Latency Test – Understanding, Measuring & Reducing Polling Rate
This Gamepad Latency Test provides an estimate only. You can also try our Gamepad Tester to check overall controller responsiveness. It runs inside your web browser and uses the Gamepad API along with the browser-supplied gamepad. Timestamp (when available) and sampling logic to estimate how quickly controller input reaches the page. It does not measure total input-to-screen latency. Measuring true end-to-end latency requires external hardware like high-speed cameras or photodiodes. Results can vary based on:
- Controller model
- Operating system
- Browser
- CPU load
- USB vs Bluetooth connection
- Power-saving settings
Use these results to compare setups (for example: wired vs wireless, different browsers, or different controllers), not as an absolute hardware benchmark. Input latency is critical for competitive gaming and any experience where timing and precision matter. This guide explains what latency is, where it comes from, how this tool measures it, how to test properly, and how to reduce delays. Each section is designed to be easy to read and practical to use.
How to use Latency Tester
Use this Gamepad Latency Test to measure input delay. Connect your controller via USB or Bluetooth, press any button to activate it, then repeatedly press the selected test button. The tool estimates input latency (in milliseconds) using browser-reported timestamps and polling logic, showing per-press results along with minimum, average, and maximum latency plus a live visual bar.
What Is Input Latency?
Input latency (also called input lag) is the time delay between pressing a button or moving a stick and the moment the system reacts. It is measured in milliseconds (ms). For game controllers, this delay includes:
- The controller is detecting the input.
- Sending data via USB or Bluetooth.
- OS and browser processing.
- The application updating behavior or visuals.
Why Input Latency Matters?
- Competitive gaming: Faster response improves accuracy and reaction time
- Rhythm games: Timing must be precise for correct scoring
- VR & motion-based apps: High latency breaks immersion and can cause discomfort
Where Latency Comes From?
Controller-Side
- Sampling Rate: How often the controller reads the button and stick states.
- Wireless Radios: Bluetooth adds encoding and transmission delays.
- Power Saving: Wireless controllers may slow updates to save battery.
Transport & Operating System
- USB polling Interval: Faster polling means lower latency.
- Bluetooth Stack: The OS may buffer or batch Bluetooth events.
- Drivers: Input filtering or drivers can add small delays.
Browser & Application
- Gamepad API Polling: Browsers read controller data at set intervals
- Event Loop Scheduling: JavaScript runs on the main thread; heavy tasks can delay input processing
- Frame Rendering: Visual updates depend on requestAnimationFrame and screen refresh rate (e.g. 60Hz ≈ 16.67ms per frame)
How does this Tool Measures Latency?
When supported, gamepad.timestamp represents the moment the browser detected a controller state change. The tool calculates:
performance.now() − gamepad.timestamp
This estimates the delay between browser input detection and page processing. This method is widely used to estimate controller-to-browser latency.
Polling Rate & Jitter
The Gamepad API works by polling. This tool also tracks:
- Poll interval: How often input is checked
- Jitter: Variations in timing between polls
High jitter increases measurement noise, so the poll interval is shown to help interpret results.
Limitations
- If gamepad.timestamp is missing, the tool uses a fallback detection method, which is less accurate
- Display latency (screen response time) cannot be measured
- The earliest internal hardware sensing inside the controller is not visible
Step-by-Step Testing Procedure
Preparation
- Use a wired USB connection for baseline testing.
- Close heavy background apps.
- Set sampleInterval to 8–16ms (16ms works well for 60Hz systems).
Running the Test
- Click Detect Controller
- Confirm your controller name appears
- Choose a test button (A / Cross is common)
- Click Start Test
- Press the button slowly and consistently (1–2 presses per second)
- Collect 30–100 samples
- Click Stop Test
- Review Min / Avg / Max latency
Interpreting Results
- Below 16ms: Excellent, usually wired USB with high polling
- 16 – 40ms: Normal for most systems
- 40 – 100ms+: Bluetooth delays, driver buffering, or CPU load issues
Platform-Specific Tips
Windows
- Wired Xbox controllers perform best
- Disable USB power saving on hubs
macOS
- Test multiple browsers for best results
- Some browsers show higher latency
Android
- Bluetooth latency varies widely
- USB OTG usually improves response
Linux
- Kernel and udev rules matter
- Chromium-based browsers often perform best
Troubleshooting Common Issues
High Average Latency
- Switch to wired USB
- Close background apps
- Try Chrome or Edge
Large Spikes or Jitter
- Increase sampleInterval slightly
- Disable CPU power-saving modes
- Compare median instead of average
No gamepad.timestamp
- Use wired mode
- Compare browsers
- Results are still useful for comparisons
Pro Tips – Reduce Latency & Improve Consistency
Quick Wins
- When using the Latency Test, it is recommended to use wired connections and modern browsers to minimize latency and enhance consistency.
- Prefer Chrome or Edge
- Close heavy apps
- Disable USB and Bluetooth power saving
For Developers & QA
- Run repeated tests
- Use medians and percentiles (50th / 95th)
- Log environment details with CSV exports
- Avoid blocking the JavaScript main thread
Safety & Practical Advice
- Avoid extremely tight polling on low-power devices
- Reboot and retest if the results look unstable
- Let the system warm up before final testing
Frequently Asked Questions
Get quick responses to frequently asked questions regarding the Gamepad Latency Test.
