Network diagnostics
Compare connection throughput, stability and delay under load using bounded server-path tests.
Every public GearCheck Lab diagnostic in one place. Start broad, then use focused tools to isolate controller faults, keyboard/mouse input problems, touchscreen or stylus issues, phone motion sensors, display defects, audio routing/polarity or camera/microphone behavior.
Use everyday symptoms too, such as “keys repeating”, “mouse clicks twice”, “screen touches itself” or “microphone too quiet”.
No close match yet. Try a device name or a shorter symptom.
Compare connection throughput, stability and delay under load using bounded server-path tests.
Use the full controller lab for a quick overview or choose a focused test when you already know the symptom.
Verify individual keys, test simultaneous rollover/ghosting, or isolate a suspect switch for repeated same-key retrigger timing.
Check movement and clicks, measure CPS/click speed, estimate DPI from a measured physical travel distance, compare browser-visible event rate, test held-button dropouts, investigate repeated clicks, or reproduce reverse scroll-wheel events.
Map touch-only coverage and simultaneous contacts, or run a hands-off monitor for unexpected browser-reported touch contacts.
Separate pen-signal questions from trajectory questions: inspect browser-reported pressure/tilt/buttons, or measure slow-stroke straightness and repeatable line wobble without fake hardware scores.
Inspect browser-exposed phone/tablet orientation, acceleration including gravity, gyroscope rotation rate and sensor update cadence.
Check browser-reported resolution, viewport and DPR, inspect pixels and uniformity, estimate browser-visible refresh cadence, and compare ghosting/smearing/overdrive artifacts using a controlled moving target.
Start with a broad audio output check, use the focused headphone left/right stereo test for channel routing, sweep and hold frequencies to find rattles, and compare in-phase versus inverted stereo polarity.
Use the combined private media test or isolate webcam resolution/frame rate, microphone level, short local record/playback, and live frequency-spectrum/noise-floor comparisons.
Inspect read-only MIDI input in a supporting browser after granting permission.
Check which browser interfaces are exposed before starting a device test. API exposure is a compatibility signal, not a hardware score.