How to test your website's font legibility
Most legibility problems are not a bad font — they are a good font used badly: too small, too tight, too pale, or stretched across a column so wide the eye loses its place. This tester checks the combination, not the font alone, and tells you exactly what to change.
To use it:
- Paste your own text — a paragraph from the page you are actually shipping — or try one of the sample passages. Real copy beats lorem ipsum: numbers, prices and long words are where legibility usually breaks.
- Set the same font settings your page uses: family, size, weight, line height, letter spacing, text and background colours, and the column width. Or start from a preset (body text, heading, small print, mobile) and tune from there.
- Read the score and the checks. The 0–100 score rolls up six checks — contrast, size, line height, line length, letter spacing and weight — and each one shows its own result, so you can see whether the problem is colour, size or spacing.
- Work through the fixes. Every failed or weak check carries one concrete change. Apply the biggest one first — usually contrast or size — and watch the score move.
- Copy the CSS. When the combination scores well, copy the generated CSS straight into your stylesheet.
What makes this tester different
The free tools that rank for this search each cover only part of the job. Goafreet's Readability Lab is a full WCAG 2.2 laboratory — powerful, but dense and jargon-heavy for a quick check. AnyTool's Font Size Tester and Bushe's font size checker grade size, leading and line length, but neither checks colour contrast at all. Digitup's readability checker scans a URL instead of letting you tune a combination by hand. And ContrastLab splits the job across three separate tools — one for contrast, one for pairing, one for readability. This page is the one place that scores contrast, size, spacing and line length together into a single 0–100 legibility score, with a fix for every weak check and CSS you can copy out — in plain English, with nothing to install and nothing uploaded.
When is this the right check?
Whenever type is about to meet readers: before launching a new site or a redesign, when a body font or colour palette changes, when a layout widens a text column, and when small print — footers, captions, form labels, prices — has to stay readable at 12–13px. It is also the fast first pass for a WCAG accessibility review: the contrast verdicts are exact WCAG 2.1 maths, applied with the correct bar for the text size.
Honest limitations
Contrast is exact; the score is not
The contrast ratio is exact WCAG 2.1 relative-luminance maths. The 0–100 score and the reading-speed estimate are heuristics built from typographic guidance — useful for comparing combinations, not a measurement of real readers.
Line length is an estimate
Characters per line is estimated from an average glyph width per family (about 0.5em for proportional Latin, 0.6em for monospace). Real fonts, weights and languages differ, so treat it as guidance, not a pixel-exact count.
No live URL fetching
The tester checks the text and settings you enter — it does not fetch or scan a live website. Copy the page's text and settings in to test a real page.
System fonts only
Only system font stacks are offered, so the page makes no font-server requests. A web font you plan to use will render slightly differently — compare its family traits here, then verify in the real font.
Not a substitute for real readers
No automated check can see your readers' eyesight, devices, lighting or language. A good score means the combination clears the standard checks — test with real readers, including older readers and people using magnification, before you call it done.
Colour alone is not legibility
A passing contrast ratio does not rescue type that is too small, too tight or set across an over-wide column. The score weighs all six checks for exactly that reason — fix the weakest one first.