What browser hardware tests can and can’t tell you
Understand which hardware signals a browser can observe and where device diagnostics, app settings or physical inspection are still needed.
Browser tests are useful because they let you check a device without installing a diagnostic package. Their convenience doesn’t remove the boundary between the hardware and the information a web page receives. Interpret each result as an observation of a particular setup.
Input tests observe delivered events
Keyboard Tester shows key events that reach the page. A system shortcut may be intercepted before the browser receives it. A function key managed inside the laptop may not behave like an ordinary letter key.
Mouse Tester similarly observes pointer and button events. It doesn’t inspect the switch inside the mouse. Repeated unexpected events can suggest a problem worth investigating but they aren’t a photograph of the failed component.
If an input is missing then compare an ordinary application and the relevant system settings. A difference between applications is valuable evidence because it points you toward input handling rather than immediately toward replacement hardware.
Camera and audio tests check one signal path
Webcam Tester can show whether this browser receives a picture from a permitted camera. It doesn’t prove that a meeting application selected the same camera or that a call will have sufficient network bandwidth.
Microphone Tester lets you inspect and record captured audio. Listen to the sample as well as watching the meter. Background noise can move a meter even when the intended voice is quiet or a different input is active.
A speaker check confirms audible output through the selected playback path. Room acoustics and output-device settings affect what you hear. Start at a low volume and don’t treat a tone test as a hearing assessment.
Screen tests depend on observation and timing
A dead-pixel test displays colors that help you inspect the panel. The page can’t look back at the physical display and count defective pixels on your behalf. Clean surface marks and compare different colors before deciding what you see.
A refresh-rate test uses browser timing. Background tabs and scheduling can affect observations. A browser estimate isn’t interchangeable with every display setting or a dedicated measurement instrument.
Controllers have a separate application layer
A controller test reports state exposed by the browser. A game can have different mappings or require a specific supported configuration. If the browser responds while a game doesn’t then preserve that distinction when troubleshooting.
Don’t infer that every special controller feature is supported from a working button display. The useful result is a record of which inputs responded under the tested connection.
Know when to use another method
Storage health and battery wear need appropriate operating-system or manufacturer tools. Physical damage needs inspection. Browser tests don’t establish the ownership history of a used machine or predict how long a component will last.
For a purchase combine the used-hardware checklist with these observations. Record the date and connection setup alongside symptoms. If a fault repeats across independent applications or machines then that evidence is more useful than a single unexplained score.
Our testing methods explain the automated checks behind this site and their limits.
Common questions
Does passing every browser test certify a used computer?
No. These checks cover observable input and output in the tested session. They don’t establish battery health or storage reliability and can’t replace checking ownership and the condition of the machine.
Can a browser prove the exact physical cause of a failure?
Usually not. The same missing input can arise from a device fault or software handling. A test gives you evidence to compare across setups rather than a guaranteed component-level diagnosis.
Why are readings different in another browser?
Browsers can expose different features and process timing differently. Permissions and active-tab behavior also matter. Record the browser and test conditions before comparing numerical results.