Realtime character and word counter tool. Fast loading, no ads, and free to use.
About the Free Character Counter Tool
Despite all the different tools and resources I make use of for work, I seem to keep needing a very simple character and word counter.
Between writing for Twitter (140 characters or below), a webpage title tag (55 characters or below for ideal length, although you can go longer), a webpage meta description (150 characters or below), or just needing to write a short summary of something your'e working on, just having a simple tool like the one above can really help speed things along.
There were a few other online tools like this one that I used to use, but over time they started adding on a million features, tons of ads, popups that interrupted using the tool, and the sites got really slow (probably from all the extra features and ads).
I got sick of watching once good tools go bad, so I cobbled together one for my own use, and thought others might benefit from it as well.
All it does is count characters (including spaces) and words as you type, so you don't have to trigger a summary every time. Want to clear out everything? Just reload the page and you'll start with a blank slate.
Bookmark it for future use and share it with others!
How to Calculate Estimated Reading Time For a Blog Post
You've probably seen on a number of sites reading time estimates for blog posts and pages.
I think it's an awesome trend, to give readers an idea of how long a post is.
There seems to be a lot of plugins and add-ons to help you figure this out, but there's a very simple DIY way to do it without any extra help.
1 – Count all the words on a post (use this tool or a plugin like Word Count for Chrome)
2 – Divide the number of words by 190.
3 – Round that number up to the next whole number, and that's the number of minutes to read your article.
A common rule of thumb used for reading speed is 200 words per minute. That's a pretty rough estimate, as not only do different people read at different speeds, but also read at different speeds under different circumstances (think of how easy or hard it is to focus when there's a lot going on around you vs being alone in a quiet area).
So I also lowered that estimated reading speed to 190 to add a little bit more of a buffer. Rounding up to the next whole number adds a little more of a buffer too.
And it's always better to overestimate how long a post will take to read, so a reader won't be caught off guard by a longer than expected read.
This is the format I use for estimating read times, and now you can too!