Testing Methodology

How We Test

Every tool on GamepadTools reads live data from standard browser APIs — nothing is simulated or pre-recorded. We build each tool against real hardware (multiple controller and mouse models, a range of monitors and GPUs) before publishing, and we re-check a tool whenever a browser update changes how its underlying API behaves.

The goal of every tool is the same: give you a fast, honest read on whether your hardware is working correctly, using only what a browser can legitimately access. That's a real constraint — browsers can't read firmware, query a mouse sensor's native DPI setting, or bypass privacy protections some browsers apply to GPU information. Where that limits accuracy, we say so below rather than overstate what a browser-based tool can promise.

Gamepad Tools

All seven gamepad tools read input through the Gamepad API, polled continuously via requestAnimationFrame so on-screen values update in sync with your controller's actual state. Button and axis indices follow the W3C Standard Gamepad Mapping, which is why the button map is consistent across Xbox, PlayStation, and Nintendo controllers even though the physical layouts differ.

• Latency Test measures the time between an input event firing and the page registering it, using performance.now() timestamps. This captures browser and rendering latency; it can't fully isolate Bluetooth radio latency from USB polling latency, so we recommend comparing the same controller over both connections rather than treating the number as an absolute spec.
• Vibration Check uses the GamepadHapticActuator interface where supported. Not every browser/controller combination exposes haptic control equally — if a check fails, that can reflect API support rather than a broken motor.
• Battery Check uses WebHID, available only in Chromium-based browsers (Chrome, Edge, Opera). This is a browser limitation, not a bug in the tool.

Mouse Tools

Mouse tools read standard pointer and mouse events with high-resolution timestamps.

• DPI Analyzer estimates DPI by measuring how far your cursor travels on screen relative to a calibrated physical distance you provide. Browsers cannot query a mouse sensor's hardware DPI setting directly, so this is a careful estimate, not a firmware readout — expect it to land close to, but not always pixel-identical to, the number in your mouse's manufacturer software.
• Mouse Polling Rate calculates Hz from the interval between consecutive mousemove events during continuous motion. Very old or heavily throttled systems can under-report a mouse's true polling rate.
• Click Speed Test and Double Click Test both rely on click event timestamp deltas, which is the same mechanism your OS and games use to interpret clicks.

GPU & Monitor Tools

• GPU Check reads the WEBGL_debug_renderer_info WebGL extension. Firefox's strict privacy mode and some browsers in incognito/private windows intentionally mask or generalize this string for fingerprinting-privacy reasons — if GPU Check shows a generic result, that's usually the browser protecting your privacy, not a detection failure.
• Frame Rate Test counts actual rendered frames per wall-clock second via requestAnimationFrame. This measures browser rendering performance, not in-game FPS — a full 3D game engine under load will report differently than a browser tab.
• Refresh Rate Test infers your monitor's refresh rate from consistent frame-timing intervals measured over several seconds. It's an inference from timing data, not a direct query of your display's EDID, so results are typically accurate to the nearest standard refresh rate (60/75/120/144/165/240Hz) rather than an exact decimal.
• Screen Bleeding Test is a guided visual test — full-screen solid color panels for you to inspect — not an automated defect scanner. Judging bleed vs. normal panel behavior is inherently a human call.
• Resolution Check reads window.screen and device pixel ratio directly from the browser, which is reliable and matches your OS display settings.

Accuracy & Limitations

These are diagnostic tools built for fast answers, not certified test equipment. They're well suited to answering "is something wrong with my hardware" and "roughly how well is it performing" — they are not a substitute for manufacturer calibration tools, oscilloscope-based latency measurement, or professional repair diagnostics when a warranty claim is on the line.

Keeping This Current

Browser APIs change. When a browser update affects how a tool reads data, we update the tool and this page. If a result looks wrong for your setup, email contact@gamepadtools.com with your browser, OS, and hardware — reports like this are how we catch API changes early.