Testing readability on a page without JavaScript
Minimalist web design often relies on plain HTML and CSS, with no JavaScript shaping the reading experience. When a page is built with care for typography, whitespace, and contrast, readability becomes a property of the text itself. Designers in Sydney and Melbourne strip work down to semantic markup, yet must verify that real readers find the content clear.
A page like this minimalist microsite shows how far restraint can go. The content loads instantly, the structure is transparent, and there is no client-side rendering to obscure the words. Australian studios that publish institutional reports often follow the same path, and the methods below apply to a one-page reference site and a government white paper alike.
Readability blends vocabulary difficulty, sentence shape, layout, and the visual rhythm of paragraphs. On a static page, all of these are visible the moment the file opens, with no spinner, delayed font swap, or interactive widget to shift text after the fact. That stability makes the reading experience measurable in a way a dynamic interface rarely is.
This article walks through practical ways to test readability when scripts are absent or irrelevant. It covers manual reading sessions, hand-calculated formulas, visual checks, and tools that parse raw HTML. The goal is a workflow any designer or reviewer in Brisbane or Perth can run from a laptop.
Why no-JS pages deserve a focused check
When a page has no JavaScript, the user sees what the author wrote and nothing else. Any flaw stands out: a skipped heading, low contrast, a line length stretched to the edge. Each becomes part of the reading experience with no script to soften it.
Many Australian government and education sites, which must work on slow regional connections in Cairns or Launceston, choose a static-first approach. Readability testing on these pages is a gate the content must pass before publication, forcing the writer to confront line length, paragraph weight, and vocabulary directly.
Because the document is stable, a tester can save the page, open it in a plain text editor, and analyse it offline. The result is a more honest measure than a screenshot of a script-driven page that may differ across devices.
Running manual reading sessions locally
The most reliable readability test is still a person reading the text. A small group of three to five participants is enough to surface problems that any formula would miss. Sessions can be held in a quiet room in Adelaide, over a video call with a reviewer in Hobart, or as a timed exercise in a university lab in Canberra.
Ask each participant to read a passage aloud while the observer records hesitations, skipped words, and rereads, then summarise the main idea in their own words. Because the page has no JavaScript, the experience is consistent: what one reader sees, all readers see, with no need to disable scripts.
Formulas you can calculate by hand
The Flesch Reading Ease score, the Flesch-Kincaid grade level, and the Gunning Fog index all rely on counts of words, sentences, and syllables. None of them require a script to evaluate. A tester can copy the text into a text file, tally the sentences, estimate the average words per sentence, and note the percentage of complex words.
For Australian audiences, the target band sits between Flesch Reading Ease scores of 60 and 70, which corresponds to plain English for a general adult reader. Government writing guides in Canberra encourage similar ranges, and a hand calculation is precise enough to see whether the text fits.
Typography and contrast on a static page
Readability is also visual. On a JavaScript-free page, the designer controls every typographic decision through CSS, with no script to override a font weight or line height. That makes it easier to check legibility by eye.
Line length, often called the measure, should sit between 50 and 75 characters for comfortable reading. Line height between 1.4 and 1.6 keeps the eye moving without losing the line. Contrast between text and background should meet accessibility guidelines, and a simple visual check in good light is a reasonable first pass.
Quick visual checks
- Measure the average line length in a representative paragraph
- Confirm the body text has a line height of at least 1.4
- View the page in bright and dim light to spot contrast issues
- Resize the window to see how the measure holds up
Comparing common readability formulas
Different formulas weight different elements, and a useful test applies more than one. The summary below lists widely used measures and what they emphasise. Each can be calculated without running any code, which suits a no-JS workflow.
| Formula | Inputs | Strength | Best for |
|---|---|---|---|
| Flesch Reading Ease | words, sentences, syllables | Simple scale, widely understood | General consumer writing |
| Flesch-Kincaid Grade | words, sentences, syllables | Maps to a school grade level | Educational content |
| Gunning Fog | words, sentences, complex words | Highlights dense vocabulary | Editorial and policy text |
| SMOG Index | sentences, complex words | Quick estimate from a small sample | Short articles and brochures |
A page aimed at readers in Perth or Darwin might target a Flesch Reading Ease above 60, while a research summary may accept a higher Fog index. The point is to choose a target and measure consistently.
Browser tools that read the source, not the runtime
A small set of browser extensions and built-in features can inspect a static page without relying on the page's own scripts. The browser's reader view, available in Safari, Firefox, and Chromium-based browsers, strips styles and presents the text in a clean column. It is a quick way to see the content as a focused reading.
Browser developer tools also let a tester view the page with JavaScript disabled. The DOM is still visible, the cascade is still applied, and the text is still selectable. Extensions that calculate readability scores parse the visible content, making them suitable for static pages.
For Australian reviewers, accessibility audits often use the Axe extension or the WAVE tool. Both work on the rendered document, do not require the page to load its own scripts, and flag issues that affect readability such as low contrast or missing heading levels.
A simple testing routine for any project
A repeatable routine helps a team catch problems before publication. The following steps work for a single-page microsite as easily as for a multi-page report, and they assume no JavaScript is in play.
Routine steps
- Export the page text into a plain file for manual review
- Calculate Flesch-Kincaid and Gunning Fog scores by hand or with a local script
- Run a reader view test in two different browsers
- Conduct at least one timed reading session with a real person
Together, these steps give a balanced view of how readable a static page really is. The combination of formula, visual check, and human session covers what a single number cannot. For a designer in Melbourne, an editor in Brisbane, or a regional reviewer, the routine is portable.
A static page rewards careful preparation. When there is no script to patch the experience after the fact, the words, the layout, and the rhythm have to carry the reader on their own. Testing readability without JavaScript is a way of listening to that work before it reaches the public.