Controller Health Test

A guided check of every button, stick and trigger, with a score at the end.

No controller detected Connect a controller by USB or Bluetooth, then press any button on it.

Ready

Connect a controller and press any button to begin.

    This walks you through a full check of the controller one stage at a time — every button, the range and centring of both sticks, and how far the triggers travel — then scores what it measured out of 100. The score is built from the readings themselves, and the breakdown shows you exactly where the points went.

    How to use it

    1. Connect the controller and press any button so the browser can see it.
    2. Press Start. Work through each stage as it is asked for — the test moves on by itself once a stage is satisfied.
    3. Buttons: press every button once, including the stick presses and the d-pad.
    4. Sticks: roll each one fully around its outer edge so the whole range is covered, then let go.
    5. Rest: hands off the controller entirely while it measures unwanted movement.
    6. Triggers: squeeze each trigger all the way in and release it fully.
    7. Read the score and the breakdown, and copy the result if you want to ask someone about it.

    How the numbers are worked out

    How the score works: buttons 35 points, left stick 20, right stick 20, triggers 15, connection stability 10. Stick points split between resting drift and how much of the range you reached. Rumble is offered as a separate check but is not scored, because browser support for it varies — scoring it would mean the same controller scoring differently in different browsers.

    Common questions

    Some buttons never register. Is the controller broken?

    Not necessarily. Not every button reaches the browser — the centre "home" or "guide" button is often intercepted by the operating system, and extra rear paddles on pro controllers usually report as a copy of another button rather than as their own input. Check whether the button does something elsewhere on your system before assuming it is dead.

    Why is rumble not part of the score?

    Browser support for rumble is inconsistent — it works in Chrome and Edge, and generally does not in Firefox or Safari. A failed rumble test usually means the browser, not the controller, so counting it would punish the wrong thing. It is there as a check you can run, not as points.

    My trigger will not reach 100%.

    That usually means either dirt in the trigger mechanism or a worn sensor. Try the stage again pressing firmly and slowly. If it consistently stops short of full travel, the trigger is not delivering its full range to games either.

    What is the connection score?

    The tool watches for the controller dropping out or stalling during the test. A wireless pad that disconnects mid-test loses points here — that is often a battery, interference or pairing problem rather than a fault with the pad itself.

    Is a lower score a reason to replace the controller?

    Not on its own. A lot of what drags a score down — mild drift, a sticky button, a trigger full of dust — is cleanable or repairable. Treat the breakdown as a list of what to look at, not a verdict.

    Not sure what your result means?

    Post it in the forums and someone who has had the same fault will usually know whether it is worth cleaning, repairing or replacing. You do not need an account to read, and it is free to join.