Controllers
Inspect browser-reported stick positions, button and trigger values, connection changes and sample timing. Repeat suspicious readings before deciding whether the controller or its software settings need attention.
GEARCHECK LABTest controllers, keyboards, mice, touchscreens, styluses, mobile sensors, displays, audio, webcams and microphones directly in your browser. No download or account required. Diagnostic device readings stay in your browser.
Inspect browser-reported stick positions, button and trigger values, connection changes and sample timing. Repeat suspicious readings before deciding whether the controller or its software settings need attention.
Check every key, test simultaneous rollover and detect ghosting or chatter across the full matrix.
Verify pointer movement, click switches, wheel input and polling-rate behavior with live browser measurements.
Map touchscreen coverage, watch for unexpected touch contacts, and inspect browser-reported stylus pressure and tilt. These checks do not certify sensor accuracy or ghost-touch resistance.
Inspect accelerometer, gyroscope and orientation data from your mobile device in real time.
Screen for dead pixels, colour uniformity, gradient banding and sharpness with fullscreen test patterns.
Check stereo channel routing, listen for repeatable rattles at selected tones and compare relative microphone input levels. Acoustic frequency response requires calibrated measurement equipment.
Confirm webcam and microphone access, inspect negotiated resolution and frame rate, and watch a relative level meter.
Device input readings and media previews are processed locally. The Internet Speed Test is different: it transfers generated test bytes to and from our server to measure the connection path. Ordinary page requests, usage measurement and contact messages also use network services; see the Privacy Policy for details.
A useful diagnosis starts with a repeatable symptom. Change one variable at a time and keep notes of the connection mode, browser, device setting and result. A second run under the same conditions is more informative than a single score.
A clean run means the symptom was not observed in the signals available to this browser during that run. It does not guarantee every component works, establish warranty eligibility or identify an internal failed part. Browser support, drivers, firmware, operating-system shortcuts and wireless conditions can alter what the page sees.
Repeat an unexpected result, compare a supported browser or connection, and use the manufacturer's utility when calibration or firmware changes are needed. The testing methodology explains the measurement boundaries. If a tool fails to start, report the tool URL and the visible error so the issue can be investigated.
Choose a focused diagnostic, inspect the available browser signals and compare a repeat run.
Use guided inspections, private media checks and bounded performance comparisons.
Use guided inspections, private media checks and bounded performance comparisons.