Your test data stays in this page
Raw input events, coordinates, page elements, session IDs and checklist choices are kept in memory only. They are not uploaded. Diagnostic and speed-test results are not written to LocalStorage and clear on refresh, with one product exception: the click counter may keep counter names, totals and step settings in this browser only (see below).
What copying includes
The optional summary contains aggregate counts, selected button, methodology version and an optional environment label you write. It excludes coordinates, raw timestamps, session IDs and your complete user-agent string.
Site analytics (GA4)
This site loads Google Analytics 4 (gtag.js) to record basic traffic signals such as page views, approximate location derived by Google, device/browser category, and referral source. Named aggregate tool-usage events may also be recorded so we can measure whether tools are actually used. Those events use a small fixed vocabulary (for example tool_started, tool_milestone, tool_completed, tool_reset, tool_result_copied, tool_related_opened, tool_interrupted) with enum parameters such as which tool, which milestone, which test mode or duration bucket, a coarse outcome label, or a related-tool target. Each milestone is sent at most once per in-page test session. There is no cookie or analytics consent banner for this path. GA4 does not receive raw mouse or keyboard events, click coordinates, test timelines, CPS run totals, polling-rate samples, environment labels, change text, free-text fields, or optional notes you type into tools. Google may set its own cookies or identifiers under Google’s Privacy Policy.
Optional guide analytics
Separately from GA4, if an operator configures a guide analytics endpoint, the troubleshooting guide shows a per-visit opt-in control. With your consent, it sends only anonymous guide events such as a step ID, entry point, or selected outcome. It never sends raw input events, coordinates, device identifiers, browser fingerprints, environment text, change text, or optional notes. Consent is kept in memory and resets when you refresh.
Double-click speed test
The double-click speed test measures the time between two intentional clicks on a test target. Click intervals, recognition status and attempt history are kept in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. The page cannot read your operating system's double-click setting or identify your mouse model.
Keyboard tester
The keyboard tester records which key positions the browser reports while the test area has focus. Pressed and tested key sets, last-key details and coverage counters stay in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. The page does not log a full keystroke transcript for export and cannot read switch contacts, firmware or your keyboard model.
Keyboard double click test
The keyboard double click test records keyboard events while the test area has focus. Raw key events, key codes, timestamps and the event timeline are kept in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. The page cannot read switch contacts, firmware debounce or identify your keyboard model.
Keyboard ghosting test
The keyboard ghosting test records which simultaneous key positions the browser reports while a run is active. Held-key sets, preset comparisons, maximum simultaneous counts and short local combination summaries stay in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. The page cannot certify NKRO, read the key matrix, or identify your keyboard model.
CPS / click speed test
The CPS test (click speed test) counts intentional mouse clicks during a timed run. Total clicks, per-second buckets, run history and CPS results are kept in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. The page cannot detect autoclickers, measure input latency or polling rate, or identify your mouse model.
Click counter
The click counter keeps running totals you enter with the Count control (pointer, or Space/Enter while that control is focused). Counter names, totals and step settings may be saved in this browser on this device via LocalStorage so you can return later. They are not uploaded to our servers, not synced to an account, and not shared across devices. Undo history stays in page memory and clears on refresh. Clearing this site's stored data, using another browser or profile, or some private-browsing modes can remove saved counters. Aggregate analytics may record the tool name and coarse milestones (for example first count or multi-counter use); names and totals are not included.
Spacebar clicker
The spacebar clicker counts trusted Space key presses while the test area has focus, in unlimited counter mode or a timed speed run. Press totals, timed averages, per-second buckets, recent finished runs and best scores stay in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. Automatic key-repeat while Space is held is ignored. The page cannot read switch contacts, firmware or identify your keyboard model.
Jitter click test
The jitter click test counts trusted left mouse clicks during a short timed run while you attempt jitter clicking. Total clicks, average CPS, peak rolling 1-second CPS, click intervals, rhythm variation, per-second pace and recent run history stay in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. The page cannot verify physical technique, detect autoclickers, measure input latency or polling rate, or identify your mouse model.
Butterfly click test
The butterfly click test counts trusted left mouse clicks during a short timed run while you attempt two-finger butterfly clicking on the same button. Total clicks, average CPS, peak rolling 1-second CPS, click intervals, rhythm variation, per-second pace and recent run history stay in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. The page cannot verify finger count or physical technique, detect autoclickers, measure input latency or polling rate, or identify your mouse model.
Drag click test
The drag click test counts trusted left-button mouse pointerdown events during a timed run while you attempt drag clicking. Total presses, average CPS, peak rolling 1-second CPS, press intervals and recent run history stay in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. The page cannot verify physical technique, detect autoclickers, measure input latency or polling rate, or identify your mouse model.
Right click CPS test
The right click CPS test counts intentional right mouse-button clicks during a timed run. Total right clicks, per-second buckets, run history, optional pace labels and CPS results are kept in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. The page cannot detect autoclickers, measure input latency or polling rate, or identify your mouse model.
Mouse test
The mouse test records which buttons and scroll directions the browser observes. Channel status, hit counts, a short input timeline and lightweight double-click notes stay in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. The page cannot identify your mouse model, measure polling rate, or perform electrical diagnosis.
Mouse DPI test
The mouse DPI test accumulates movementX/Y totals only while Pointer Lock is active. Physical distance, optional known DPI, pass totals, same-mode medians and variation stay in page memory, with no LocalStorage or backend upload. Refreshing clears them. No raw movement sequence or device fingerprint is sent. Aggregate analytics may record the tool name, requested capture mode (raw-requested or OS-adjusted), first valid pass, completion of three same-mode valid passes, reset, interruption and related-tool navigation. Distances, entered DPI values and measured results are not included.
Mouse polling rate test
The mouse polling rate test counts trusted pointer-move events over the test pad to estimate effective report rate in Hz. Live rates, timed-run totals, stability samples and distribution buckets stay in page memory only. They are not uploaded, stored in LocalStorage or retained across a refresh. The page cannot read USB descriptors, identify your mouse model, or certify factory polling rate.