Reading Time
The estimated time it takes to finish reading a text. It is calculated from the character count or word count.
Reading time is the estimated time needed to read a text from beginning to end. Values of 400 to 600 characters per minute for Japanese and 200 to 250 words per minute for English are widely used as guidelines. One of the triggers that made the display common on blogs and news sites was Medium, and the company published how its site calculates it in June 2014. The premise used there is about 275 words per minute, which is faster than the guidelines above. In other words, even for the same manuscript, the number of minutes displayed changes depending on which premise value you adopt.
The calculation itself is simple: divide the total number of characters (or words) in the main text by the reading speed per minute and round up the fraction. For a 2,000-word article, it is 10 minutes at 200 words/minute and 8 minutes at 275 words/minute. For Japanese, many implementations adopt around 500 characters per minute, and when technical documents or specialized books are assumed, they lower it to about 300 to 400 characters. For articles that include images or code blocks, there is also a method of adding viewing time. In the published information mentioned above, Medium describes a method that adds 12 seconds for the first inline image and 11 seconds for the second, reducing by 1 second per image, and adds a flat 3 seconds for the 10th image onward. This is because if you simply keep multiplying 12 seconds per image, reading time grows unrealistically long for articles with many images.
The purpose of displaying reading time is to let readers grasp the length before they start reading. If it says "you can read this in about 3 minutes," it becomes easier to decide whether to read it even when you cannot set aside a block of time. For writers, it becomes material for considering whether to split the article or narrow its structure. However, no generalized figures have been published on how much displaying it changes the way articles are read, so treat it on the premise that you will confirm the effect with measurements on your own site.
On the implementation side, there are two methods: precalculating on the server side, and calculating dynamically on the client side with JavaScript. In static site generators, it is common to calculate the reading time of each article at build time and embed it as metadata. Hugo has the page variable .ReadingTime as standard, and in Gatsby, gatsby-transformer-remark provides timeToRead. WordPress also has multiple plugins that display reading time. What to watch out for with the precalculation method is the accident in which an old number of minutes remains without being recalculated after the main text is revised. Because reading time is a value derived from the main text rather than from metadata, fix the generation order so that it comes after the main text is finalized.
How to decide the calculation scope is another part that differs between implementations. The word count changes depending on how much of the headings, figure captions, footnotes, code, tables, and comment sections is included. Because code and tables divide readers into those who skip them and those who follow them line by line, no treatment yields a value that fits everyone. Rounding up the fraction also has its quirks, and both a 300-character article and a 600-character article are displayed as "1 minute." On sites lined with short articles, the number of minutes alone does not convey the difference in length, so it is more practical to show the character count alongside it.
A common misconception is thinking that reading time must be accurate. Reading speed varies greatly between individuals and changes even for the same person depending on the subject and level of concentration, so an accurate prediction is not possible in the first place. What matters is consistency rather than accuracy, and applying the same premise value and the same calculation scope to every article on the site leads to trust. Making articles look shorter than they really are to encourage people to start reading betrays the expectations of readers who did not finish, so it is not recommended in the long term.
In relation to character counting, reading time is a metric derived directly from the character count. Since the reading time is determined at the point you decide the target character count, you can also proceed by working backward from "how many minutes should the article take to read" at the planning stage to set the character count. A Japanese article that can be read in 5 minutes is around 2,500 characters on the premise of 500 characters/minute. Note that no search engine has announced that it uses the length of reading time itself as a ranking signal. The goal is to keep the length to what readers can read through, and it is no reason to pad or cut text to match a specific number of minutes.