Word Pacer
Show Stats
Show Labels
Statistics
Words:
Sentences:
Paragraphs:
Average word length:
Minimum reader velocity:
Maximum reader velocity:
Average reader velocity:
# Paste your text in here In short, *Word Pacer* is a little web app designed to help you adjust the pacing in your writing. Whether it's fiction, essay, or poetry, the idea is that you can control how fast your audience reads (I call it **reader velocity**) by adjusting the length of your words, sentences, and paragraphs. That last sentence, for example, is long. It would slow a reader down. Here's the basic premise: **Long words, paragraphs, and sentences reduce reader velocity.** **Short words, paragraphs, and sentences increase reader velocity.** **Very short paragraphs and sentences (for example, one word long or one sentence long) dramatically reduce reader velocity.** There's some nuance in there, but that's the gist of it. When you paste your text, the graphs above show breakdowns of each paragraph and the lengths of each word in them. The red line indicates your reader velocity. You can zoom in on part of the graph by drawing a box in it. Or you can use the small navigation graph in the upper right corner. Clicking on individual words in the graph should highlight that word in the rendered text on the right. *Word Pacer* primarily supports Markdown syntax with a couple additional features. For instance, the `---` is an em dash (---). However, plain text should also work just fine so long as you have two carriage returns between paragraphs. Eventually, I'll add support for just plain text... and perhaps if there's interest, I'll see about adding other text formats. *Word Pacer* is still very much under development. It should analyze 2000 words of text in just over 3 seconds after you click the *Analyze Text* button. If you're reading this, chances are good that I contacted you directly about checking it out. It's hosted on GitHub and released under the GPL3. Please use that for giving me feedback (you can also track me down via email or social media, but the issue tracker is easier to follow). I'm mostly interested in feedback on the user interface, performance, and the accuracy of the reader velocity calculations... but I'll take whatever you've got. Have fun!
Debugging