DeviceMetrikBrowser diagnostics

Controller Tests

Choose a general controller input check or a focused analog-stick drift analysis.

2 tests

Common problems and tasks

Choose the right path

Missing buttons, unexpected stick movement, trigger ranges, mapping, and real hardware-latency questions are different tasks with different browser limits.

Diagnose a controller symptomChoose button, trigger, axis, drift, polling, or latency context.Run a gaming/controller checkRecord browser-visible input coverage and display timing locally.

Choose by task

Choose the right controller test

Start with the general controller check. Continue to the focused stick test only when the symptom concerns analog centering, noise, deadzone context, or rotation geometry.

General controller checkGamepad TesterUse this first to confirm that the browser sees the controller and inspect its general inputs.
  • Multiple-controller selection and mapping
  • Buttons, D-pad, analog triggers, sticks, and raw axes
  • Session input coverage
  • Capability-dependent browser-supported vibration
Open Gamepad TesterFocused analog-stick analysisStick Drift TestUse this when the issue is unwanted stick movement or you need repeatable analog-center evidence.
  • Hands-off baseline, center bias, and neutral noise
  • P99 neutral envelope and game-specific deadzone context
  • 24-sector rotation geometry and settled return-to-center shift
  • Aggregate-only local history
Open Stick Drift Test

Recommended path

Start broad, then investigate the stick

  1. Start with Gamepad Tester

    Connect and wake the controller, then select the intended pad.

  2. Confirm the general inputs

    Check that buttons, triggers, sticks, and mapping are browser-visible.

  3. Go deeper only when needed

    Use Stick Drift Test for unwanted movement or inconsistent centering.

What browser controller tests can show

  • Inputs, mapping, and connection state exposed through the Gamepad API
  • A short bounded vibration request when a compatible interface is exposed
  • Repeatable neutral and rotation stick samples

A completed vibration request is not proof of motor health.

What they cannot certify

  • Raw USB/HID polling rate or controller, radio, and in-game latency
  • Firmware, battery, complete motor, spring, or overall hardware health
  • Manufacturer calibration or one universal game deadzone

Return-to-center shift compares settled browser-observed centers; it is not snapback latency or mechanical recentering speed.

Other input devices

Looking for keyboard or mouse tests?

Input TestsKeyboard, mouse, scrolling, DPI, event-rate, and reaction checks.