I’ve been working on a small project called PCHardwareTest.
The idea started from a simple problem: sometimes you just want to know whether a keyboard, mouse, webcam, microphone, speaker, screen, or controller is actually responding, without installing another desktop utility.
So I built a browser-based toolkit that lets you run several hardware checks directly from the browser.
It currently includes:
- Keyboard testing
- Mouse and touchpad testing
- Microphone testing
- Speaker and headphone testing
- Webcam testing
- Screen and dead-pixel visual checks
- Gamepad testing
- Touchscreen testing
- Battery status
- Network information
- Browser-reported system information
One thing I tried to be careful about is not claiming more than the browser can actually detect. For example, the system information section can show things like logical CPU cores, approximate device memory when supported, screen resolution, viewport size, touch capability, and browser information, but it cannot reliably identify the exact CPU or GPU model.
Everything runs in the browser, and permission-based features such as camera and microphone only request access when you start those tests.
Project:
https://pchardwaretest.com/
I’m still improving it, so I’d especially like feedback from other developers: what hardware test would be most useful to add next?
Top comments (2)
A browser-only hardware toolkit is the kind of thing people land on straight from a search like "test my mic online", so the page titles end up doing a lot of the work here.
I'm a Staff SDET and ran an automated QA pass on pchardwaretest.com. It scored 98/100 (A), so there isn't much to pick at. The top flag was title length on the tool pages: "Touchscreen Test Online | Free Touch Screen & Multi-Touch Tester" is 64 characters, and the microphone, headphone and network test pages are over 60 too, so Google cuts the tail off in results. Trimming the part after the pipe (say, "Touchscreen Test Online | Free Multi-Touch Tester") is a quick fix in the shared title pattern.
That pass only turned up 2 other issues.
Thanks for taking the time to run the audit and share the feedback!
The title-length observation is helpful. I'd like to validate it against the actual search snippets before changing the shared title pattern across multiple tool pages.
Could you share the other two issues you found, ideally with the affected URLs and a brief explanation of how to reproduce or verify them? I'd also be interested in seeing the audit report if the free preview provides one.
Thanks again for checking out PCHardwareTest!