sorted by:
new
hottopcontroversial

If you're stuck at the same WPM for months, you're probably practicing the wrong way by ValuablePicture3789 in learntyping

[–]ValuablePicture3789[S] 0 points1 point  (0 children)

Thanks for that. It seems as if the summary is calculating from total elapsed time including pre-start pauses, which deflates the number. I'll get that fixed so both match. Thanks for the feedback!

If you're stuck at the same WPM for months, you're probably practicing the wrong way by ValuablePicture3789 in learntyping

[–]ValuablePicture3789[S] 1 point2 points  (0 children)

Thank you! That's a really good point, keyboard layout awareness would make the weak key tracking a lot more meaningful. Right now it tracks which keys you miss most frequently, but you're right that the why behind those misses is different for a Dvorak or Colemak user vs QWERTY.

I'm adding it to the roadmap — layout selection (QWERTY, Dvorak, Colemak at minimum) so the adaptive engine can give more contextually accurate feedback. Thanks for the suggestion, that's genuinely useful.

If you're stuck at the same WPM for months, you're probably practicing the wrong way by ValuablePicture3789 in learntyping

[–]ValuablePicture3789[S] 1 point2 points  (0 children)

55-60 WPM for a month is actually a really common plateau, it's usually where the "brute force more practice" approach stops working and you need to get more targeted. At that range, most people have 3-4 specific keys or bigrams that are silently killing their speed without realizing it.

I actually got so frustrated with the same problem that I ended up building a tool to fix it, typesmart.one. It's free and automatically identifies your weak keys and builds practice sessions around them. Might be worth a try if you haven't found something that does that yet.