Testing Methodology

How we measure everything

Every diagnostic tool on GPADLAB is backed by a documented algorithm. This is where we show the work — the exact code paths, the numeric thresholds, the sample windows, and the honest limits of what browser-based testing can measure. 3 methodologies documented, more shipping soon.

Method
GPADLAB Testing Standards
The Controller Health Score combines six diagnostic stages — stick drift, button response, trigger range, deadzone, latency, and connection stability — into a single 0-1000 composite. Each stage has a fixed maximum point value; each result maps to healthy, partial, mild, or faulty severity, and grades range from S at 950+ down to F below 400.
Method
How We Detect Stick Drift
We sample the radial magnitude of each stick's resting position for 5 seconds while the controller sits on a flat surface untouched, then compare the observed maximum against a three-band threshold. A stick reading under 0.05 is healthy; between 0.05 and 0.15 is mild drift; over 0.15 warrants replacement.
Method
How We Measure Input Lag
We sample the elapsed time between successive controller input events using performance.now() inside a requestAnimationFrame loop, over a 10-second active window with at least 30 valid samples. The result reports polling-loop latency — how quickly the browser observes state changes — not thumb-to-photon end-to-end input lag.

How we measure everything

GPADLAB Testing Standards

How We Detect Stick Drift

How We Measure Input Lag