Testing Methodology

Published testing methods

This hub contains the full methodology articles GPADLAB has published so far. Tool pages also include concise notes about their implementation and limits, but a dedicated methodology article is not yet published for every diagnostic. 3 methodologies currently documented, with additional methods added as they are reviewed and validated.

Method
GPADLAB Testing Standards
The GPADLAB Controller Health Score is a site-defined browser benchmark combining six stages: stick drift, button response, trigger range, deadzone, latency, and connection stability. Each stage has a fixed point budget, results use four severity bands, and the normalized 0-1000 score maps to grades from S at 950+ to F below 450.
Method
How We Detect Stick Drift
We sample each stick's radial resting magnitude for 5 seconds while the controller sits untouched, then compare the observed maximum with GPADLAB's site-defined bands. Under 0.05 is our healthy reference, 0.05 to 0.15 indicates increasing center offset, and 0.15 or higher is our severe-drift band for further investigation.
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.

Published testing methods

GPADLAB Testing Standards

How We Detect Stick Drift

How We Measure Input Lag