Skip to content
keysprint

Contact

Send a message

Bug reports, incorrect scores, wording suggestions and general feedback are all welcome. keysprint is a small project run by one person, and every message is read.

How to reach us

keysprint is built as a static site with no server behind it, so there is no inbox for a contact form to post to. Instead, the button below opens your own email application with the address and a suggested subject already filled in. Nothing is sent until you press send in your mail app.

Email keysprint

Or copy the address into your mail application:hello@keysprint.onrender.com

What to include

A short message is fine. If you are reporting something specific, these three details make it much faster to find:

  • The page you were on. For example/typing-test/1-minute/.
  • What you did and what happened instead. "I pressed the left shift key and the character was still typed as lowercase" is a complete report. "It is broken" is not.
  • Your browser and device. Whether the problem happens on a desktop keyboard or a phone keyboard, and which one it happens on, usually points straight at the cause.

What we can help with

Scores that look wrong
Yes, please write. The scoring code is in a single module and is covered by unit tests, so a genuine error is worth finding. Include the results panel figures.
Something on the page that is confusing
Very welcome. The site was written by one person, and the places where a page is unclear are usually the places where the writer was thinking about something specific that other people do not.
Typing advice
Use the learn typing guide and the lesson stages first. If something is missing from them, say so.
Requests for features
Read, but not always acted on. keysprint deliberately has no accounts, no leaderboard and no progress tracking across devices, so the feature list is short on purpose rather than by accident.

Response time

Most messages get a reply within a few days, and longer ones sometimes take a week or two. keysprint is maintained in the gaps around other work, so a slow reply is more likely to mean a quiet week than a forgotten message.

Other things worth reading

  • About keysprint — how the site works and how the numbers are calculated.
  • Privacy policy— what is stored, where, and what is not collected.
  • Terms of use — the short version of what you can and cannot do with the site.

Frequently asked questions

Questions about contacting keysprint.

Why is there no contact form?
Because keysprint is a static site with no application server. A form would have to post to a backend that does not exist, and a form that silently fails is worse than no form at all. The link above opens your own email application with the address and subject already filled in, which always works.
I think my score is wrong. What should I do?
Please write and include the test length, the text type and the figures from the results panel. The scoring code is small and centralised, so a genuine bug in it is worth finding, and the unit tests that cover it will be extended when one turns up.
Can I request a specific passage or topic?
Possibly. The corpus is deliberately plain so it exercises the keyboard rather than the reader, which rules out most specific requests, but suggestions about the range of vocabulary or the mix of sentence lengths are welcome.
Do you answer every message?
Most of them. Keysprint is a small project maintained in spare time, so replies can take a few days, and long messages about typing theory may get a shorter answer than a precise bug report.
Can I use keysprint in my own project or article?
Link to it freely. The passages in the test are original to keysprint, so quoting a short passage in a review or a screenshot of the results panel is fine as well. The terms of use page sets out the details.