How the tools work
Quick Test Hub Measurement Methodology
This page explains what each core tool records, how the visible result is calculated, and where the browser cannot provide a laboratory-grade measurement. The goal is a useful, repeatable check—not a misleading claim of precision.
One session, one local result
Core tests run in the current browser tab. Timing and input values are calculated from events observed during the active session. The site does not need an account for a test result, and the tools do not ask for a name, password, payment information, or government identifier.
Some features such as recent CPS attempts or a personal best use browser-local storage so the same browser can show a comparison later. That local history is not a server-side profile. Clear the site's browser data to remove it.
Timing and speed tools
| Tool | Recorded signal | Visible calculation | Best comparison practice |
|---|---|---|---|
| Reaction Time | Time from the green signal to the click or tap. | Average of five valid rounds, plus best and slowest round. | Use the same device, browser, display, and input method. |
| Typing Speed | Characters typed, elapsed time, and mismatches against the sample. | Words per minute, accuracy, elapsed time, and error count. | Compare the same language, passage length, keyboard, and layout. |
| CPS | Clicks or taps received during the selected timer. | Clicks per second = total clicks ÷ timer seconds. | Compare the same timer length and input surface. |
| Spacebar Clicker | Space key presses during the fixed ten-second run. | Presses per second = valid presses ÷ ten seconds. | Keep the same keyboard and avoid held-key auto-repeat. |
| Double Click | Click pairs and the interval between clicks. | Double-click count, click count, and fastest observed pair. | Use the same mouse and button when comparing results. |
These values describe browser-observed behavior. They include human movement, event delivery, display refresh, operating-system scheduling, and device latency. The page cannot separate those components or certify a mouse, keyboard, display, or person.
Keyboard and pointer checks
The Keyboard Test listens for key events and shows the key name, code, and the set of keys detected in the session. The Mouse Test listens for buttons, wheel movement, double-click events, and pointer movement. These tools answer a practical question: did the browser receive the input event?
The Keyboard Polling Rate Test runs for ten seconds while the visitor alternates two keys. It ignores held-key repeats, converts each positive interval to an estimated rate using 1000 ÷ interval in milliseconds, and reports the average rate, peak rate, interval range, jitter, and a broad stability label. It is an event-timing estimate, not a USB-bus or firmware measurement.
Camera, microphone, and controller checks
The Microphone Test requests microphone permission only after the visitor starts it. The page reads the live time-domain signal into a browser analyser and displays a relative level and peak meter. It does not upload or record the audio. Stopping the test stops the media tracks.
The Webcam Test requests video permission after the start action, displays the local video stream, reports the resolution exposed by the browser, and can draw a still image into a local canvas. The Gamepad Tester reads the browser Gamepad API and displays buttons and axes while the tester is running. Browser support, permissions, drivers, focus, and another application's use of the device can affect what appears.
How to make a fair repeat comparison
- Use the same device, browser, display, and input method.
- Close obvious CPU-heavy or media applications and keep the test tab focused.
- Run several attempts and compare the average or pattern, not only the fastest value.
- Record the timer length and input method when sharing a result.
- Treat a sudden change as a troubleshooting clue; check connections, permissions, browser load, and device settings before drawing a conclusion.
Privacy boundary
Camera and microphone access is controlled by the browser permission prompt. The live streams are used by the page for the local preview or meter and are stopped when the test stops or the page is left. Do not paste confidential API schemas, passwords, private documents, or sensitive personal information into any browser tool, including QA generators.
Analytics may record anonymous tool-start and tool-complete events so the site owner can find broken flows. These events describe the tool and coarse result parameters; they are not intended to contain camera frames, microphone audio, typed passages, or raw device streams. See the Privacy Policy and Cookie Policy for the broader site controls.
What these tools are not
Quick Test Hub is not a medical, psychological, employment, school-placement, safety, hardware-certification, or laboratory measurement service. Use a qualified professional or calibrated diagnostic tool when a decision has safety, health, legal, or financial consequences.