Device tests family
Browser Device Tests and Troubleshooting Guide
Use repeatable browser checks to narrow a symptom, while recognizing that an online test cannot confirm every hardware, driver, operating-system, or security cause.
What this page helps you do
Browser device tests can help isolate a problem by producing a controlled input or output and recording what happens. A touch-screen test can reveal areas that do not register during a simple pattern, a speaker test can compare channels, and a keyboard polling-rate test can observe events delivered to the browser. These observations are clues, not a definitive hardware diagnosis.
Prepare the environment before testing. Save work, disconnect unnecessary accessories, confirm volume and mute settings, clean the device according to manufacturer guidance, close applications that intercept input, and note the browser, operating system, connection type, and permissions. Repeat the same test after one change at a time so that the result remains interpretable.
The grid below should list only published tests. Review each test’s permission request, data handling, supported browsers, measurement method, and expected limitations. Do not claim that a passing browser test proves security, electrical safety, warranty status, or full device health.
Published resources in this family
Free WebGPU Test for Browser Support, GPU Limits, Shader, and Compute
Free Webcam Test for Resolution, FPS, Camera Preview, and Snapshot
Free Online Mic Test for Level, Noise, Clipping, and Playback
Free WebGL Test for WebGL 1/2 Support, GPU Limits, and Rendering
Free Mouse Latency Test for Click Delay, Jitter, and Consistency
Free Audio Spectrum Analyzer With Live FFT, Peak Frequency, and Band Energy
Free Keyboard Latency Test for Event Delay, Jitter, P95, and Consistency
Free Audio Latency Test for Browser Output, Scheduling, and Loopback Estimates
Free Screen Pixel Ruler With Drag Measurement and Physical Calibration
Free Browser Compatibility Test for Modern Web Features and APIs
Free Browser Storage Test for LocalStorage, IndexedDB, Cache, and Quota
Free Keyboard Tester for Keys, Codes, Chords, Repeat, and Event DetailsChoose the right approach
Test one pathway
Choose the smallest test that matches the symptom: touch registration, audio channel, keyboard event timing, camera permission, microphone input, or display behavior.
Control the environment
Record device, browser, OS, accessories, settings, connection, power state, and recent changes. Avoid changing several variables at once.
Compare and escalate
Repeat in another supported browser or user account, use the manufacturer’s diagnostics, and contact qualified repair or support when the symptom persists or safety is involved.
Reference table
| Symptom | Browser check | What the result may suggest | Next step |
|---|---|---|---|
| A screen area does not respond | Trace slow lines across the full touch surface | A repeatable dead area, palm rejection, protector interference, or browser issue | Remove nonessential accessories, restart, compare an approved diagnostic, and seek service if repeatable. |
| Only one audio channel is heard | Play left and right channel samples at a safe level | Balance setting, cable orientation, speaker path, or source problem | Check balance and connectors; compare headphones or another known source. |
| Keys repeat or miss | Use a key display and controlled typing sample | Key switch, layout, accessibility setting, wireless link, or event handling | Check layout and settings, compare wired mode or another device, and clean safely. |
| Polling result varies | Run several short samples under similar load | Browser scheduling, system load, connection, device firmware, or test design | Use median and range; do not treat one peak value as device certification. |
| Permission is denied | Review browser site permissions and OS privacy controls | Permission state, insecure context, policy, missing device, or another app using it | Change only the required setting and retest with a trusted page. |
| Test passes but the app fails | Compare the target app and a minimal browser test | Application configuration, codec, driver, account, network, or content issue | Use app-specific support and manufacturer diagnostics. |
Worked troubleshooting example: intermittent speaker output
A laptop sometimes produces sound only from the right side. The user first notes the operating system, browser, output device, connection, and whether the symptom affects every application. Volume is lowered to a safe level before any tone is played.
The browser speaker test plays a left-channel sample, a right-channel sample, and a centered sample. The left channel is missing in both the browser and a local operating-system sound test. Headphones work correctly, while the internal speakers show the same symptom after a restart.
This pattern narrows the issue but does not prove which component failed. The user checks the balance control, removes audio effects, installs only manufacturer-approved updates, and runs the manufacturer’s diagnostic. No liquid, heat, burning smell, damaged cable, or battery swelling is present.
Because the internal left channel remains absent across two independent sources, the user records the observations and contacts service. The browser test helped create reproducible evidence; it did not authorize disassembly or establish a warranty conclusion.
Practical checklist
Prepare safely
Save work, lower audio levels, inspect for obvious hazards, and stop if there is heat, odor, smoke, swelling, exposed wiring, or liquid damage.
Record the setup
Note browser, OS, device model, connection, permissions, accessories, power state, and the exact symptom.
Run repeatable checks
Use the same sequence, change one variable at a time, repeat several times, and record both passes and failures.
Choose the next route
Use official diagnostics, backups, updates, accessibility support, warranty service, or qualified repair as appropriate.
Assumptions, limitations, and review
Browser timing and event delivery are affected by operating-system scheduling, system load, power management, wireless conditions, browser implementation, and page design. A browser measurement is not laboratory calibration.
A successful test does not prove that a device is secure, electrically safe, free from intermittent faults, or suitable for medical, industrial, emergency, or accessibility-critical use.
Do not open equipment, bypass safety systems, install untrusted drivers, or raise audio to uncomfortable levels to force a result. Follow manufacturer instructions and qualified service guidance.
Related TestsAndTools pages
External reference resources
These links support further verification and learning. External sites have their own content, privacy, and accessibility practices.
MDN: Permissions API
Technical reference for querying and working with browser permission states.
MDN: MediaDevices.getUserMedia()
Technical reference for requesting microphone and camera media streams, including security and permission requirements.
Frequently asked questions
Can an online test confirm that my hardware is broken?
It can show a repeatable browser-level symptom, but confirmation may require operating-system, manufacturer, electrical, or repair diagnostics.
Why do results differ between browsers?
Browsers differ in permissions, event scheduling, APIs, media handling, security rules, and support. System load and settings also matter.
Is a high keyboard polling result proof of performance?
No. Review repeated results, test conditions, latency elsewhere in the system, and the device manufacturer’s specifications.
What should I do when a permission request does not appear?
Check secure connection requirements, site permissions, OS privacy controls, policy restrictions, device availability, and whether another app is using the device.
When should I stop testing and seek repair?
Stop for electrical or battery hazards, physical damage, persistent repeatable failures, warranty concerns, or any situation where disassembly or safety expertise is required.