Skip to main content

Gamepad Tester

🎮 Gamepad — Latency Test

The Gamepad Latency Test checks how quickly your controller responds after you press a button or move a stick. Latency means the delay between your action and what happens on screen. If the delay is too high, games can feel slow or unresponsive. With this test, you can see the response time of your controller in real-time, helping you find out if it’s working smoothly or if there’s a lag problem. Just connect your gamepad and start testing—no downloads needed.

Interactive Latency Tester

Connect your controller (USB or Bluetooth), press any button to wake it, then press a chosen test button repeatedly. The tool uses browser-reported timestamps and polling logic to estimate latency (ms). It shows per-press latency, min/avg/max, and a small realtime bar visualization.

Test Controls

Lower = more accurate but higher CPU usage. 16 ms ≈ 60Hz.
Ignore repeated presses within this window to avoid double-counting single physical presses.

Live Readouts & Stats

Last Latency
— ms
Poll Interval
— ms
Samples:
0
Min (ms):
—
Avg (ms):
—
Max (ms):
—
Last ts: —
Note: Uses browser-reported timestamps (if available).

How to use: Choose a button in the dropdown, press Start Test, then repeatedly press that button on your controller at a comfortable pace (don’t mash). The tool will record each press and estimate latency for each event. After enough samples you will see min/avg/max values displayed. Export logs to CSV for deeper analysis.

Disclaimer

This latency test is a browser-based estimate. It relies on the Gamepad API and the browser-provided gamepad.timestamp (when present) plus sampling logic to estimate the time between device-state updates and the page's processing. It does not measure absolute display/input latency (which requires external hardware such as photodiodes or high-speed cameras). Results will vary by controller, OS, browser, CPU load, USB vs Bluetooth, and power state. Use the results as comparative indicators (e.g., wired vs wireless, different browsers, or different controllers) rather than as an absolute hardware measurement.

Full Guide — Understanding, Measuring & Reducing Gamepad Latency

Latency matters for competitive gaming and any interactive experience where control precision counts. This guide explains what latency is, what causes it, how this tool measures it, step-by-step testing methodologies, platform-specific advice, developer notes, and an extensive Pro Tips list. Each major section is boxed for readability.

What is Input Latency?

Definition

Input latency (or input lag) is the delay between a user's physical input (pressing a button or moving a stick) and the time the system responds — typically expressed in milliseconds (ms). For a controller, latency includes the time for the controller to detect the press, transmit it to the host (via USB/Bluetooth), for the OS and browser to process it, and for the application to update visuals or behavior.

Why it matters

  • Competitive gameplay: Lower latency improves reaction times and precision.
  • Rhythm and timing games: Accurate input timing is critical for scoring.
  • VR and motion-sensitive applications: Latency affects immersion and can cause discomfort.

Where Latency Comes From (Breakdown)

Controller-side

  • Sampling rate: How often the controller samples its own buttons / sensors.
  • Wireless radios: Bluetooth introduces encoding/decoding and packetization delays.
  • Power-saving modes: Wireless controllers reduce update frequency to save battery.

Transport & OS

  • USB polling interval: HID over USB is polled at certain intervals; faster polling reduces latency.
  • Bluetooth stack: OS Bluetooth stack may buffer or batch events.
  • Driver layers: Device drivers and filtering can add small delays.

Browser & App

  • Gamepad API polling: Browsers poll controllers at their own cadence; `gamepad.timestamp` often reflects when the browser updated the state.
  • Event loop scheduling: JavaScript runs on the main thread; heavy CPU or rendering tasks can delay processing.
  • Frame presentation: Visual update depends on requestAnimationFrame and display refresh rate (e.g., 60Hz → 16.67ms per frame).

How This Tool Measures Latency

gamepad.timestamp — browser-supplied time

When supported, gamepad.timestamp is updated by the browser/driver to indicate the moment the gamepad state changed. By computing performance.now() - gp.timestamp when detecting a pressed button, we estimate the time between the browser’s sample timestamp and the page processing time. This is a widely used method to estimate input-to-browser latency.

Polling cadence & jitter

Because the Gamepad API is polled, the tool also tracks the effective poll interval and jitter (variations in sampling timing). A slower or highly variable poll loop increases measurement noise — the tool shows poll interval to help interpret results.

Limitations

  • If gp.timestamp is not implemented by the browser, the tool falls back to a heuristic that records the first detection time during the sample cycle — less accurate.
  • The tool cannot measure display latency (screen response time) or the very first nanoseconds of hardware sensing inside the controller.
  • Results are best used comparatively (compare modes, controllers, browsers), not as absolute ground truth.

Step-by-Step Testing Procedure

Preparing

  1. Prefer a wired USB connection for baseline testing (removes Bluetooth variability).
  2. Close heavy background apps to reduce CPU contention and scheduling delays.
  3. Use the sampleInterval value around 8–16ms for best results (16ms is typical for 60Hz polling).

Running the Test

  1. Click Detect Controller and confirm your device is shown.
  2. Select the button you want to test (A / Cross is common).
  3. Click Start Test.
  4. Press the chosen button at a comfortable cadence — don’t mash. Aim for 1–2 presses per second to get independent samples.
  5. Collect at least 30–100 samples for meaningful statistics.
  6. Click Stop Test and review Min/Avg/Max latency.

Interpreting the Numbers

  • Sub-16ms: excellent; implies very low browser-side detection delay (often seen with USB + high poll rate).
  • ~16–40ms: common for many setups with 60Hz polling and some buffer overhead.
  • 40–100ms or higher: indicates Bluetooth delays, OS driver buffering, or heavy CPU load.

Platform-Specific Advice

Windows

  • Wired Xbox controllers usually give the best results in Chromium-based browsers.
  • Disable USB power-saving on hubs if you see intermittent spikes.

macOS

  • Gamepad support is improving but may show higher latency in some browsers; test multiple browsers.

Android

  • Bluetooth latency varies by device and Android version; USB OTG typically reduces latency.

Linux

  • Kernel input subsystems and udev rules affect behavior; Chromium-based browsers on modern kernels often give good results.

Troubleshooting — Common Problems & Fixes

High Average Latency

  1. Use wired USB and retest — if latency drops significantly, Bluetooth was the issue.
  2. Close background apps (especially browsers with many tabs, virtualization, or recording software).
  3. Try a different browser — Chrome/Edge are recommended for consistent Gamepad API behavior.

Large Jitter / Spikes

  1. Increase sampleInterval slightly to stabilize readings (but note this reduces temporal resolution).
  2. Check system power settings — CPU throttling can cause uneven scheduling.
  3. Run the test multiple times and compare medians instead of raw averages to reduce outlier influence.

No Timestamp Support

If gp.timestamp is missing, the tool falls back to first-detection heuristics. In that case, compare different browsers or use wired mode to minimize unknowns. You can still get comparative results (e.g., Browser A vs Browser B) even without timestamps.

Extensive FAQ

Q: Is this measuring my controller-to-display latency?
A: No — this tool measures browser-received timestamps and polling timing. True controller-to-display latency requires external sensors (photodiode + oscilloscope or high-speed camera) to measure the display update. Use this tool for browser/driver-level diagnostics and comparisons.
Q: Why does Bluetooth show higher latency?
A: Bluetooth packets are batched and retransmission/encoding adds overhead. Different Bluetooth profiles and controller implementations have different latencies.
Q: Why does latency change between runs?
A: CPU scheduling, background processes, power saving, and wireless interference change timing. Repeat tests and use median/percentile metrics to get reliable comparisons.
Q: What is an acceptable latency?
A: It depends on context. For casual gaming, 30–60 ms may be fine; for competitive FPS, lower is better (sub-20 ms). Compare across your setups to decide what’s acceptable for you.

Pro Tips — Reduce Latency & Improve Consistency

Quick wins

  • Use a wired USB connection instead of Bluetooth where possible.
  • Prefer Chromium-based browsers (Chrome / Edge) for consistent Gamepad API behavior.
  • Close heavy apps and background processes while testing.
  • Turn off power-saving modes for USB ports and Bluetooth adapters.

For developers & QA

  • Automate repeated runs and compute medians and percentiles (50th/95th) to avoid drawing conclusions from a single test run.
  • Log test environment (OS, browser, controller, wired/wireless, CPU load) with each CSV export.
  • Use high-resolution timers (performance.now) and avoid blocking the main thread.

Safety & practical advice

  • Don't run extremely tight polling loops on low-power devices (phones) — they will overheat and skew results.
  • If results look unstable, reboot the test device and re-run tests to clear transient system noise.
Pro tip: When comparing controllers, run multiple short sessions instead of one long session — environmental conditions (Wi-Fi, USB hubs, battery levels) drift over time and bias long recordings.
Community Q&A

Questions About The Latency Test

Real faults players ran into with this test, answered on real hardware and checked by the Gamepad Tester Team.

Ask A Question
My Controller Feels Laggy Only When I Play On My TVVerified By Gamepad Tester

The controller is almost certainly fine; TVs add display lag from picture processing. Turn on game mode or the TV's PC or low latency mode, enable automatic low latency mode if available, and turn off motion smoothing and other processing.

Read the full answer
Should I Use A Wired Or Wireless Controller If I Care About Winning?Verified By Gamepad Tester

Wired is genuinely faster, but by roughly 5 to 10ms, which is below what most players can perceive. The real argument for wired is consistency and never dropping out mid-match, not the raw figure.

Read the full answer
Everything Tests Perfectly But The Game Still Feels Delayed And FloatyVerified By Gamepad Tester

You are probably not imagining it, but the controller is not the cause. A clean controller with a floaty feel almost always points to the display chain or in-game settings, and there are specific things to measure.

Read the full answer
How Much Input Lag Is Actually Normal, And Is My Controller Too Slow?Verified By Gamepad Tester

Your numbers are good. Wired 11ms and Bluetooth 19ms are both in the normal band. Worry above roughly 25ms wired or 40ms wireless, or if the figure is unstable rather than high.

Read the full answer
Can Anyone Explain Why Inputs Feel Late In Menus But Fine In Gameplay?Verified By Gamepad Tester

Menus usually run at a lower frame rate and often add deliberate animation delay, so the same input takes longer to show a result. It is the game's presentation, not your controller.

Read the full answer

All guides and answers