Contact
Bugs, ideas, and everything else
Home Row is small and independently run, so email is the fastest way to reach us. We read everything, even if a reply takes a day or two.
Before you write
Most questions are already answered in the FAQ, including how WPM and accuracy are calculated, what the heatmap shows, which keyboard shortcuts exist, and what is saved on your device. If a score looks different from what you expected, the guides explain what affects it, such as test length, mode, and fatigue.
What to include in a bug report
- Your browser and device (for example, Safari on an iPhone, or Chrome on Windows)
- The test length and mode you were using
- What you expected to happen and what happened instead
- A screenshot, if it helps show the problem
Home Row never receives what you type, so for a scoring problem it also helps to say roughly what you typed and how the result looked.
Bug report or feature request
If the WPM or accuracy looked wrong, let us know what you typed and roughly how long the test ran — it helps track things down fast.
Email a bug reportGeneral question
Anything else — how the scoring works, a licensing question, press — goes to the same inbox.
Send an emailBefore writing in, the FAQ answers most common questions about WPM, accuracy, and how the test works.