How to evaluate website readability and plain English

Evaluate website readability by asking whether a reader can understand the point and act on it, not by chasing a single reading-age score. Review a realistic page, mark unfamiliar terms and test whether headings, sentences and action labels carry meaning for its audience.

Choose a page and reader task

Pick a service, help or policy page with a clear purpose. Ask a person who resembles the intended reader to find one answer and explain it in their own words. If no reader is available, write the question first and assess whether the page answers it directly. Record the audience and task, because technical terms may be appropriate for specialists but confusing for first-time customers.

Start from the heading and first paragraph. Can the reader tell why the page exists before scrolling?

Mark the barriers precisely

Highlight long sentences, unexplained jargon, vague pronouns and headings that do not predict their sections. Check whether a button label states an action rather than saying only “Learn more”. Note when a reader has to reread or use another page to understand a term.

A readability tool may flag sentence length, but it cannot judge whether a short sentence is accurate or useful. Use it as a clue and confirm the issue with a person where possible.

Try a small rewrite test

Consider “Our innovative solutions facilitate seamless optimisation of customer-facing processes.” A clearer version for many readers might be “We help your team answer customer enquiries faster.” The second is shorter and more concrete, but it should be used only if it accurately describes the service. Test whether readers can identify the action and benefit after the rewrite.

The website typography guide covers visual factors that may affect the same reading task.

Record meaning before style

Save the original sentence, the reader's question, the point of confusion and the proposed change. Ask the content owner to confirm accuracy before publishing. A clear sentence that misstates the service is not an improvement. Retest the task with the revised copy rather than assuming shorter always means better.

Use a teach-back question

After a reader finishes a short section, ask them to explain what they would do next and which condition might change the answer. If they repeat the page's words without being able to act, the prose may be fluent but not useful. Record the phrase that caused uncertainty and test one revised sentence with a fresh reader. For a technical service, do not simply remove a necessary term; define it at first use and keep the precise version available for readers who need detail. This checks comprehension rather than an arbitrary text score.

Frequently asked questions

Is a reading-age score enough?

No. It may flag complex text, but it cannot decide whether specialised language is needed or whether a reader understands the page.

Should all technical terms be removed?

No. Define terms when the audience may not know them and keep precision where it matters to a decision. Ask a representative reader to explain the decision in their own words.

Can a short page still be hard to read?

Yes. Vague headings, unexplained words or missing context can make even a few sentences difficult to use. Test whether a visitor can identify the offer and next action without asking for help.