Testing Tools
Quick hardware and browser checks that run right in your browser — test your keyboard, mouse, webcam, microphone and screen, or measure your typing and click speed.
About Testing Tools
When a key stops registering, a phone screen ignores a corner, or a video call insists your microphone is broken, the first question is always the same: is it the hardware, or is it the software? This category exists to answer that quickly, with eighteen checks that run in the browser. If you would rather not pick from a list, start at the Laptop & PC test or the Mobile & Tablet test — each one gathers the checks that actually apply to that kind of device, grouped by what they test, so you can work straight down the page.
Start with whatever the symptom points at. A key that seems dead goes to the keyboard tester, which lights up each key as your browser receives it — if nothing lights up, the problem is before the browser. Erratic clicking goes to the mouse tester; a controller that veers on its own goes to the gamepad tester, where stick drift shows as an axis that never returns to zero. On a phone, the touch screen test finds dead zones by drawing where your finger goes, and the motion sensor test proves the accelerometer still reports. Display trouble splits three ways: the dead pixel test for stuck pixels, the screen resolution checker for what the browser sees, and the refresh rate test to confirm a 120Hz panel is not quietly running at 60. Before a call, run the webcam test and microphone test rather than finding out during it.
Everything here is free, needs no sign-up, and runs entirely in your browser — nothing is installed and nothing is uploaded. That matters most for the camera and microphone: the preview and the level meter are rendered on your own device, so no video or audio is ever recorded or sent anywhere, and access ends the moment you close the tab. The honest limits are worth knowing too. A browser can only report what the operating system hands it, so these tools are excellent at proving something works and at narrowing down where a fault lies, but they cannot diagnose a driver, a cable or a failing component. A few also depend on the browser itself: vibration is Android-only, and battery details are exposed by Chrome and Edge but not by Firefox or Safari. Each tool says so on its own page rather than showing you an empty panel.
Frequently asked questions
Where should I start — is there one page with everything?
Yes. The Laptop and PC test page collects every check that applies to a computer, and the Mobile and Tablet test page does the same for a phone or tablet, each grouped by what it tests. If you open the one that does not match your device, it will point you at the other. Otherwise, pick the tool that matches your symptom from the list on this page.
Is my webcam or microphone recorded when I run the test?
No. The video preview and the audio level meter are produced entirely in your browser on your own device. Nothing is recorded, nothing is uploaded, and access ends as soon as you close the tab. You can prove it by disconnecting from the internet: both tests still work.
A key does not light up in the keyboard tester. Is my keyboard broken?
Not necessarily, but it is a strong hint. It means the browser is not receiving that key. Some keys are intercepted by the operating system before any web page sees them, so check the tester has focus first by clicking it. If an ordinary letter still does nothing, the fault is almost certainly the keyboard itself.
Why does one test say it is not supported on my browser?
Because the browser genuinely does not offer that feature. Vibration works on Android but is blocked entirely on iPhone and iPad. Battery details are available in Chrome and Edge, while Firefox removed them and Safari never added them, both for privacy reasons. Rather than show you an empty panel, each tool tells you which browsers do support it.
Can these tools fix a problem they find?
No, and none of them claim to. They are diagnostic: they tell you whether the hardware is reaching your browser and what it is reporting. That is usually enough to know whether to reseat a cable, reinstall a driver, or take the device in — but the repair itself is a separate job.