ClackLab was founded on a simple conviction: you should not need to download questionable third-party executable files or install bloated proprietary companion drivers just to verify whether your gaming peripherals are performing to their technical specifications.
Modern gaming hardware is marketed with staggering claims—8,000Hz polling rates, 0.2ms optical actuations, and infinite key rollover. Yet, when a switch begins double-clicking or key inputs drop during a clutch round, gamers are left guessing whether the culprit is mechanical failure, Windows USB power saving, or in-game latency.
ClackLab provides an open, transparent, and instant diagnostic suite designed to measure real physical input performance directly inside modern web browsers across four international languages.
Our Core Principles
Zero Downloads
No .exe files, no kernel-level drivers, no installation wizards. Every tool runs instantly in standard browser environments.
Absolute Privacy
Your inputs never touch our servers. Every keystroke, click, and cursor motion is processed locally in client memory and discarded on tab close.
Microsecond Precision
We leverage high-resolution performance.now() browser APIs, providing millisecond and sub-millisecond event timestamps.
Four Native Languages
Full support for English, Korean, Japanese, and Turkish—crafted specifically for local gaming and hardware communities.
Technical Architecture & Timing Methodology
How does a browser accurately test hardware latency and polling rates? Modern browsers provide high-performance low-level APIs that allow direct interaction with the host operating system's input subsystem:
- High-Resolution Monotonic Timers: Unlike standard JavaScript
Date.now()(which is subject to system clock skew and drift), ClackLab utilities utilizewindow.performance.now(), a monotonic clock with microsecond-level precision. - Pointer & PointerLock APIs: Our mouse polling and latency tests listen directly to unscaled
pointermoveandpointerdownevents, bypassing synthetic software mouse acceleration. - Matrix Event Listeners: Keyboard tests utilize native
keydownandkeyupevent listeners, cross-referencing physical hardware scancodes (event.code) rather than localized OS character mappings.
Who We Are
ClackLab is maintained by mechanical keyboard builders, competitive FPS players, and web performance engineers. We believe in transparent hardware benchmarking, open technical education, and reproducible testing methodologies.
Have suggestions for new diagnostic tools, found a bug on a specific operating system, or want to contribute a localization correction? Visit our Contact page—we read and reply to all feedback.