Start with a core input or display diagnostic, then use focused follow-up checks for the same device or signal.
01 / Input
Check browser-visible signals from pens, touchscreens, mice, keyboards, and controllers.
Test stylus pen pressure, tiltX/tiltY, pointer type, and drawing response in the browser using the Pointer Events API.
Test touchscreen multi-touch support, touch IDs, coordinates, and browser touch input on phones, tablets, laptops, and touch monitors.
Check left click, right click, middle click, scroll wheel up/down, and double-click issues online.
Check mouse polling rate and mouse Hz with median, peak, distribution, and stability metrics.
Check mouse double-click issues, switch chatter, click interval, and accidental double clicks online.
Test every key on your keyboard and check keyboard ghosting, NKRO combinations, modifiers, and key chatter online.
Test keyboard anti-ghosting and N-key rollover (NKRO) by pressing multiple keys simultaneously and seeing which register.
Test controller buttons, triggers, analog sticks, deadzones, and stick drift in your browser.
02 / Display
Inspect pixels, motion, refresh timing, uniformity, contrast, HDR setup, and visible flicker patterns.
Check your monitor, laptop, TV, or phone for dead pixels, stuck pixels, backlight bleed, and IPS glow with full-screen color patterns.
Check backlight bleed, IPS glow, dirty screen effect, clouding, and color tinting with full-screen solid colors.
Check monitor Hz, 60Hz, 144Hz, 240Hz, frame pacing, and display refresh rate online.
Check monitor ghosting, motion blur, inverse ghosting, overdrive artifacts, and pixel response online.
Calibrate monitor brightness and contrast with near-black, near-white, ANSI contrast, PLUGE, and white clipping patterns.
Check OLED, AMOLED, and LCD image retention using solid colors, gray screens, and checkerboard patterns.
Check HDR setup, near-white clipping, shadow detail, contrast, and color volume using browser-rendered test patterns.
Display simulated flicker patterns from 30 to 1000 Hz for visual inspection. Includes motion ruler mode and a warning-gated strobe mode.
03 / Audio + Video
Verify browser permission, live input, playback channels, and camera output before troubleshooting hardware.
Test speakers, headphones, left/right stereo channels, frequency sweep, bass, and microphone input online.
Free microphone test online. Check mic input level, peak clipping, and live waveform in your browser.
Test your webcam or camera. Check live preview, resolution, frame rate, permissions, and image quality.
Supporting checks
Use these after a core diagnostic points to a narrower device, setting, or signal.
Check monitor color banding, posterization, gradient smoothness, and 8-bit vs 10-bit bit depth online.
Test your subwoofer and speakers with low-frequency tones from 20 Hz to 200 Hz. Find the lowest bass your system can reproduce.
Estimate your mouse DPI by moving it a measured distance. Compare repeated browser readings with your configured sensitivity.
Test headphone channel balance, frequency sweep, and phase response. Verify left/right audio and stereo imaging.
Test your mouse scroll wheel speed and behavior. Measure deltaY values, scroll direction, and events per second.
Rapidly cycle colors to try fixing stuck pixels on LCD monitors, TVs, laptops, and phones.
Test individual speaker channels including left, right, center, and surround. Verify each speaker in a multi-channel setup.
Test Xbox controller buttons, analog sticks, triggers, and D-pad in your browser. Detect stick drift with adjustable deadzone.
Check monitor black level, near-black shadow detail, black crush, lifted blacks, and PLUGE calibration online.
Test Nintendo Switch Pro Controller and Joy-Con buttons, sticks, and triggers in your browser. Detect Joy-Con drift.
Check monitor color temperature, D65, 6500K, white balance, warm/cool tint, and gray ramp neutrality online.
Estimate webcam frame-update rate delivered to your browser. View the live feed with resolution and device info.
Test DualSense buttons, triggers, analog sticks, deadzones, and stick drift in your browser.
Verify monitor geometry with circle test, grid, diagonals, crosshair, and ruler patterns. Detects display resolution and closest aspect ratio.
Display browser-reported resolution, available area, device pixel ratio, estimated pixel dimensions, color depth, and orientation.
Check your display color depth and view gradient test patterns to detect 8-bit vs 10-bit color banding.
Measure browser animation-frame timing over 10 seconds using requestAnimationFrame. See average, min, and max FPS with a live bar chart.
Measure browser-level click-to-frame latency using requestAnimationFrame. See average, best, and worst lag across 10 clicks.
Utilities
Useful browser utilities and performance exercises that sit outside the core diagnostic workflow.
Measure your click speed with 10s/30s/60s timers. Track CPS/CPM, left/right clicks, and share results.
Measure your reflex speed in milliseconds with a 5-round click test. Compare to gamer and average population benchmarks.
Click targets to train mouse accuracy and measure targets per second. Three difficulty levels: large, medium, and small targets.
Precision click test — click stationary targets and measure your accuracy percentage and click speed across difficulty levels.
Measure your typing speed in words per minute (WPM) and accuracy. Choose 30s or 60s mode with color-coded word feedback.
Non-calibrated browser hearing range screening with tones from 125 Hz to 16000 Hz. Compare left/right perception and learn when a clinical audiogram matters.
Simplified Ishihara-style color vision screening with 8 colored dot plates. Results are browser-based and not medical diagnosis.
Measure browser-to-server HTTP request round-trip time with 10 requests. See average, min, and max response time in milliseconds.
Benchmark your browser JavaScript engine with Math, DOM, String, and Array workloads.
Stress the browser rendering pipeline with a Canvas animation of 500 moving circles and monitor live FPS.
Benchmark browser JavaScript CPU speed with integer math, float math, prime sieve, Fibonacci, and JSON parsing.
Check browser memory usage, JS heap size, approximate device memory, and run a 50MB allocation speed test.
Record your screen directly in the browser using the Screen Capture API. Download recordings as WebM video files.
Diagnostic map
Browser hardware tests are most useful when they answer one narrow question. A keyboard tester can show whether the browser receives a key event; a refresh-rate test can estimate visible frame timing; a solid-color screen can reveal a fixed pixel defect. None of those results, by itself, certifies an entire device.
Start with the symptom you can observe, select the smallest relevant test, and repeat it under controlled conditions. If the result changes when you switch a cable, port, browser, source device, or operating-system setting, that comparison is usually more useful than one isolated score.
Repeatable workflow
Write down what fails, when it happens, and whether it affects one application or the whole device. “One key is missing” is more testable than “the keyboard feels wrong.”
Use a supported browser, keep the tab visible, connect the device directly when possible, and close software that can intercept input, audio, camera, or display timing.
Repeat the same test without changing anything. Then change one variable—such as browser, cable, USB port, profile, or source device—and run it again.
Save the observation, not just the score. A stable defect across browsers and source devices points toward hardware; a result that moves with software points toward configuration.
Tool selection
SIGNAL / 01
Use keyboard, mouse, polling-rate, or controller tests when a press, click, movement, axis, or button is missing or inconsistent. First confirm that the page has focus and that the operating system sees the device. Browser shortcuts, game modes, remapping software, Bluetooth power saving, and USB hubs can all alter the signal before the page receives it.
SIGNAL / 02
Use solid colors for fixed bright or dark points, gray fields for visible uniformity, motion patterns for response artifacts, and refresh timing for a browser-observed frame-rate estimate. Clean the panel and compare another input before treating a mark as a pixel defect. Visual tests do not replace a colorimeter, photodiode, or warranty inspection.
SIGNAL / 03
Use channel playback to verify left/right routing, microphone and webcam tests to check permission and live input, and recording tools only after selecting the intended device. A silent result can come from browser permission, the OS mixer, an incorrect default device, a muted physical control, or the hardware itself.
Result discipline
Timing results vary because browsers schedule events, merge pointer updates, throttle background tabs, and share CPU/GPU time with the rest of the system. A single maximum value is therefore weak evidence. Compare repeated runs, the spread of values, and whether the same behavior appears in another browser or native system tool.
For visual checks, keep viewing distance, room light, brightness, scaling, resolution, and refresh mode consistent. For input checks, use the same movement, connection mode, device profile, and test duration. Documenting those conditions makes a support or warranty conversation much more useful.
Field checklist
Measurement boundary
A browser is intentionally sandboxed. It receives selected events and media streams after the device firmware, operating system, drivers, and browser have processed them. That makes online tests convenient and safe for screening, but it also limits the claims a result can support.
Before you decide
No. First rule out focus, permission, browser compatibility, operating-system settings, cables, ports, profiles, and another source device. Hardware becomes more likely when the same physical symptom stays fixed across those comparisons.
Browsers can use different event-coalescing, graphics, power, and scheduling paths. Treat browser timing as an observation of that browser environment, then compare repeated runs under the same conditions.
Raw keyboard, mouse, microphone, camera, and controller inputs are processed in the browser. Ordinary page requests, aggregate analytics when enabled, and explicit network-test requests can still occur; the privacy policy describes those boundaries.
Include the exact model, connection method, operating system, browser, tested settings, repeatable steps, screenshots or photos, and whether the behavior remains on another port, cable, browser, or device.
Continue the diagnosis
Use the methodology guide to understand browser measurement boundaries, or follow the practical checklist when you need to decide whether to reconfigure, repair, return, or keep a device.