A keyboard won’t fix bad technique, but for someone who already types well, the wrong keyboard can genuinely cap their speed and comfort. Here’s what actually matters when choosing one.

Key travel and actuation

Key travel is how far a key moves before it registers, and actuation force is how hard you need to press. Shorter travel and lighter actuation generally favor speed, since fingers spend less time per keystroke, but very light keys can also increase accidental presses if your typing is heavy-handed.

Mechanical switches, by type

  • Linear switches (like Cherry MX Red) move smoothly with no bump, generally favored for speed since there’s less resistance mid-press.
  • Tactile switches (like Cherry MX Brown) have a small bump partway down, giving physical feedback that helps some typists confirm a keystroke registered without needing to bottom out the key.
  • Clicky switches (like Cherry MX Blue) add an audible click on top of the tactile bump, which some people find helps rhythm, though it’s the loudest option by far.

Membrane keyboards aren’t automatically worse

Most laptops and budget keyboards use membrane or scissor-switch designs. They’re generally mushier than mechanical switches, but a good scissor-switch laptop keyboard can still support high WPM for someone with solid technique. The keyboard matters less than most people assume until you’re already typing consistently above 80-90 WPM.

Layout and size

A cramped or unusually shaped keyboard, common on some ultra-compact or gaming boards, can slow down anyone used to a standard full-size or tenkeyless layout. If speed matters more to you than saving desk space, a standard layout is usually the safer choice.

Test your own speed on your own setup

Rather than assuming a new keyboard will help, it’s worth measuring your current typing speed before and after switching, since the difference is often smaller than marketing around “gaming” or “typing” keyboards suggests.

This comes up constantly in typing communities: does switching from a membrane keyboard to a mechanical one actually raise your WPM, or does it just feel different?

The honest answer: mostly feel, some speed

For someone with solid touch-typing technique, the difference between a good membrane keyboard and a good mechanical one is usually a few WPM at most, not a dramatic jump. The bigger factor is almost always technique, practice consistency, and familiarity with the specific keyboard you’re using, mechanical or not.

Where mechanical keyboards do genuinely help

Mechanical switches tend to have more consistent actuation across the entire keyboard, since every key uses the same physical switch. Cheap membrane keyboards can have inconsistent feel between keys, especially after wear, which can introduce small errors that a consistent mechanical board avoids.

Where the myth overstates things

Marketing around “gaming” and “typing” mechanical keyboards often implies a dramatic speed boost, but competitive typists have posted extremely high WPM scores on both mechanical and quality laptop keyboards. The switch type matters far less than raw practice hours at the top end of typing speed.

Familiarity beats switch type

Switching keyboards, even to an objectively “better” mechanical one, often temporarily lowers speed for a week or two while your fingers adjust to new travel distance and actuation force. If you’re preparing for something time-sensitive, like a job interview typing test, it’s usually safer to practice on whatever keyboard you’ll actually use for it.

Test it yourself

Rather than relying on general claims, run a few timed tests on your current keyboard and again after switching, using the same test mode and duration each time, to see what the real difference looks like for your own hands.

Typing speed rarely gets treated as a real academic skill, but for students it quietly affects note-taking, essay writing, and timed exams more than most people realize.

Note-taking in real time

A lecture moves at whatever pace the instructor sets, not the student’s pace. A student typing at 25 WPM is constantly choosing what to leave out, while one typing at 50-60 WPM can capture far more of what’s actually said, including the small asides and clarifications that often matter for understanding a topic later.

Essay and assignment writing

Typing speed doesn’t just save time, it changes how writing feels. When getting words onto the page is slow and effortful, there’s a real cost to stopping and rewriting a sentence, which pushes some students toward keeping weaker first drafts rather than editing. Faster typing lowers the friction of revising, which tends to produce better writing, not just faster writing.

Timed exams

Many exams, especially essay-based ones, are timed tightly enough that typing speed genuinely affects the score, independent of how well a student knows the material. A student who thinks quickly but types slowly can run out of time before finishing an answer they clearly understood.

Building the habit early

Typing speed is easiest to build before it’s urgently needed, rather than during exam season under pressure. A short daily habit, even five to ten minutes, using Time or Words mode, compounds over a school term far better than occasional long sessions.

Accuracy matters as much as speed here

A fast typist who makes constant errors ends up spending time fixing mistakes mid-exam, which erases the speed advantage. Practicing with an eye on accuracy percentage, not just the WPM number, builds a skill that actually holds up under exam pressure.

Typing is one of those skills kids increasingly need for school long before they’re taught it formally. A little structure at home goes a long way, without needing to turn it into a big project.

What age to start

Most children can start learning basic finger placement around age 7 or 8, once their hands are large enough to comfortably reach across a keyboard and they can follow simple instructions about which finger goes where. Younger than that, it’s usually more frustrating than useful.

Keep sessions short

Ten to fifteen minutes is plenty for a child’s typing practice session. Longer sessions tend to produce frustration and bad habits, like reverting to two-finger typing just to get through it, rather than actual skill building.

Make the home row stick first

Before worrying about speed at all, focus on getting a child comfortable resting their fingers on A-S-D-F and J-K-L-semicolon without thinking about it. Games and typing apps aimed at kids often built around this exact idea work well here, since the repetition matters more than the specific tool used.

Use Zen mode for low-pressure practice

Timed tests can feel stressful for a child still building basic confidence. Zen mode, which has no timer at all, is a gentler way for kids to practice typing without the pressure of a countdown, especially in the early weeks.

Praise accuracy before speed

Kids naturally want to go fast, but early speed usually comes at the cost of bad finger habits that are hard to undo later. Praising a slow, accurate line of typing over a fast, sloppy one sets a better foundation, even if it feels like it’s moving slower in the moment.

A lot of admin, data entry, customer support, and transcription roles still ask candidates to complete a timed typing test as part of the hiring process. If you’ve got one coming up, here’s what’s actually being measured and how to walk in prepared.

What employers usually require

Requirements vary by role, but general office and admin positions commonly ask for 40 to 50 WPM. Data entry and transcription roles often set the bar higher, sometimes 60 to 70 WPM, since the entire job is built around typing speed. Executive assistant and legal secretary roles frequently want both a speed minimum and a high accuracy threshold, often 95% or above, since transcription errors in that kind of work carry real consequences.

Accuracy usually matters more than the number suggests

Most employer tests calculate a net WPM that subtracts errors, so a fast test full of typos scores lower than a slightly slower, clean one. If you’re deciding how to spend limited practice time before an interview, practicing at 90%+ accuracy is usually worth more than chasing five extra WPM with sloppy form.

Practice with realistic conditions

Employer tests almost always include punctuation, capital letters, and sometimes numbers, since that’s what real workplace writing looks like. Practicing exclusively on plain lowercase words will leave you underprepared. Turning on punctuation and number modes during practice gets you much closer to what the actual test will feel like.

Know your number before you walk in

Nerves during a timed test in front of an employer often knock a few WPM off your usual pace. If you’ve never actually measured your typing speed, the interview itself is a bad place to find out for the first time. Running a few practice tests beforehand, in Time mode with a 60-second duration to match how most employer tests are structured, gives you a realistic number and takes some of the pressure off on the day.

Build a short daily habit before the interview

A week of five to ten minutes a day, focused on accuracy first and speed second, moves the needle more than one long cram session the night before. Typing speed responds to consistency, not intensity.

Programmers type differently than most people. Code leans heavily on symbols, brackets, and punctuation that barely show up in normal writing, and standard typing tests built around plain words don’t train for any of it.

Why plain-word typing tests don’t fully transfer

A test made of common English words trains letter-to-letter movement, which does help overall speed and finger memory. But code involves constant switching between letters and symbols like brackets, parentheses, and operators, plus frequent use of the shift key for capitals and special characters. That switching is its own skill, separate from raw letter speed.

Turn on punctuation and numbers deliberately

The closest a general typing test gets to code-like typing is running with punctuation and number modes turned on together. This forces constant hand repositioning between the letter rows, the number row, and shifted symbols, which is a decent proxy for the kind of movement code actually requires.

Use Custom Text mode with your own code comments

One of the more direct ways to practice is pasting your own code comments, commit messages, or documentation notes into Custom Text mode and typing them directly. This builds speed on your actual vocabulary and habits rather than generic text, and it’s a realistic way to warm up before a coding session.

Don’t ignore your number and symbol row

A lot of programmers develop a habit of glancing down specifically for numbers and symbols, even if they’ve touch typed letters for years. If this is you, it’s worth deliberately practicing the top row and its shifted characters the same way you’d practice any other weak spot, since it quietly costs more time than it seems to.

Track consistency, not just peak speed

Code involves a lot of short bursts followed by pauses to think, so a smooth, steady consistency score during a typing test is arguably more relevant to programming than a high top-end WPM achieved on an easy passage.

Touch typing is just typing without looking down at the keyboard, using memory and muscle habit instead of your eyes to find each key. It sounds like a small thing, but it’s the single biggest jump in typing speed most people ever make, bigger than any amount of practice on random word tests.

Start with home row

Put your left fingers on A, S, D, F and your right fingers on J, K, L, semicolon. Most keyboards have small raised bumps on F and J so you can find this position without looking. Every other key on the keyboard is reached by moving one finger away from home row and immediately returning it. That return trip is the habit you’re building.

Assign every key to a specific finger

This is the part people skip, and it’s why they plateau. Each finger owns a small column of keys, not just the letter closest to it. Your left index finger, for example, covers both F and G, plus R and T above it, and V and B below it. Looking up a standard finger chart once and sticking to it matters more than any app or game.

Expect it to feel slower at first

This is the part that makes people quit. For the first week or two, typing without looking is genuinely slower than your old hunt-and-peck habit. That’s normal. You’re replacing a fast bad habit with a slow good one, and the good one only gets fast after it becomes automatic, usually somewhere between two and four weeks of regular use.

Practice on real tests, not just drills

Finger-placement drills teach the position, but a real typing test is what builds speed under natural conditions, since real writing doesn’t move through the keyboard in a neat predictable order. Running a Time or Words mode test daily, even for five minutes, does more for actual typing speed than an hour of repetitive single-key drills once you know the basic layout.

A realistic timeline

Most people can stop looking at the keyboard entirely within one to two weeks of deliberate practice. Getting back to their old hunt-and-peck speed, but now touch typing, usually takes another two to three weeks after that. Surpassing their old speed is where things get interesting, and that’s when it’s worth tracking your WPM properly instead of guessing.

Typing speed isn’t really about how fast your fingers can physically move. Most people who plateau at a certain WPM are being held back by one of a few specific habits, not by a hard ceiling on their ability.

1. Looking down to check yourself

Even people who technically know touch typing often glance down after a mistake, or before a word they’re unsure of. Every glance costs a fraction of a second finding your place again afterward. If this is you, cover the keys with a cloth for a week of practice. It feels uncomfortable but breaks the habit fast.

2. Fixing errors mid-word instead of finishing first

Backspacing the instant you notice a typo interrupts your rhythm more than the typo itself does. Faster typists tend to finish the word or thought, then correct, rather than stopping mid-flow. This is partly why a consistency score is more revealing than raw WPM, it shows how much these interruptions are actually costing you.

3. Using only two or three fingers per hand

A lot of self-taught typists develop a modified hunt-and-peck that’s fast but caps out lower than proper touch typing, because two fingers are doing the work of ten. If you’re not sure whether this is you, try typing a sentence without looking at your hands. If your fingers wander far from home row, this is worth fixing.

4. Tensed shoulders and wrists

Physical tension slows down finger movement in a way that’s easy to miss because it builds up gradually during a session. Wrists should float slightly above the keyboard, not rest heavily on it, and shoulders should stay down, not creep up toward your ears as you concentrate.

5. Practicing only easy text

Plain lowercase words without punctuation are the easiest possible typing, and they don’t prepare you for real writing. Turning on punctuation and number modes occasionally forces your hands to handle capital letters, shifted symbols, and digit rows, which is where a lot of real-world slowdown actually happens.

Fixing even one or two of these usually moves the needle more than weeks of unfocused practice. Run a quick test now and see which of these shows up in your own typing.

If your wrists or hands ache after typing sessions, it’s rarely the typing itself causing the problem. It’s almost always posture, desk height, or keyboard position, and all three are fixable without buying anything expensive.

Check your wrist angle first

Wrists should stay roughly straight, not bent upward, downward, or sideways toward your pinky. A bent wrist while typing compresses the same tunnel of nerves and tendons that repetitive strain injuries come from. If your keyboard sits higher than your relaxed elbow height, your wrists are almost certainly bending upward without you noticing.

Elbows at roughly 90 degrees

Chair height matters more than most people think. If your desk forces your elbows above or well below a right angle, that tension travels down into your wrists over a long session. Adjusting chair height, or adding a cushion, is often a bigger fix than any keyboard purchase.

Stop resting your wrists on the desk while typing

Wrist rests are meant for pausing, not for typing with your wrists planted while your fingers do all the reaching. Typing with wrists resting forces your fingers to stretch further for each key, which adds strain across a long session. Let your wrists hover slightly, supported mainly by your forearms and shoulders.

Take breaks based on time, not pain

By the time you feel discomfort, some strain has already built up. A short break, even 30 seconds of shaking out your hands, every 20 to 30 minutes during long typing sessions prevents the buildup rather than just responding to it.

Speed and posture aren’t in conflict

A common myth is that proper ergonomic form slows you down. In practice, tension and awkward angles are what cost speed over a long session, since fatigue degrades accuracy well before it degrades raw finger speed. Comfortable form is faster form once a session runs longer than a few minutes, which is part of why consistency matters as much as your peak speed.

If you’ve searched “monkey typing test” and landed here a bit confused about where monkeys come into typing speed at all, you’re not alone. The name has nothing to do with actual monkeys. It comes from a much older idea.

Where the “monkey” part actually comes from

There’s a famous thought experiment called the infinite monkey theorem. It goes like this: if you sat a monkey at a keyboard and let it type completely at random, forever, it would eventually produce every play Shakespeare ever wrote, purely by chance. Not because the monkey learned anything, just because infinite random attempts eventually stumble onto every possible sequence.

It’s a math and probability idea, not a real experiment (nobody is actually testing this on monkeys). But the image stuck. Over the years it became a kind of shorthand joke for “typing without any real skill or intention behind it”, and that phrase eventually got attached to online typing speed tools. People search “monkey typing test” the same way they’d search for any fast-paced typing speed test, and tools built around this theme picked up the name.

So what is a “monkey typing test” today?

In practice, when someone says “monkey typing test” they almost always mean a specific style of typing speed test: clean, minimal, no ads cluttering the screen, random words instead of long paragraphs, and a live WPM counter while you type. It’s become the default format most people picture when they think of testing their typing speed online.

The core mechanics are the same wherever you find them:

  • A stream of words appears on screen, usually pulled from a common-word list rather than a fixed sentence.
  • You type them as accurately and quickly as you can.
  • Your speed gets measured in WPM (words per minute), using the standard formula: correct characters typed, divided by 5, divided by the minutes elapsed.
  • Accuracy gets tracked alongside speed, since a fast test full of mistakes isn’t actually that useful.

Running one on MonkeyTypeHub

MonkeyTypeHub follows this exact format, plus a few things we thought were missing from the usual version:

  • A consistency score, so you can see whether your pace held steady through the whole test or fell apart halfway through.
  • A results graph showing exactly where your speed dipped, rather than just handing you one final number.
  • Multiple modes: Time, Words, Quote, Zen, and Custom Text if you want to practice on your own writing instead of random words.
  • A leaderboard if you want to see how your result stacks up, with just a name, no account needed.

Try it

You don’t need to know anything about theorems or monkeys to use it. Head to the MonkeyTypeHub homepage, pick a mode, and start typing. If you want to see how the format compares to other well-known versions, we also wrote a Monkey Type vs MonkeyTypeHub comparison.