Controller Tests latency reaction time input lag

Gamepad Reaction Time Test

Measure reaction time from an on-screen cue to a gamepad press. Not USB controller poll latency.

Interactive tool

Run the test

Runs in your browser

After Start, a random 1–3 s delay precedes a flash cue. Press any controller button as soon as you see it. Results include your reaction time plus browser scheduling — not lab-grade input latency.

Wait…

Press Start, then wait for the flash. Reaction + browser scheduling only.

Permission status

Checked in your browser. DeviceHub does not store permission grants.

  • Special permission Not required

Live results

Metrics update as you run the test. Nothing is uploaded.

Loading

Waiting for interactive tool output…

Device information

Labels and capability details reported by your browser.

No device details yet.

Description

About Gamepad Reaction Time Test

Introduction

Gamepad Reaction Time Test measures delay from an on-screen cue to your controller press as timestamps in the browser. Human reaction, display refresh, and browser scheduling dominate. It is not USB controller poll latency.

What this tool does

The tester schedules a visual cue, watches Gamepad button pressed transitions, and computes a delta. Results show per-trial times and simple averages when available. Pair with Gamepad Test to confirm the button works at all.

When to use it

Use it when comparing Bluetooth versus wired feel, evaluating two pads on the same PC, or teaching that reaction drills differ from hardware poll myths. Prefer hardware analyzers for certified input-lag numbers.

How it works

Cues use high-resolution clocks in the page. Presses are observed through Gamepad polling aligned with animation frames, so poll granularity is included. Background tabs throttle timers. No Permissions API prompt appears.

Step-by-step instructions

  1. Open Gamepad Reaction Time Test, connect the pad, and press a button to wake the Gamepad API.
  2. Start a trial, wait for the cue without anticipating, then press promptly.
  3. Complete several trials and note the average rather than one lucky run.
  4. Optionally repeat USB versus Bluetooth with browser and display settings held constant.

Common problems

High totals usually reflect human reaction plus display and browser scheduling. Wrong button index or an asleep pad causes missed detections. Do not publish results as controller poll rate.

Privacy explanation

Reaction timestamps stay in your browser session. DeviceHub does not upload scores or controller identifiers. No microphone or camera permission is requested.

Runtime principles

Built for the browser

What happens when you run this test — without downloads or accounts.

  1. 01

    Runs in your browser

    Gamepad Reaction Time Test uses standard web APIs — no install, extension, or desktop app required.

  2. 02

    Reads what the browser allows

    Results come from events and capability signals the web platform exposes for this session.

  3. 03

    Private by default

    Input and diagnostic values stay in your browser session for display — nothing is sold as media.

Compatibility

Supported browsers

Expected support for modern engines. Individual APIs may still vary by device.

  • Chrome

    supported

    Latest stable

  • Firefox

    supported

    Latest stable

  • Safari

    supported

    Latest stable

  • Edge

    supported

    Latest stable

Devices

Supported devices

Hardware and form factors this browser test is designed to exercise.

  • USB & wireless gamepads

    When the browser Gamepad API exposes the device.

  • Console-style controllers

    Xbox, PlayStation, and similar pads with browser support.

  • Fight sticks & specialty pads

    Mapped as standard gamepad inputs when recognized.

Privacy

Your data stays with you

Gamepad Reaction Time Test is built privacy-first. Diagnostics run in your browser session whenever web APIs allow.

Read our privacy policy

Troubleshooting

Common problems

Quick fixes before you dig into FAQs.

Times look much higher than expected
This is reaction-time best-effort, not USB poll hardware measurement. Use a foreground tab, wired connection, and several trials, human reaction dominates the total.
Presses never register
Wake the gamepad with a button first, keep focus on the page, and confirm the same button works in Gamepad Test.
Results jump wildly between trials
Variance is normal for human reaction tests. Average multiple runs, disable heavy background CPU load, and avoid Bluetooth if you need tighter repeatability.

FAQ

Frequently asked questions

Structured answers for users and FAQ rich results.

Browse FAQs
Is this USB controller poll latency?
No. Results are reaction time between an on-screen cue and your press, not a hardware USB analyzer measurement.
Why are my times so high?
Human reaction, display refresh, and browser scheduling dominate. Compare averages on the same PC rather than chasing laboratory HID numbers.
How many trials should I run?
Several. Single trials are noisy. Average multiple runs with the tab focused and, when possible, a wired connection.
Presses are not detected
Wake the pad first, keep focus on the page, and confirm the button index in Gamepad Test or Mapping Test.
Can I compare Bluetooth vs wired?
Yes. Keep browser and display settings fixed so the connection path is the main variable.

Newsletter

Updates coming soon

A lightweight email digest for new tools and release notes is planned. No signup form is live yet — check Release Notes for product updates.

Release notes

Need another diagnostic after Gamepad Reaction Time Test?

Explore related DeviceHub tools that pair well with this test.