Gamepad Tester controller logo GamepadTester
DIAGNOSTIC TOOL / 05

How often does the browser see input?

A transparent browser-side estimate for input sampling—not a measurement of the controller's physical USB or wireless polling rate.

Run this test →

LIVE GAMEPAD DIAGNOSTICS

Connect your gamepad

Browser sample-rate test

CONTROLLER 01

No controller detected

Offline
GAMEPADREADY
YXBA
LBRB
Waiting for input
Button events0Last input—
COMPLETE INPUT MAPPRESS EACH CONTROL
Face buttons
A0.00
B0.00
X0.00
Y0.00
Shoulders & triggers
LB0.00
RB0.00
LT0.00
RT0.00
Menu & stick clicks
Back0.00
Start0.00
L30.00
R30.00
Directional & system
D-pad up0.00
D-pad down0.00
D-pad left0.00
D-pad right0.00
Home0.00
Touchpad0.00
ANALOG INPUT

Stick telemetry

LIVE X / Y
Left stickCENTERED
X +0.00Y +0.00
Right stickCENTERED
X +0.00Y +0.00
DRIFT & DEADZONE

Stick health check

WAITING

Leave the sticks untouched, then calibrate. The result measures the signal exposed by your browser.

Not calibrated
Center offset—
Jitter—
Detection threshold0.12
Drift score—
STICK RANGE

Circle test

READY

Choose a stick, click start, then rotate it around the edge once. The result is an estimate based on radius consistency and angle coverage.

Samples0
Min radius—
Max radius—
Angle coverage0%
Radius score—
ANALOG BUTTONS

Triggers

0 — 1.00
LT / L20.00
RT / R20.00
HAPTIC FEEDBACK

Vibration test

NOT READY
RAW GAMEPAD API DATA

Input snapshot

Axes0.00, 0.00, 0.00, 0.00
Buttons pressedNone
Browser sample rate—
API modeStandard Gamepad

Browser-side diagnostic only. Connect the controller in your operating system first; this page cannot pair Bluetooth or install drivers. Results depend on the browser, operating system, connection and controller mapping.

WHAT IT CHECKS

Measure the signal, not the guess

Use the live browser sample counter to compare input delivery under wired and wireless controller connections. It reports requestAnimationFrame timing, not a hardware polling specification.

  • Live requestAnimationFrame sample count
  • Wired versus Bluetooth comparison
  • Browser and display conditions
  • Clear limits of the estimate
HOW TO GET A CLEAN RESULT

Test conditions matter

Use a wired connection when possible, close other controller software, and press a button after the device is connected.

  • Keep the same display refresh rate during comparisons.
  • Run each connection mode for several seconds.
  • Treat the result as browser sampling, not hardware polling.
  • Use a native hardware tester for true controller polling measurements.
Privacy by design: input data is read and processed locally by your browser. It is not uploaded to a server.
KEEP TESTING

Related tools

Analog diagnosticsJoystick drift testCheck joystick center offset, deadzone, jitter and unwanted movement.Open →Analog diagnosticsGamepad calibrationSet a browser-side center reference and check stick range without changing controller firmware.Open →Input diagnosticsButton testCheck every button, D-pad direction, bumper and trigger response.Open →Haptic diagnosticsVibration testTest supported light, heavy, burst and pulse rumble patterns.Open →
FAQ

Questions about this test

Is browser polling rate the same as hardware polling rate?+

No. This page reports the browser animation-frame sample rate, which can be affected by display refresh rate, browser scheduling and system load.

How should I compare wired and Bluetooth?+

Run the same movement pattern in both modes and compare the observed browser sample rate under the same browser and display conditions.