All tests
Before a call
Microphone, camera, speakers and headphones — the things that fail right before a meeting, interview or exam.
Keyboard, mouse, controller, touch
Every key, button, stick and finger, with the numbers that tell wear from settings.
Screen
Dead pixels, pure colours, real refresh rate and everything your browser knows about your display.
When something fails
A test that fails tells you why — permission blocked, no device found, device busy — and links to the fix for your app and system. The most-read guides:
Why this exists
Microphones, cameras and speakers fail at the worst moment: a minute before an interview, a lecture or a proctored exam. Most of the time nothing is broken — the wrong device is selected, an operating-system switch is off, or another app is holding the hardware. These tests use the same browser interfaces your call app uses, so a pass here means the hardware and the system are fine and only the app’s settings remain. The guides go straight to those settings, in the order that finds the fault fastest.
Questions, answered
Is anything recorded?
No. Audio and video are analysed in your browser and discarded. The report is text you can copy; it never leaves your device unless you share it.
Why does the browser ask for permission?
Browsers require your consent before any page can use the microphone or camera. Choose Allow; the test cannot run without it.
Will a pass here guarantee my meeting works?
It proves the hardware, the operating system and the browser can use the devices. Your meeting app must still have permission and the right device selected — the guides show where.