TypeVelo.
← All tests

Mixed-Content Typing Test

Net 0 wpmGross 0 wpmAcc 100%Time 120s
It is a mistake to suppose that the difficulty lies in the beginning of a thing; the beginning is easy enough, and pleasant besides, for nothing has yet gone wrong and everything is still possible. The wind had risen again in the night, and by morning the road was scattered with small branches and the loose grey dust that had lain undisturbed for a fortnight, so that the first carriage to pass left a track behind it as clear as writing. 48 91 07 23 65 84 10 39 52 76 18 90 0117 496 0592 0203 555 0134 0161 496 0000 0117 496 0592 0203 555 0134 0161 496 0000 48 91 07 23 65 84 10 39 52 76 18 90 300000 45000 1250 78 6 902 41500 337 12.50 340.75 8.09 1250.00 66.40 7.99 4820 71 9053 128 6644 30 5917 2286 1994 2003 2011 2018 2024 1987 1962 2030 4820 71 9053 128 6644 30 5917 2286 grep -rn 'total' ./src | sort | uniq -c > counts.txt type Result = { ok: true; value: string } | { ok: false }; func Total(rows []Row) int { total := 0; for _, r := range rows { total += r.N }; return total } const total = rows.reduce((sum, r) => sum + r.count, 0); def load(path): return [line.strip() for line in open(path)] for (let i = 0; i < items.length; i += 1) { render(items[i]); } some part of some may down many write new number she down did these would from like which people its an get so is an how many make and if word but how who her about little write that she then than he it more little are been only been one out but may up then be their then said but they them an he with word water his what and look time water more

QWERTY layout assumed. Backspace corrects; uncorrected errors count against net WPM.

This test's passage is built from four different pools stitched together: a stretch of continuous prose, then a run of number strings, then a fragment of code, then a stretch of common single words — always in that order, though the specific words, numbers, and code lines drawn from each pool are randomized every time you take it.

The join between each section is nothing more than a single space; there's no heading, no visual break, no warning that the type of text is about to change. One moment you're mid-sentence in a long piece of prose, and a beat later you're typing a phone-number-shaped string of digits with no letters in it at all.

What this measures isn't top speed in any one of the four styles — the Continuous Prose Typing Test, Numbers Typing Test, and Code Typing Test each already do that individually. This measures the moment of the switch itself: how much your pace dips right as one kind of text gives way to another, and how quickly it recovers.

How This Test Works

Each attempt divides its target length into four roughly equal segments and fills them, in order, from the prose pool, the numbers pool, the code pool, and the common-words pool, joining all four with plain spaces into one continuous passage. Because the sequence itself never changes — prose always leads, numbers always follows it, code always comes third, common words always close it out — a typist who takes this test repeatedly can learn roughly when a switch is coming, even though the exact content of each segment is different every time.

The common-words segment is worth calling out: unlike the prose, numbers, and code sections, which each carry their own real punctuation and capitalization, the common-words pool has none of either, so the passage's final stretch reads as a sudden run of plain, unmarked lowercase words right after a code fragment full of symbols — one of the sharpest contrasts in the whole test.

That number is worked out exactly as described on How WPM Is Actually Calculated, applied across the whole two-minute passage rather than broken out per segment, so the final figure blends all four styles into one result rather than reporting them separately.

Who It's For

This suits typists who want to test how well they handle unannounced context switches, which is closer to how typing works outside a controlled test — copying a document that includes a table of figures, a code snippet, and ordinary prose in the same file, for instance, rather than four separate documents each in one style.

It's a poor choice if you want a clean read of your best speed in any single style, since the constant switching will pull your overall number below what you'd score on any one of the four dedicated tests this one borrows from. Run Continuous Prose, Numbers, or Code individually first if that's what you're after.

The Order Never Changes, Even Though the Text Does

Prose leads, numbers follows, code comes third, and common words close out every single attempt — a fixed structure hiding behind passages that look different every time because the specific sentences, numbers, and code lines are drawn fresh from each pool on every attempt. Noticing this pattern doesn't make the test easier exactly, but it does mean you can anticipate roughly when the next switch is coming, which is a learnable skill this test rewards over repeated attempts.

Why the Numbers-to-Code Switch Is the Sharpest One

Moving from prose into numbers is a shift from letters to digits; moving from numbers into code adds a second shift on top of the first, since code brings back letters but now mixed heavily with symbols the numbers section never used at all — parentheses, semicolons, and equals signs appearing for the first time in the passage. That back-to-back double transition is where most typists lose the most time in this test.

What Recovering Quickly Actually Looks Like

A fast recovery after a switch doesn't mean typing the new section at full speed immediately — it means the slowdown lasts a word or two rather than a full sentence. Most people's first few characters after any switch are cautious regardless of skill level; what separates a strong result here is how fast that caution burns off once the new pattern is recognized.

Frequently Asked Questions

Does the order of prose, numbers, code, and words change between attempts?

No — that order is fixed for every attempt. What changes each time is the specific prose, numbers, and code drawn from each pool, not the sequence they appear in.

Why does my WPM drop right when the content type changes?

A moment of hesitation while your hands and eyes adjust to a new kind of text is normal and happens to nearly everyone; it's the size and length of that dip, not its existence, that varies between typists.

Is this test a fair way to compare my numbers-typing skill against someone else's?

Not directly — the Numbers Typing Test isolates that skill on its own for a full minute, while here it's only a quarter of a two-minute passage sandwiched between three other styles.

Should I expect a lower overall WPM here than on the individual tests?

Usually, yes, since the transitions cost time that a single-style passage never asks you to spend, on top of whatever your baseline speed is in each individual style.