HomeToolsProduct designTooltip reading time calculator
Reading time calculator for tooltips and tours
Paste the text of each tooltip, tour step or modal, one per paragraph. The calculator counts words and characters, estimates reading time at a realistic speed for the language, adds time to notice and click for the whole tour, flags steps that exceed the length guideline for the format and suggests where to split them.
—
Formula. Reading time = words ÷ words per minute × 60. Tour time = Σ reading time + steps × notice-and-click time. Limits are Clew’s editorial guideline for in-app UI copy, not a published standard.
Everything is calculated in your browser — nothing you enter is sent anywhere.
How to use it
- Paste the stepsPut each tooltip or tour step in its own paragraph, including its title and button label. Copy from your design file, spreadsheet or onboarding tool.
- Choose format and languageThe format sets the length guideline — a hover tooltip should be shorter than a modal. The language sets a default reading speed that you can change.
- Review the flagged stepsEach step shows words, characters and seconds against the guideline. Long and too-long steps get the reason and a split suggestion at sentence boundaries.
- Check the whole tourThe total adds reading and interaction time. If the tour is longer than five steps or a minute, move part of it into a checklist or a later tour.
How reading time is calculated
Reading time is the number of words divided by reading speed, measured in words per minute (wpm):
Default speeds come from the IReST study (International Reading Speed Texts, Trauzettel-Klosinski, Dietz et al., 2012), which measured adults reading standardized, equivalent texts in 17 languages: English 228 wpm, Spanish 218, Russian 184, Portuguese 181. IReST texts were read aloud; silent reading is somewhat faster (a 2019 meta-analysis by Brysbaert puts English non-fiction at about 238 wpm), but interface text is read in fragments and under distraction, so the IReST figures are a sensible conservative default. Words per minute differ between languages largely because word length differs — the same message takes fewer, longer words in Russian than in English. Indonesian, Filipino and Kazakh are not covered by IReST; the calculator uses 180, 180 and 165 wpm as estimates and says so.
Two caveats matter for UI text:
- People skim interfaces. A tooltip is read in fragments between actions, often on a small screen and while the user is thinking about their own task. Real reading is slower per word than in the lab, and much of the text is skipped — both reasons to write less, not to count on the average.
- Reading is not the whole interaction. Before reading, the user notices the hint and orients to the element it points at; after reading, they find and press a button. The "notice and click" field adds this per step to the total tour time; two seconds is a conservative default.
How long should a tooltip or tour step be
There is no official standard for tooltip length. The limits in this calculator are Clew's editorial guideline, based on how onboarding hints are used in product interfaces and aligned with our tooltip copy checker:
A step is marked Long when it exceeds a limit by up to 50 % and Too long beyond that. Words, characters and seconds are checked separately: long words in German or Russian can break the character limit while the word count looks fine, and a small bubble on mobile is limited by characters, not words.
Why short matters in onboarding
- Hints interrupt a task. The user came to do something; every second spent reading delays it. One idea per step keeps the interruption short.
- Long bubbles cover the interface. A 60-word tooltip hides the very element it explains, especially on laptops and phones.
- Long tours lose people. Each extra step is another chance to click "Skip". If the flow has more than five steps, move later steps into a checklist the user opens when ready, or show a second tour when they reach that feature.
How to shorten tour copy
- Start with the action. "Click New project to start" beats "In order to get started with your work, you can create a new project by clicking the button".
- One step, one idea. If a step has two sentences about different things, it is two steps — the split suggestion shows where the sentence boundaries are.
- Cut what the interface already says. Don't repeat the button label or describe what the user can see.
- Move details out. Explanations, edge cases and "you can change this later" belong in help docs linked from the step, not in the bubble.
- Use the button as copy. "Invite teammates" as a button label replaces a sentence telling the user to invite teammates.
- Check readability and tone. Plain words and active voice read faster; the readability checker shows long sentences and hard words.
Sources
- Trauzettel-Klosinski S., Dietz K., IReST Study Group. Standardized Assessment of Reading Performance: The New International Reading Speed Texts IReST. Investigative Ophthalmology & Visual Science, 53(9), 2012 — reading speeds for 17 languages.
- Brysbaert M. How many words do we read per minute? A review and meta-analysis of reading rate. Journal of Memory and Language, 109, 2019 — silent reading rates for non-fiction and fiction.
- Nielsen Norman Group. How Users Read on the Web; Tooltip Guidelines — scanning behavior and tooltip content.
- Clew. Length guideline for in-app onboarding copy (tooltips, tour steps, modals, checklists) — editorial guideline used by this calculator.
FAQ
How do you calculate reading time?
Divide the number of words by the reading speed in words per minute and multiply by 60 to get seconds. At 228 words per minute, the average for English, a 20-word tooltip takes about 5.3 seconds to read.
What is the average reading speed?
In the IReST study adults read standardized texts at about 228 words per minute in English, 218 in Spanish, 184 in Russian and 181 in Portuguese. Silent reading is a little faster: a 2019 meta-analysis by Brysbaert estimated about 238 wpm for English non-fiction.
How many words should a tooltip have?
Clew’s guideline is up to 25 words and 160 characters for a tooltip, and up to 35 words for a product tour step, including title and button text. That keeps reading time under 7–10 seconds. This is an editorial guideline, not a formal standard.
How many steps should a product tour have?
Our guideline is three to five steps. Longer tours are more likely to be skipped; move later steps into an onboarding checklist or show them as a separate tour when the user reaches the relevant feature.
Why is reading speed different for each language?
Mostly because words have different average lengths: languages with longer words fit the same meaning into fewer words, so words per minute is lower even when the information rate is similar. Set the speed to the language of the text you are checking.
Does the calculator count characters with spaces?
Yes. Characters are counted with single spaces between words, the way text appears in a tooltip; repeated spaces and line breaks count as one space.
More in Product design
- Color contrast checker
Does this text and background color pair pass WCAG AA or AAA?
- Accessible palette generator
How do I get an accessible color palette with contrast checked for every shade?
- Type scale & fluid type generator
Which font sizes make a consistent, fluid type scale?
- Tooltip copy checker
Is this tooltip short, clear and actionable enough?
- SUS calculator
What is the System Usability Scale score, and is the usability good?
- NASA-TLX calculator
How heavy did this task feel, and which kind of demand made it heavy?