What a good hardware report cannot prove

A hardware report can look reassuring when every check appears normal. But a browser test can only report what it was able to measure during that session. It cannot certify that every part is healthy or guarantee that a problem will not come back.

Use Test Everything to check the available hardware step by step and get a report. Then use the limits below to decide what a result does, and does not, tell you.

Run the report in a useful way

1. Open Test Everything on the device you want to check, then follow the on-screen instructions for each test.
2. Connect devices you want checked, such as a headset, external display, controller, or USB drive. A browser cannot test hardware that is disconnected or unavailable to it.
3. Allow camera or microphone access when a test needs it. If you deny permission, the test may not be able to check that device.
4. Let each check finish, and note any warning or test that could not run. If one result concerns you, run the relevant focused test again under the same conditions.
5. Write down what was connected, whether the laptop was charging, and what you were doing when a problem appeared. These details help you compare results later.

What the result means

The checks look normal

This means the tests that ran did not find an issue in the measurements they made at that time. It does not prove that a device will work under every workload, that a fault is not intermittent, or that a problem in another app is fixed. If the original symptom returns, note when it happens and test that part again while the symptom is present.

A test shows an unusual result

Treat it as a reason to investigate, not a final diagnosis. A slow score can depend on background activity, temperature, power settings, or the connection between devices. Repeat the test once with other demanding apps closed. For a memory speed result, for example, the Memory Test (RAM) measures read, write, and copy speed, not whether every memory chip is physically healthy.

A test is missing or unavailable

This does not automatically mean the hardware is broken. The browser may not expose that feature, the device may not have it, or permission may be blocked. Battery Meter and Charger & Cable Test appear only when a device's browser reports battery information. Some browser features also work only in certain browsers or on computers.

The report looks good, but the problem continues

The symptom may depend on an app, a driver, a cable, or a condition that the test did not reproduce. A microphone can work in a browser but be muted in a meeting app. A network can respond well during a brief check and still drop later. Test the suspected part while reproducing the problem, and check the settings in the app where it happens.

How to get stronger evidence

1. Repeat the check under controlled conditions. Close games, video calls, and other heavy tasks, then run the focused test again. For wireless problems, use Wi-Fi Signal to observe response time, jitter, and lost requests, or Connection Stability to watch for dropouts over a few minutes.
2. Check what the operating system sees. On Windows 11, open Settings › System › About for basic device details. On macOS, open the Apple menu and choose About This Mac. These screens can confirm information the browser reports only approximately.
3. Check permissions and device selection. On Windows 11, open Settings › Privacy & security and check the permission for the device in question. On macOS, open System Settings › Privacy & Security and check the relevant permission, such as Microphone or Camera. Also verify that the affected app selected the intended device.
4. Compare with a second connection or accessory. Try another cable, port, headset, or network when possible. If the same symptom follows one accessory across devices, that is stronger evidence against the accessory than one browser result alone.
5. Keep a record of repeat failures. Note the date, conditions, and which focused test showed the issue. If the problem affects important work or persists across devices, use that information when contacting the manufacturer or a repair shop.

Why a browser report has blind spots

A browser is not a full hardware diagnostic program. It can check only the features the browser and operating system make available, and it cannot inspect every component directly. A test can show that a key registered or that a screen displayed colors, but it cannot measure every mechanical property or predict how long the part will last.

Some measurements are intentionally limited. Browsers get only a rounded hint about RAM size, not an exact amount. Wi-Fi tools cannot read signal strength in dBm, a radio signal measurement. They measure how the connection behaves instead, including response time, jitter, and lost requests. A Battery Meter can show charge information when the browser reports a battery, but it cannot determine the battery's full physical condition from one reading.

Network results also depend on conditions beyond your device. Speed tests exchange test data with our server to measure the connection, so the result reflects the route and network load during the test as well as your local equipment. A clean report is useful evidence, but it is one snapshot, not a guarantee.