This is a static site with no backend and no contact form, so email is the only channel — which also means nothing you send passes through this website at all.
Email: rlaejrtn16@gmail.com
What gets answered first
The site is maintained by one person alongside other work, so replies usually take a few business days and sometimes longer. Two categories jump the queue, because both are defects:
- A number that is wrong. Any figure in any table on this site is generated by the same code that scores your run and is checked cell by cell in an automated test suite. If one is nonetheless wrong, that is a real bug and it will be fixed and re-verified.
- A click that was not counted, or counted twice. That is the one thing this tool exists to do correctly, so a reproducible miscount matters more than any feature request.
Reporting a miscount usefully
Clicking speed makes bug reports hard, because "it felt wrong" is not reproducible. The way to make a report actionable is to run a deliberate, countable test rather than a fast one:
- Pick the 5-second test and tap exactly twenty times at about four per second, counting out loud.
- Write down what the counter said. Repeat the run three times.
- Include your browser and its version, your operating system, and whether the input was a mouse, a trackpad, a touchscreen or the spacebar.
- Say whether the same thing happens in a second browser. That single line separates a bug in this site from something happening in your system or your hardware.
A count that is consistently higher than your deliberate presses is usually a switch registering twice rather than a scoring bug — but it is worth reporting either way, because if the tool is double-counting a pointer event on some device, that is exactly the kind of thing one report can surface and nobody else would notice.
Reporting a wrong number
Every figure printed in a table on this site comes out of the same functions that score your run, and each cell has an assertion attached to it in the test suite. That makes a wrong number unlikely, and it also makes one easy to fix once it is pointed out — the correction goes into the assertion first, and the suite runs as a build step, so it then either passes or fails the build. If you spot one, the useful report is the page it appeared on, the row and column, the figure shown and the figure you believe is right. Working out the arithmetic in the message is welcome but not required.
The same goes for wording as much as for arithmetic. If a sentence on this site reads as more certain than the evidence behind it — a claim about what players can do, about what is safe for your hands, or about how a game handles input — that is worth reporting too. The rule this site tries to hold to is that anything not derived by arithmetic should be labelled as what it is, and where that slips the sentence should be corrected.
Embedding and reuse
The copy-paste embed snippet on the main page is free to use on any site, with no attribution required and no permission needed — if it is useful to your wiki, forum or server page, take it. There is no need to email about it. Do get in touch if the embed misbehaves inside a particular layout, since that is something that cannot be tested from here.
Questions this address cannot help with
Which mouse to buy, whether a particular technique is worth learning, and how to get faster are all outside what an email exchange can usefully do — the honest answer is that this site measures a number and does not coach. Anything about pain, strain or injury needs a qualified professional. A website that counts button presses cannot help you there, and that is not modesty — it is the limit of what anyone here is in a position to say.
Server rules and game mechanics are also outside scope. Whether a technique is allowed where you play, and whether a higher click rate does anything in a game that gates attacks behind a cooldown, are questions for that game's own documentation and community.
Before writing
Most questions about how the measurement works are already answered on the about page — what counts as a click, how the timing window is defined, and what the tool cannot see. Data handling and advertising cookies are covered on the privacy page. And the per-length questions — why a one-second score is always a whole number, why a fast start costs so little over ten seconds, what a pause costs across a hundred — are answered in the FAQ on each of those pages.