Help Center

Common questions and troubleshooting paths

This page collects the most common questions across keyboard, mouse, screen, and audio/video tools. When the browser can only provide an estimate, we say so clearly.

Keyboard Mouse Screen Audio/Video

Keyboard FAQ

Start by separating browser limits from real keyboard issues such as chatter, dropped input, or rollover conflicts.

Keyboard Key Test Double Click / Rapid Fire Full Key Rollover Test

Why does Fn not show up?

Fn is usually handled directly by keyboard firmware, so the browser does not receive a standard event for it.

Why does Win / Meta sometimes not light up?

Some systems intercept system-level shortcuts before the browser sees them. That is an OS-level limitation, not always a page issue.

One press becomes two inputs. What should I do?

Use the double-click page to confirm the symptom first. If it repeats often, worn switches, unstable contacts, or debounce settings are common causes.

A combo always misses one key. Is that a browser bug?

Not necessarily. Matrix limits or missing NKRO support are more common. Test with your real combo in the rollover page.

Mouse FAQ

The web page helps with clicks, wheel input, motion, and reaction-training observation, but it still is not a hardware lab tool.

Mouse Button Test DPI Test Latency Test

Why is the DPI result only an estimate?

Browsers can see pointer displacement and timing, but they cannot read the mouse hardware’s true DPI directly.

Is the latency page the real mouse latency?

No. It measures pointerdown to next paint on the page, so it is a browser-side response observation rather than end-to-end hardware latency.

Why are side buttons inconsistent?

Some browsers or systems attach default navigation behavior to those buttons, which can affect whether the page receives the event.

What is the reaction test good for?

It is better for understanding aim rhythm, target acquisition, and reaction practice than for reading any real system sensitivity value.

Screen FAQ

Screen tools are best for quick browser-based checks of dead pixels, tint, grayscale, sharpness, and estimated refresh behavior.

Screen Test Color Test Refresh Rate Test

How do I check dead pixels more reliably?

Switch between full black, white, red, green, and blue, then inspect from different distances and brightness levels.

Why does the refresh-rate estimate differ from system settings?

The page uses requestAnimationFrame, so the result can be affected by browser scheduling, window state, and current load.

Why does burn-in cycling not start automatically?

To avoid unnecessary risk on OLED and other bright panels, cycling must always be started manually.

Can the resolution page reveal scaling issues?

Yes. The 1px lines, pixel grid, and sharpness patterns are useful for spotting blur caused by scaling.

Audio/Video FAQ

Media tools depend on browser permissions and API support, so behavior can vary between browsers and operating systems.

Audio/Video Test Microphone Test Camera Test

Why does the page say permission is missing?

The browser needs explicit permission for microphone or camera access. If you already denied it, re-enable the permission in site settings.

Why can’t the speaker test switch output devices?

Browser output-device control is limited and support varies by browser and operating system. Many setups only allow the system default output.

The microphone has live level, but recording is unavailable. Is it broken?

Not necessarily. Some browsers or privacy modes do not support MediaRecorder, so the page keeps live levels but hides recording features.

Does camera stutter always mean a device problem?

No. Check resolution, frame rate, and current browser load first. A high-resolution preview can stutter simply because the browser is busy.

Still not seeing your issue?

Go back to the relevant test page, reproduce the problem, and then use the guidance here to narrow the cause step by step.

Return to home test Read the toolbox guide