You’ve just rewritten the services page for your landscaping business. Out of curiosity you paste it into a readability checker, and the big number at the top comes back as −15.2, labelled Very difficult. You didn’t know the scale went below zero. Is the page bad? Did you break something?
Here’s the paragraph that did it: “Our team of experienced landscaping professionals is committed to delivering comprehensive, environmentally responsible garden solutions tailored to the individual requirements of each client. From initial consultation through to final installation, we provide a personalised service that combines creative design expertise with practical horticultural knowledge. Maintenance packages are also available.”
Nothing is broken. That number is a Flesch Reading Ease score, and it’s telling you something fairly specific about those sentences. Once you know what it counts, it becomes a useful nudge rather than a mystery. You can follow along by pasting your own text into the Readability Checker.
What Flesch Reading Ease actually measures
Rudolf Flesch published the formula in 1948. It looks at just two things: how many words your sentences have on average, and how many syllables your words have on average. Long sentences and long words pull the score down. That’s it. Here is the whole formula:
206.835 − 1.015 × (words ÷ sentences) − 84.6 × (syllables ÷ words)
Look at the weights. Each extra word per sentence costs about one point. Each extra syllable per word, on average, costs nearly 85. So the landscaping paragraph sinks mainly because of words like “environmentally”, “consultation” and “horticultural”, and partly because two of its three sentences run past 20 words.
What the formula doesn’t look at is meaning. It can’t tell whether your argument holds together, whether the reader knows what “SKU” means, or whether a short sentence is also a confusing one. Treat the score as a reason to re-read, not a verdict.
Reading the 0–100 scale
Most text lands between 0 and 100, and higher means easier. Very short, simple text can go above 100, and dense text like the example above can drop below zero. Flesch attached plain-language labels to the ranges, and the Readability Checker shows the same ones:
| Score | Label | Roughly suits |
|---|---|---|
| 90–100 | Very easy | about 5th grade (age 10–11) |
| 80–90 | Easy | about 6th grade (age 11–12) |
| 70–80 | Fairly easy | about 7th grade (age 12–13) |
| 60–70 | Plain English | 8th–9th grade (age 13–15) |
| 50–60 | Fairly difficult | 10th–12th grade (age 15–18) |
| 30–50 | Difficult | college level |
| 0–30 | Very difficult | college graduate level |
One more thing before you trust a number. Scores from a single paragraph jump around a lot, because one long sentence has a big effect on the average. A few paragraphs give a much steadier reading.
Why it doesn’t match the grade level you’ve seen elsewhere
If you’ve used other tools you may have seen a Flesch–Kincaid grade level instead, something like “grade 8.4”. It’s a close cousin, made in 1975 for the US Navy. It uses the same two ingredients with different weights and gives the answer as a US school grade. The direction is flipped, though: a higher Reading Ease means easier text, while a higher grade means harder text. A Reading Ease of 65 and a grade of 8 can describe the same page.
Other formulas measure difficulty in their own way. Coleman–Liau and the Automated Readability Index count letters instead of syllables, Gunning Fog looks at the share of words with three or more syllables, and SMOG needs a sample of 30 sentences. The Readability Checker runs all six and averages the grade-level ones into a single “about US grade X” line under the main score (SMOG joins the average once there are 30 sentences). That’s why the line won’t always agree neatly with any one formula.
What is a good Flesch Reading Ease score?
For general web content, around 60 or higher is the usual target. That’s the Plain English band, and it covers product pages, help articles, emails to customers and most blog posts. Pages for a broad public audience, like instructions or a council letter, do well even higher.
Not every text should hit 60, though. A legal contract, a research paper or an engineering spec will usually score somewhere in the 30s or 40s, and that’s normal. Those readers expect precise terms, and “myocardial infarction” is a mouthful whether you like it or not. Swapping technical words for vague ones to please a formula makes the writing worse.
So compare drafts of the same piece rather than chasing one number. If your report scored 32 last week and 41 after editing, you’ve made it easier to read, even if it’s still labelled Difficult.
How to improve your Flesch Reading Ease score
Start with the sentences the tool flags. Under the scores, the Readability Checker marks every sentence over 20 words as Long and every one over 30 as Very long, with the word count beside it. Those are your first edits. Splitting one sentence into two is often enough on its own.
Here’s an example from a typical training email. “The installation of the software should be completed prior to the commencement of the training session, which will be facilitated by a member of our technical support team.” That one sentence scores 36.4. Rewritten as “Install the software before the training starts. Someone from our support team will run the session.” it scores 77.1. Nothing was lost, and the instruction is now the first thing you read.
That rewrite used several tricks at once. Taken one at a time:
- Swap long words for short ones where the meaning doesn’t change. “Prior to” becomes “before”, “commencement” becomes “start”, “facilitate” becomes “run” or “help”, and “utilise” becomes “use”. Because syllables carry so much weight, this often moves the score more than shortening sentences does.
- Turn nouns back into verbs. “The installation of the software should be completed” hides the action inside a noun. “Install the software” says it directly and drops five words.
- Pull nested clauses out into their own sentences. “The report, which was prepared by the finance team after the audit that the board requested in March, shows that costs rose” scores 73.0. “The finance team wrote the report after the March audit. It shows that costs rose.” scores 92.1, and the main point no longer waits until the end.
- Cut words that don’t do anything. “Are also available” can usually lose “also”, and phrases like “in order to” work fine as “to”.
Applied to the landscaping paragraph from the start, the result reads: “We design and build gardens for homes and businesses across the region. Every plan starts with what you need. We use plants that suit the local soil and weather, so your garden needs less water and less work. We can also look after it once it’s finished.” Same offer, same length almost to the word. The score goes from −15.2 to 83.3.
A word of caution about gaming it. Headings and list items each count as a sentence, and chopping everything into four-word fragments will push the number up fast. It will also make the page read like a telegram. If a sentence needs 25 words to be clear, let it have them, and make the ones around it shorter.
Checking your own text
Paste a page or a draft into the Readability Checker, look at the Reading Ease score and the sentences marked Long, fix the worst few, and paste it in again. Your text stays in your browser the whole time. It only works for English, since the formulas and the syllable counting were built for it.
Shorter sentences make typos easier to spot too, so it’s a good moment to run the result through the Grammar Checker. And if the piece has to fit a word limit, the Word Counter keeps a running total while you cut.
Back to all articles




