Browser Diagnostic Center · 32 specialist tests

Test your hardware and devices in your browser

Find the right specialist test by name, technical term, or symptom. Run it immediately with honest browser limits, no installation, and no account.

  • No account
  • No installation
  • Runs locally
  • Permissions only when needed

Search names, tasks, and symptoms. Try “frame rate”, “black smear”, “mic”, or “stick drift”.

Diagnose a problem

Start with what you notice

Choose the closest symptom; these curated routes suggest a test without pretending to diagnose hardware.

Common diagnostics

Start with these tests

Quick paths into common browser-visible display, motion, and audio checks.

Guided checks

Complete one real task

Move through several specialist tests with neutral observations and a local-only report. A check never turns browser evidence into a hardware health score.

4 stepsLocal session

Video Call Check

Check the browser-visible camera, microphone, speaker, and optional headphone path before a call.

A local record of what you opened and observed in this browser.Start check
9 stepsLocal session

Used Device First Check

Run a browser-visible first pass across common input, display, camera, and audio functions on a laptop, desktop, all-in-one, or display setup.

A local coverage record for the browser-visible checks you chose to perform.Start check
6 stepsLocal session

Gaming / Controller Setup Check

Check browser-visible input and display timing before a gaming or controller setup session.

A local record of input coverage and browser-observed display timing checks.Start check

Browser-visible first pass only—not OEM diagnostics, hardware certification, a repair diagnosis, or a warranty report.

Browse by device

Device test categories

Choose the hardware area, then use the category guide to select the right specialist test.

What a browser test can tell you

Evidence, not a universal health verdict

DeviceMetrik names the kind of evidence each instrument can produce and keeps unsupported hardware conclusions out of the result.

Read the measurement methodology

Direct browser input

Keyboard, mouse, gamepad, and touch tools read browser-exposed events or state—not electrical switches, firmware, or raw USB traffic.

Browser-observed timing

FPS, refresh, event-rate, DPI, and reaction tools estimate what reaches or runs in the browser—not laboratory hardware timing.

Visual and listening checks

Controlled patterns or signals help you inspect what you see or hear. Your observation is not an automatic hardware diagnosis.

Camera and microphone capability

Media tools request only the needed permission after Start and process locally. They do not upload media or certify device quality.