On this page
The short version
Every number comes from the gamepad data your browser already gives web pages. No downloads or special drivers.
Every controller is judged against the same limits. They're all listed below, along with every change.
All the maths runs on the page. A share link carries the result inside the link itself.
Where the numbers come from
Your controller sends its state to your computer or phone. The system and its driver turn that into standard values, and the browser hands them to web pages through the Gamepad API. From that, we read three things:
- Axes. Each stick has an X and a Y axis, from −1 to 1. Zero on both means dead center.
- Buttons. Each button reads from 0 (not pressed) to 1 (fully pressed). Triggers are buttons that can sit anywhere in between.
- Timestamp. When the browser last received new data from the controller.
Stick drift
Drift is a stick reporting movement while nobody is touching it. Here's how the drift test and the health check measure it:
- You let go of both sticks.
- For 3 seconds, we record every reading of each stick's X and Y.
- For each reading, we work out its distance from the center.
- The resting distance is the median of those distances.
We use the median so that one twitch doesn't change the verdict. We don't subtract a resting offset, and we don't apply a deadzone of our own.
These starting limits follow the open-source stick-drift-detect project (MIT licence). After testing more controllers we may set different limits per model, and every change will be listed in the change log.
Circularity
A stick pushed to its edge should reach the same distance in every direction.
- You rotate the stick slowly around its edge, 3 full turns.
- We split the circle into 72 slices of 5° each and keep the farthest reading in each slice. That's the stick's reach in that direction.
- The average error is the mean gap between each slice's reach and a perfect 1.0.
We'll confirm this limit after testing more controllers. Until then, circularity never produces a fail.
Deadzone
The deadzone test suggests in-game settings for one stick at a time. It gives suggestions, not a verdict.
- You let go for 2 seconds. We record the largest distance from the center: the resting max.
- You push the stick slowly to the edge. The first reading clearly above the resting max is the first movement. If the stick read exactly 0 at rest and its first movement is above 0.04, the controller has a built-in deadzone.
- You turn the stick once around the edge. As with circularity, we keep the farthest reading in each of 72 slices.
Triggers
Triggers are analog. While you press each one all the way and let go, we record its lowest and highest value.
A trigger that stops short of the top may never register a full press in some games.
Vibration
A web page can ask the browser to vibrate the controller, but it can't tell whether the motors actually spun. So we play each motor and ask whether you felt it. The result is felt, not felt or not supported in this browser.
“Not supported” is a browser limit, so it never counts against your controller.
Report rate
We count how many times per second the timestamp changes, which tells us how often the browser receives new data from the controller.
The number is capped by how often the browser itself checks the controller, and it only changes when the input changes, so keep a stick moving while it measures. It is not the controller's own polling rate, and it is not input lag.
We also rate how steady the readings are, from the jitter: how much the gap between readings varies, compared with the average gap.
What a browser can't measure
We'd rather tell you what's out of reach than show a number that looks precise and isn't.
- The controller's real polling rateBrowsers check controllers on their own schedule, which is often slower than the controller can report.
- Input lagTiming a press all the way to the screen needs a camera or dedicated hardware, not a web page.
- Readings before the driverSome systems apply a small deadzone of their own, which can hide very small drift.
- Adaptive triggers, light bar, motion sensors and batteryThese need a lower-level browser feature that this site doesn't use yet.
All limits
The full set of limits behind every verdict. Provisional limits may change after more hands-on testing.
| Check | Pass | Warn | Fail | Status |
|---|---|---|---|---|
| Stick drift (resting distance) | < 0.10 | 0.10 – 0.25 | ≥ 0.25 | Set |
| Circularity (average error) | < 8% | ≥ 8% | — | Provisional |
| Deadzone (suggested settings) | Suggestions only, no verdict | Provisional | ||
| Trigger range | ≤ 0.02 → ≥ 0.98 | anything else | — | Provisional |
| Buttons | registers cleanly | stuck or bouncing | no response | Provisional |
| Vibration | felt | not felt | — | Set |
| Report rate (steadiness) | Steady < 15% | Some jitter < 35% | Uneven ≥ 35% | Provisional |
Change log
- Limits v1.0
First published limits. Stick drift limits follow stick-drift-detect. Circularity, deadzone, trigger, button and report rate limits are provisional.
- Next
Per-model limits, once we've tested enough DualSense and Xbox controllers.
Does a result look wrong for your controller? Tell us which controller, browser and system you used, and we'll look into it.
Contact us