Word Counter / Text Analyzer

// HOW TO USE

1. 01Paste any text — counts, lengths, and timings update live.
2. 02Reading time uses ~200 wpm; speaking time uses ~150 wpm. Sentences are detected by ., !, and ? punctuation.
3. 03The top-words list filters common stop words like the, a, of, in, and so you see meaningful frequency.

// WHEN TO USE

Use this when you need to verify that text content in a test fixture, UI label, or API field falls within specified length constraints. Paste copy from a CMS, localisation file, or content field and immediately see character count, word count, and estimated reading time. Also useful for checking that generated lorem ipsum or test data text is the right length before seeding it into a database or fixture.

// WHAT BUGS THIS FINDS

• Character limit boundary not tested

  A 140-character bio field looks correct at 100 characters but silently truncates at 141 — paste text at 139, 140, and 141 characters and confirm the application handles each boundary correctly.

• Word count vs character count mismatch

  An application that enforces word-count limits (not character limits) silently accepts a one-word string of 500 characters — verify whether the constraint is on words or characters before writing the boundary test.

• Reading time exceeds spec

  A user story specifies 'under 3 minutes to read' — paste the content and confirm the estimated reading time before it goes to UAT review, rather than measuring manually.

• Stop word inclusion skews keyword frequency

  A search feature indexes the top words from a description field — the top-words list (filtered for stop words) shows what the indexer treats as keywords, revealing whether the copy is optimised correctly.

// QA USE CASES