Controller Diagnostics Hub
TEST A CONTROLLER METHODICALLY
A useful controller diagnosis is more than moving both sticks once and deciding whether the pad “feels fine.” Different faults produce different signals. Stick drift, an oversized deadzone, a weak trigger, a chattering button, a poor wireless link and inconsistent browser-visible update timing can all feel like “the controller is bad” while requiring very different next steps.
This guide gives you a repeatable order for testing a gamepad in the browser, explains what each measurement can and cannot tell you, and links directly to GearCheck Lab’s focused controller diagnostics. The tools run locally in your browser and are intended to narrow down a problem—not to certify that every internal component is perfect.
A practical controller test sequence
When the symptom is unclear, test from the simplest signal checks toward the more specialized measurements. Changing several settings at once makes diagnosis harder because you lose track of which change affected the result.
- Confirm the controller is actually detected.
Connect the pad, press a button to wake browser gamepad access, and confirm the browser reports a controller before interpreting any other measurement. If detection itself is unstable, start with the Controller Connection Test. - Release both sticks and observe the centre.
Place the controller on a stable surface and keep your hands off the sticks. A repeatable non-zero resting offset is more informative than a single brief fluctuation. Use the Stick Drift Test before changing deadzone settings. - Check the full stick range.
Rotate each stick slowly around the edge and visit the cardinal and diagonal directions. The Circularity & Range Test helps reveal uneven outer travel or a weak quadrant that a centre-only drift check would miss. - Test buttons and triggers separately.
Press every digital button and then move each analogue trigger from rest to full pull several times. Use the Gamepad Button Test and Controller Trigger Test to isolate missing or inconsistent inputs. - Evaluate deadzone only after measuring the raw centre.
A deadzone is a software choice, not a repair. The Controller Deadzone Test helps show how much centre movement would be ignored by a chosen threshold. - Compare update behaviour under repeatable movement.
Move a stick continuously and use the Controller Polling Rate Test as a browser-visible activity estimate. Repeat the run rather than treating one number as a hardware specification. - Test optional output features last.
If your browser/controller combination supports gamepad vibration output, use the Controller Vibration Test. Lack of browser vibration support is not automatically proof of a failed motor. - Repeat suspicious findings after reconnecting.
If the result matters—for example before repair, return, warranty or buying a used controller—repeat the relevant test after reconnecting and, when possible, compare wired and wireless modes.
Choose the controller diagnostic that matches the symptom
The broad controller lab is useful when you are not sure where the problem is. Focused tests are better once the symptom is known because they give more context for one signal instead of mixing several measurements together.
Stick drift and deadzone are different problems
Stick drift describes reported movement while the stick is released. The important word is reported: the browser receives an axis value away from the neutral centre even though you are not intentionally moving the stick.
A deadzone is an intentional software range around centre where small movements are ignored. Games use deadzones because analogue hardware is not perfectly motionless and because different controllers have different centre behaviour.
If you increase the deadzone until unwanted movement stops, the symptom may disappear in that game, but the underlying centre offset still exists. A larger deadzone also reduces fine control near centre. That is why GearCheck Lab separates the raw drift check from the deadzone visualization.
Do not treat one percentage as a universal pass/fail standard for every game. A competitive shooter with a small configured deadzone may reveal centre movement that a racing game with a larger deadzone ignores.
Why circularity and outer range matter
A stick can centre well and still have a range problem. Worn mechanics, calibration differences or physical interference may cause one direction to reach a different maximum than another. A circularity/range pass asks a different question from a drift test: what shape does the reported outer movement create when the stick is rotated around its full edge?
Move slowly enough to cover the perimeter rather than flicking the stick around randomly. Repeat the circle in both directions. If the same quadrant repeatedly falls short, compare the other stick and, where practical, repeat on another device or connection before deciding the controller needs service.
USB vs Bluetooth: use the connection as a diagnostic variable
If a controller supports both wired and wireless operation, testing both modes can help separate a device-input problem from a connection-path problem. The browser still receives data through the operating system in either case, so this is not a laboratory latency comparison. It is a practical A/B troubleshooting step.
| Observation | What it suggests | Useful next step |
|---|
| Same stick drift over USB and Bluetooth | The centre offset is less likely to be caused only by the wireless link. | Repeat the drift sample, check calibration and inspect deadzone needs. |
| Inputs freeze only over Bluetooth | Wireless pairing, interference, battery state or the Bluetooth stack may be relevant. | Charge the controller, re-pair it and compare again with USB. |
| Controller is detected only after pressing a button | This can be normal browser/gamepad activation behaviour. | Press a face button after connection before concluding detection failed. |
| Polling estimate changes between runs | Observed browser timing is affected by the whole software/connection path. | Repeat multiple runs under similar conditions and compare trends, not one isolated peak. |
| Vibration works in one browser but not another | Browser/API support may be the limiting factor rather than the motor itself. | Confirm compatibility before treating lack of rumble as hardware failure. |
What browser controller diagnostics can measure
Strong use caseLive stick axes, digital button state, analogue trigger values, centre offset and repeated movement patterns.
Useful comparisonChanges between wired/wireless runs, before/after calibration, or one controller versus another on the same system.
Needs cautionPolling estimates, vibration support and any result that depends heavily on browser, OS, driver or connection behaviour.
The browser reads the controller data exposed through standard web APIs. It does not directly inspect potentiometers, Hall sensors, solder joints, batteries or internal mechanical wear. A clean browser result therefore means “no problem was visible in the tested signals under these conditions,” not “every component has been certified perfect.”
How to make a result more repeatable
- Place the controller on a stable surface for centre/drift measurements.
- Do not rest a thumb on the stick during an untouched sample.
- Use the same browser and system when comparing before/after results.
- Repeat a suspicious result instead of relying on one brief reading.
- Test another USB port or cable when connection behaviour is involved.
- Charge wireless controllers before diagnosing intermittent input.
- Record the exact game deadzone/settings separately from the browser measurement.
- If a repair was performed, test the same sequence before and after the repair.
When the result points toward repair
Browser testing cannot tell you which internal component has failed, but repeated patterns can justify closer inspection. Persistent centre movement that returns after reconnecting and calibration, a trigger that repeatedly stops well before the opposite trigger, or a button that intermittently disappears across multiple runs are all stronger evidence than a one-off glitch.
Before opening hardware, check warranty status and manufacturer guidance. Cleaning or disassembly can create additional damage or affect warranty coverage. If the controller is expensive, safety-critical for accessibility, or still covered by warranty, professional or manufacturer service may be the better next step.
GearCheck Lab diagnoses browser-visible signals. It does not repair controllers and does not replace manufacturer service tools, electrical testing or physical inspection.
Controller testing FAQ
Can a browser controller test prove that my controller is fault-free?
No. It can reveal repeatable problems in the input and output data that the browser can access. It cannot inspect every internal component or guarantee future reliability.
Should I test over USB or Bluetooth?
If your controller supports both, test both when diagnosing an intermittent or timing-related symptom. Matching results help rule out a connection-only cause; different results provide a useful troubleshooting clue.
Is stick drift the same as deadzone?
No. Drift is unwanted reported movement when the stick is released. Deadzone is an intentional software range that ignores small movement around centre.
Why does my controller not appear immediately?
Browsers and operating systems may not expose gamepad data until the controller is connected and an input is pressed. Connect the controller, focus the page and press a face button before concluding it is unsupported.
Why does polling rate vary?
The number shown by a browser test reflects observed update activity through the controller, connection, operating system, browser and current page timing. Repeat the test under similar conditions and compare trends rather than treating a single run as a hardware specification.
Can the vibration test damage my controller?
The tool only requests a short supported browser vibration effect. Stop testing if the controller behaves abnormally. Browser vibration support varies, and a missing response is not automatically proof that the motor is defective.
Start with the symptom you actually have
If you are unsure, begin with the full controller test. If you already know the symptom, use the focused test so the measurement and troubleshooting guidance match the problem.