Which browser tests help a freelance IT technician?

When a client says a microphone stopped working, Wi-Fi keeps dropping, or a laptop feels slow, you need a quick way to narrow down the cause. Browser tests can check many common devices and connection behaviors without installing a diagnostic app.

Start with Test Everything for a step-by-step pass, then use individual tests to investigate the reported symptom. Treat the results as evidence, not a complete diagnosis: a browser cannot inspect every driver, component, or system setting.

Run useful checks in a client visit

1. Open Test Everything on the device being checked and follow the prompts. Tell the client which tests may request camera or microphone permission, and get their approval before granting access. The tool runs its tests step by step and gives a report.
2. Get a basic picture of the machine with System Info and Browser Info. Note the reported processor, graphics, screen, browser version, permissions, and supported features. A browser can report only a rounded hint about RAM, not the exact installed amount.
3. Choose tests based on the complaint rather than treating every result as equally important. For input problems, use Keyboard Test or Mouse Test. For calls, use Camera Test, Microphone Test, or Speaker Test. For screen complaints, open Display Test.
4. For a network complaint, compare connection quality with Wi-Fi Signal, throughput with Speed Test, and repeated dropouts with Connection Stability. Speed Test exchanges test data with TooLab's server to measure the connection.
5. After a repair or setting change, repeat the relevant test under similar conditions. Record the device, browser, time, connection type, symptom, and observed result in your service notes. Avoid including client passwords, private recordings, or unrelated personal details.

For a short visit, begin with the complaint and a focused test. Use the full step-by-step check when the client wants a wider baseline or when the cause is unclear. Some checks, such as battery information, appear only if the device's browser reports a battery.

What the results can tell you

A device responds consistently in its browser test

If each key registers, the mouse responds to movement and clicks, or the camera preview appears, the browser can communicate with that device in the current setup. If the client's app still fails, check its device selection, permissions, and settings next. A successful browser test does not prove that every program or driver is working correctly.

A test cannot access the device

That may point to a blocked permission, an unavailable device, or a browser limitation rather than broken hardware. Camera and microphone tests need permission. Some tools also need specific browser support, so check Browser Info and try a supported browser before replacing equipment.

Connection quality is poor or changes during testing

A low speed reading points to limited throughput at that moment. Repeated delay spikes or lost requests in Connection Stability suggest interruptions, but they do not identify whether the router, Wi-Fi environment, ISP, VPN, or another device is responsible. Browsers cannot read Wi-Fi signal strength in dBm. Wi-Fi Signal measures how the connection behaves instead.

The results look normal, but the problem continues

Try to reproduce the issue in the same app, location, and workload where the client noticed it. A short browser check may miss a fault that happens only after warming up, under load, or with a particular accessory. Record when it occurs, then choose a test that matches that condition.

Fix common test blockers

1. Check the browser's permissions. Use the icon next to the address bar to review camera or microphone access, allow the device if the client agrees, and reload the page. A denied permission can look like a device failure.
2. Check system privacy access. In Windows 11, open Settings › Privacy & security › Camera or Settings › Privacy & security › Microphone, then check access for apps and desktop apps. On macOS, open System Settings › Privacy & Security › Camera or System Settings › Privacy & Security › Microphone and allow the browser.
3. Select the intended audio device. In Windows 11, open Settings › System › Sound and check the input or output device. On macOS, open System Settings › Sound and choose the device under Input or Output. A headset can connect successfully while the computer continues using its built-in microphone or speakers.
4. Close other apps using the device. Quit meeting, recording, or camera software, then try the browser test again. Another app may be using the camera or microphone, or may have selected a different device.
5. Reconnect the accessory and retest. For a wired device, check the plug and try another port. For a wireless device, confirm that it is connected and charged. If the issue remains, test the accessory on another computer when practical.
6. Update or restart only after recording the current result. A restart or driver change can clear useful evidence. Note what failed first, then restart or follow the computer or device manufacturer's update instructions and repeat the focused test.

When a browser test points to hardware

If a built-in keyboard, speaker, camera, or screen shows the same fault in more than one browser and in the operating system, hardware becomes more likely. Confirm with a second device or a known-good accessory where possible. A browser test cannot inspect a loose internal connector, diagnose a damaged circuit, or prove that a storage device is reliable. For a computer still under warranty, document the symptom and test conditions before contacting the seller or manufacturer. For out-of-warranty equipment, compare the cost of a part or repair with replacement.

Keep the test within its limits

Browser checks are useful because they run on the client's device without installing a diagnostic program. Most checks are local. Speed tests exchange test data with the server for measurement, so explain that distinction when discussing privacy. Do not use a browser score alone to promise a specific repair or certify that a device is fault-free.