About DeviceMetrik
DeviceMetrik provides browser-based tests for input devices, controllers, displays, audio, and cameras without requiring a desktop utility. The directory currently contains 32 implemented tests.
What DeviceMetrik can observe
Direct browser input
Keyboard, mouse, gamepad, and touch tools read the input state exposed by the browser while you interact with the page.
Browser-observed estimates
FPS, refresh timing, event timing and rates, and reaction timing are estimates based on browser scheduling and timestamps.
Visual checks
Pixel, frame-skipping, tearing, ghosting, and stuck-pixel tools present controlled visual patterns for you to inspect.
Permission-dependent media
Microphone, pitch and vocal input, webcam, and online mirror tools depend on browser permissions and available media APIs.
What the results do not prove
Browser observations are not laboratory measurements, certified hardware measurements, or manufacturer diagnostics. Browser scheduling, the operating system, settings, scaling, permissions, and hardware support can all affect interpretation. A result does not prove true hardware polling rate, certified latency, automatic fault diagnosis, or hardware-health certification.
Privacy and permissions
Current tools do not require an account. Microphone and camera access is not requested automatically: the relevant permission is requested only when you start a media-dependent tool. Applicable media processing runs locally in the browser, and the test does not automatically upload raw microphone audio or camera frames.
Methodology, feedback, and corrections
Each test page states its workflow, result meaning, and browser-specific limits. DeviceMetrik treats a browser observation as evidence for the current session, not as a certified hardware verdict.
If a method or explanation appears incorrect, a useful correction includes the page, browser and device context, steps to reproduce, and the observed output so the wording or method can be reviewed against the browser evidence.