CPS Test – Kohi, Jitter & Click Speed Test
Measure clicks per second with multiple clicking modes.
Complete browser testing toolkit
Test speed, reaction, typing, device sensors, hardware, controllers, keyboards, displays, hearing signals and speakers through one organized browser-based collection.
Choose a browser test
Use these tests to observe clicks, typing, controller input, screen patterns, audio playback and supported device sensors. Start with the test that matches the symptom, then check its permissions and setup. Results describe what the browser can measure or display; timing estimates and visual screenings have practical limits.
Measure clicking, connection speed, reaction time, spacebar performance and typing accuracy.
Measure clicks per second with multiple clicking modes.
Measure download speed, upload speed, ping and jitter, then review connection guidance.
Measure how quickly you respond to a visual signal.
Count spacebar presses and measure space-bar speed with timed CPS challenges.
Measure typing speed, accuracy and words per minute.
Check device sensors, computer hardware, controllers, keyboards, mobile capabilities and physical scale.
Use your device sensors as a digital spirit level.
Check key computer, browser, display and input functions.
Test controller buttons, triggers, sticks, drift, deadzones, range and vibration.
Visualize key presses, key codes, repeats, rollover and possible ghosting in real time.
Test phone sensors, screen, audio and device capabilities.
Use a calibrated actual-size ruler in centimetres, millimetres and inches.
Screen color vision, inspect pixels, generate tones, estimate refresh rate and test speakers.
Take an Ishihara-style color-vision screening with display checks and result guidance.
Locate stuck pixels and run a targeted rapid color cycle over the affected area.
Inspect monitors, TVs and phone screens with fullscreen solid-color test pages.
Test audible frequencies and generate precise audio tones.
Estimate display refresh rate and inspect motion smoothness.
Test left, right and frequency playback on speakers.
| What to check | How to run it | What you can observe | Main limitation |
|---|---|---|---|
| Clicking, spacebar and typing speed | Choose a duration and use the same input method for repeated runs | CPS counts accepted clicks per active second; typing reports WPM and accuracy. | Browser input handling, test duration and text difficulty affect comparisons. Typing uses five characters as one standard word. |
| Visual reaction time | Wait for the signal, then respond with the chosen pointer or key | Elapsed milliseconds from the browser signal timestamp to your response, with repeated-round statistics. | Display, input and browser delays contribute to the result. It is not a clinical reflex measurement. |
| Connection throughput and request timing | Start a test on the connection you want to compare | Download/upload Mbps and latency-related measurements against the test endpoint. | Wi-Fi, other traffic and the route to this endpoint affect results; they do not describe every internet service. |
| Keyboard or controller input | Focus the page; connect a controller and press a button if it is not visible | Key events and rollover, or Gamepad API buttons, axes, drift, range and supported vibration. | Browser shortcuts and controller mappings limit what is exposed. Haptics require compatible browser and controller support. |
| Sensors and browser-accessible hardware | Run the relevant module and allow only the requested device permissions | Tilt readings or browser-exposed capabilities, workloads and manual device checks. | Motion needs supported sensors and a secure page; some browsers request permission after a tap. Missing access alone does not prove hardware failure. |
| Physical on-screen length | Match the calibration guide to a known reference or enter a measured scale | A ruler in centimetres, millimetres or inches at the chosen calibration. | A CSS inch is not guaranteed to match a physical inch. Recheck calibration after changing zoom, display or scaling. |
| Pixel appearance | Use fullscreen solid colours to inspect the panel; target a suspect area for the fixer’s colour cycle | Visible stuck or dark pixels and whether a stuck pixel changes after cycling. | You inspect the panel yourself. Colour cycling cannot guarantee repair or restore a physically dead pixel; avoid flashing patterns if sensitive. |
| Animation cadence and motion clarity | Keep the tab visible, choose a longer sample and inspect the moving pattern | Estimated Hz = 1000 ÷ median frame interval in milliseconds, plus frame pacing and motion patterns. | This is requestAnimationFrame cadence. Browser caps, power settings, workload and background throttling can differ from the panel’s rated refresh rate. |
| Audio playback or colour screening | Select the output device, begin at low volume, or follow the visual screening instructions | Left/right playback and tones, or responses to colour-vision patterns. | Speaker playback is separate from a microphone test. Hearing and colour results depend on equipment and environment and are not a diagnosis. |
Test tools FAQ
Quick guidance for selecting and using the browser-test collection.
The tester reads controllers exposed through navigator.getGamepads(). Connect the controller, keep the page focused and press a controller button so the browser can make it available. OS support, connection mode and browser mapping affect the buttons and axes shown. A missing device or unavailable vibration can reflect browser support rather than a broken controller.
Bubble Level uses motion and orientation readings, and the hardware tools only expose features the browser supports. Sensor access requires a secure context and may require an explicit permission request triggered by tapping Start or Enable. If readings remain unavailable, check site permission settings and device/browser support. Calibrate the level on a known reference surface before comparing angles.
Speaker Test generates playback with Web Audio, including channel and frequency checks; it does not use microphone input for those checks. Microphone modules in the hardware tests separately request audio input with getUserMedia, which requires permission and a secure context. Choose the intended output device and begin quietly. Tone audibility depends on speakers or headphones and cannot establish a medical hearing age.
CPS is accepted clicks divided by active seconds. Typing net WPM is counted correct characters divided by five and by elapsed minutes; gross WPM uses typed characters. Reaction time subtracts the signal timestamp from the response timestamp in milliseconds. Refresh Rate Test divides 1000 by the median animation-frame interval. Repeat under the same conditions: event handling, display/input delay, browser load and frame scheduling can change the readings.
The pixel test fills the display with solid colours for your visual inspection; fullscreen helps cover more of the panel. The fixer cycles colours over an area and offers no guaranteed repair. For physical measurements, calibrate Online Ruler against a known-size object or measured scale. Its 96 CSS-pixels-per-inch baseline is only a starting point, and zoom, operating-system scaling or moving to another monitor can require recalibration.
Use the Help Center for troubleshooting, Contact to report a broken test, or Request a Tool to suggest a missing testing workflow.