Writing for the Web: Word Count, Reading Time and Why They Matter

"How long should it be?" is the question every writer asks, whether they're drafting a blog post, an email, a product description or an essay. Word count and reading time are the two simplest measures we have, and used well they're genuinely useful guides. Used badly, they turn into arbitrary targets that make writing worse. This guide explains what each really tells you and how to use them to write things people actually finish.

What reading time actually measures

Reading time is an estimate of how long a typical person takes to read your text, based on an average silent reading speed of around 200 words per minute. It's the "5 min read" label you see on articles. Its value isn't precision — people read at very different speeds — but expectation-setting. Telling a reader "this is a 4-minute read" helps them decide to start, and studies of on-site behaviour suggest a visible, honest reading time can improve how many people commit to reading.

Speaking time is a close cousin, running slower at roughly 130 words per minute, because we talk more slowly than we read silently. If you're writing a speech, a presentation script or a video voiceover, that's the number that matters — it tells you whether your talk fits its slot. Our reading time calculator gives you both.

Why word count matters (and when it doesn't)

Word count is a blunt but honest instrument. It tells you the size of what you've made, which matters for practical reasons: hitting a limit (a tweet, a meta description, an essay assignment), fitting a layout, or judging whether a piece is substantial enough to be worth publishing. Our word counter tracks it live as you type.

But word count is a measure of length, not quality, and confusing the two is the classic trap. A tight 400-word post that answers a question completely beats a padded 1,500-word one that buries the answer. Writing to a word count — stretching thin ideas to hit a number — produces exactly the kind of bloated, low-value content that both readers and search engines have learned to skip. Length should be a result of covering a topic properly, not a target you inflate towards.

So how long should it be?

The honest answer is "as long as it needs to be, and no longer." A few practical anchors:

• Answer-style content (how do I do X?): as short as fully answers the question. Often 300–800 words.
• In-depth guides and explainers: usually 800–2,000 words, because covering a topic well genuinely takes that space. Depth earns the length.
• Emails and messages: shorter than you think. If it's over a screen, ask what can be cut.
• Meta descriptions and titles: strict limits (roughly 150–160 characters for descriptions), so word and character counting is essential.

The useful mindset: decide what the piece must accomplish, write until it does, then cut everything that doesn't serve that goal.

Readability beats raw length

Whether people finish your writing depends less on how many words there are and more on how easy they are to move through. On the web especially, readers skim. A few habits make a huge difference:

• Short paragraphs. Walls of text scare readers off. Two to four sentences per paragraph keeps momentum.
• Descriptive subheadings. They let skimmers navigate and find the part they came for — which, ironically, makes them more likely to read the whole thing.
• Front-load the point. Put the answer or the key idea early. Don't make readers dig for it.
• Vary sentence length. A run of long sentences tires the reader; a short one lands a point.
• Lists for parallel items. When you're enumerating things, a list is easier to scan than a dense paragraph.

A simple editing pass

Once a draft is done, run it through a quick check. Read it at full length and ask: does the reading time match the value? A "10-minute read" had better deliver ten minutes of worth. Then cut ruthlessly — most first drafts shrink by 10–20% with no loss of meaning, and every removed filler word makes the rest hit harder. If you're wrangling lists of items, keywords or references, a line sorter can help you organise and de-duplicate before you finalise.

Length, SEO and the reader's trust

There's a persistent myth that longer articles always rank better on search engines. What's actually true is subtler: in-depth content tends to rank well because thoroughly answering a question naturally takes more words — not because length itself is rewarded. Search engines have spent years getting better at spotting padding, and readers spot it instantly. A page that makes someone hit the back button after ten seconds sends a worse signal than a short page that answers cleanly and lets them leave satisfied. So write for the person first: cover the topic completely, respect their time, and let the word count fall where it may. Do that consistently and both the readers and the rankings tend to follow.

Key takeaways

• Reading time (≈200 wpm) sets reader expectations; speaking time (≈130 wpm) fits talks to a slot.
• Word count measures length, not quality — never inflate a piece to hit a number.
• Write until the topic is properly covered, then cut everything that doesn't serve the goal.
• Readability — short paragraphs, clear subheadings, front-loaded points — matters more than raw length.