JavaScript Typing Test
Type real JavaScript: arrow functions, objects, async code and template strings.
Loading coding passages...
JavaScript is punctuation in motion: arrow functions, chained calls, object literals and quotes, often several on one line. This test serves real JavaScript and scores every symbol, so you can see whether braces, quotes or semicolons are what slows you down.
What you will actually be typing
Two excerpts from the 10 JavaScript passages in this test, shown exactly as you type them. Press Enter at the end of each line and the next line’s indentation is filled in for you. Each passage runs to several thousand characters, more than anyone types in five minutes.
const profileEvents = [
{ id: 101, actor: 'Asha', type: 'draft', delta: 14, value: 33 },
{ id: 102, actor: 'Ravi', type: 'verified', delta: 21, value: 44 },
{ id: 103, actor: 'Mira', type: 'verified', delta: 28, value: 55 },
{ id: 104, actor: 'Noah', type: 'draft', delta: 35, value: 66 },
{ id: 105, actor: 'Isha', type: 'verified', delta: 42, value: 77 },
{ id: 106, actor: 'Kabir', type: 'verified', delta: 49, value: 88 },
];
function parseProfileEvent(event) {
return {
id: Number(event.id),
owner: String(event.actor).trim(),
status: event.type === 'verified' ? 'verified' : 'draft',const notificationTransitions = {
queued: ['sent', 'archived'],
sent: ['archived'],
archived: [],
};
function moveNotification(item, nextStatus) {
if (!notificationTransitions[item.status]?.includes(nextStatus)) throw new Error('Invalid transition');
return { ...item, status: nextStatus, updatedAt: new Date().toISOString() };
}
async function saveNotificationReview(api, rows) {Who this test is for
Front-end and Node.js developers, bootcamp students and anyone who writes JavaScript daily and feels their speed drop whenever a line turns into =>, (), {} and quotes in quick succession.
It is also a useful check before a live-coding interview, where nerves make symbol errors more likely and every correction is visible.
| Durations | 1, 2, 3 or 5 minutes |
|---|---|
| Passages | 10 JavaScript passages, 45,919 characters in all; choose one before you start |
| Difficulty | One level: every passage is real working code, not graded drills |
| What counts | Every character and line break must match the passage. Enter fills in the next line’s indentation; Tab inserts two spaces |
| Speed | Gross WPM = characters typed ÷ 5 ÷ minutes. Net WPM takes one word off per error |
| Accuracy | Overall accuracy, plus symbol accuracy: the share of brackets, quotes and operators typed correctly |
| Report card | Separate counts for symbol, bracket, quote, semicolon, whitespace and new-line mistakes |
The JavaScript symbol profile
Across 10 passages and 45,919 characters, JavaScript here runs at 16.9 symbols per 100 characters, among the highest on the site. Parentheses and quotes lead, followed by dots from chained calls and property access.
Names average 6.2 characters, in camelCase, so a capital letter mid-word is routine. Indentation is light, 3% of characters, because JavaScript blocks are delimited by braces, not whitespace.
| Symbol | Per 100 characters |
|---|---|
| ( parenthesis | 2.2 |
| ) parenthesis | 2.2 |
| ' single quote | 2.2 |
| . dot | 1.8 |
| ; semicolon | 1.2 |
| = equals | 1.1 |
| , comma | 1.1 |
| { brace | 1 |
The symbol runs you will type most
=> leads by a distance, from arrow functions. The next runs, ', and '); , are strings ending inside lists and calls. If one of these clusters is slow, the whole line is slow.
| Run | Per 1,000 characters |
|---|---|
=> | 5.9 |
', | 4.5 |
'); | 3.2 |
); | 3 |
|| | 2.9 |
(' | 1.3 |
How JavaScript compares with the other coding tests
| Measure | HTML & CSS | Java | JavaScript | Python | SQL | TypeScript |
|---|---|---|---|---|---|---|
| Symbols per 100 characters | 17.2 | 13.7 | 16.9 | 14.3 | 6.5 | 16.1 |
| Indentation, share of characters | 2.6% | 3.3% | 3% | 8.2% | 0.1% | 1.6% |
| Capital letters, share of characters | 2% | 4.4% | 2.4% | 0.5% | 22% | 4% |
| Average name length | 5.5 chars | 6.9 chars | 6.2 chars | 5.8 chars | 6.3 chars | 6.5 chars |
| Average line length | 37 chars | 39.1 chars | 36.6 chars | 40.3 chars | 32.6 chars | 53.4 chars |
Typing JavaScript: arrows, pairs and semicolons
The arrow is the signature JavaScript chord: an equals sign and a greater-than in a row, the second needing Shift. These passages contain 272 of them. Practise => as one movement with the right hand, because typing it as two separate decisions is where the hesitation comes from.
Brackets come in pairs, and many typists type the opener, the contents and only then think about the closer. A better habit is to know the closing sequence before you start the line: if you open ({ you will end with }). Bracket and quote mistakes are listed separately in the report card, so you can see whether this is your problem.
Semicolons appear in 44.1% of lines here. JavaScript can insert many of them for you automatically, as MDN documents, but the test is exact: if the passage shows a semicolon, type it. In real code, follow your team’s style; here, follow the passage.
Quotes are the other frequent symbol: single quotes for strings, backticks for template literals, and ${ } inside those. The backtick sits at the far top-left of the keyboard under the left little finger, and it is easy to hit the apostrophe instead.
Anatomy of one line
One guard line from the state-machine passage. Count the symbols: a negation, optional chaining with ?., three pairs of parentheses (two of them nested), square brackets and a quoted error message, then a closing semicolon.
if (!notificationTransitions[item.status]?.includes(nextStatus)) throw new Error('Invalid transition');| Characters | 105, of which 2 are indentation |
|---|---|
| Letters | 83 |
| Symbols | 15 |
| Spaces | 7 |
| Keys that need Shift | 12 |
Reading your JavaScript report card
Start with bracket errors. JavaScript lines often close two or three brackets at once, such as }); or ]), and a bracket error usually means the closing sequence came out in the wrong order. Then check quote errors: the passages use single quotes for strings and backticks for template literals, and the two are easy to swap when you are typing fast.
Semicolon errors are worth reading carefully. A missing semicolon at the end of a line is a habit issue; a semicolon where none belongs, for example after a closing brace of a function, is usually a sign of rushing. Whitespace errors are spaces inside a line, after commas or around operators; indentation is filled in when you press Enter.
Mistakes the report card will show most
- Typing = then > with a pause between, or hitting - for = in an arrow.
- Closing an object literal’s brace before the call’s parenthesis: }) and )} are both common, and only one is right.
- Typing an apostrophe where the passage has a backtick.
- Dropping the semicolon after a statement that ends in a closing brace.
The habits that apply to every kind of typing, such as accuracy before speed and short daily practice, are in how to type faster. For symbols on their own, use the symbol typing test.
A three-step practice plan
The aims below are our suggestions, not pass marks. The test itself has no pass mark; it reports your speed and accuracy and lets you judge the trend.
| Step | Run | Aim for |
|---|---|---|
| Warm up | 1 minute on the symbol typing test | => and paired brackets as single movements |
| Build | 2-minute JavaScript runs, rotating passages | Bracket and quote errors under 3 per run |
| Stretch | 5-minute JavaScript runs | Symbol accuracy of 95% or more |
Frequently asked questions
What does the JavaScript typing test include?
10 passages of JavaScript with functions, arrow callbacks, object literals, array methods, async code and template strings. Every character must match, including line breaks; the indentation after each Enter is filled in for you.
Do I have to type the semicolons?
Yes, wherever the passage shows one. JavaScript can insert many semicolons automatically, but this test compares your typing to the passage character for character, so a missing semicolon is an error.
What is symbol accuracy?
The share of symbols in the passage (brackets, quotes, operators, punctuation) that you typed correctly. It is reported separately from overall accuracy because JavaScript typists are usually much more accurate on letters than on symbols.
Is this useful before a coding interview?
It helps with the mechanical part: typing correct syntax under time pressure without stopping to fix brackets. Pair it with real problem practice; speed is never what an interview is judging.
Does the test include modern syntax like optional chaining?
Yes. The passages include optional chaining (?.), spread syntax, async and await, template literals and arrow functions, alongside classic loops and object literals.
Can I use this to practise for Node.js work?
Yes. Many passages are service-style code: parsing input, validating records, calling an API and building reports, which is as common on the server as in the browser.
Do the passages follow a particular style guide?
They use a consistent, common style: two-space indentation, single quotes for strings (never double quotes), backticks for template literals and semicolons at the end of statements. The test checks you against that style exactly.
Other coding typing tests
Sources
Conventions cited on this page come from the sources below. Every figure about the passages is measured from the passages themselves, and recalculated each time the site is built.
- Lexical grammar — Automatic semicolon insertionMDN Web Docs · link checked 20 Oct 2026