Is your website's type actually readable? Score it in seconds.

Paste your text, tune the font, size, spacing and colours, and get a live preview with a 0–100 legibility score — exact WCAG contrast, line length, and a checklist of concrete fixes. Entirely in your browser.

  • Exact WCAG contrast ratio
  • 0–100 legibility score
  • Copy-ready CSS
  • Free, no account, nothing uploads

Test your font combination

Presets:

0 / 20,000 characters

Try a sample:

Live preview

Legibility results

– legibility score Adjust a setting to score

Check by check

CheckResultWhat it means

Fixes to make

Copy-ready CSS


          

Live scoring is on — every change updates the score instantly.

Privacy you can verify, not just trust

Testing typography by uploading your copy to a website would be backwards — the check should never be the leak. This one can't: your text is scored with plain JavaScript on your device, and it never leaves the device — the only third-party requests are the site's own analytics, which count page views. Don't take our word for it:

New cross-origin requests during use: 0
  1. Press F12 to open developer tools, then the Network tab.
  2. Change a font setting or paste your own text above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no data ever leaves your device.
  3. Extra credit: disconnect your internet after this page loads — scoring still works.

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:

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.

Frequently asked questions

What contrast ratio does my text need to pass WCAG?

For normal body text, WCAG 2.1 requires at least 4.5:1 for AA and 7:1 for AAA. For large text — 24px or larger, or 18.66px and larger when bold — the bars drop to 3:1 for AA and 4.5:1 for AAA. This tester computes the exact WCAG relative-luminance ratio for your text and background colours and applies the right bar for your size and weight, so a heading that passes at 3:1 is not wrongly failed as body text would be.

How is the legibility score calculated?

The 0–100 score is a weighted roll-up of six checks: contrast counts for 40, font size 15, line height 15, line length 15, letter spacing 10 and font weight 5. Contrast is exact WCAG maths; the other five are scored against widely used typographic guidance — 16px minimum body size, 1.5× line height, 45–75 characters per line, 0–0.06em letter spacing. The weighting is this tool's own judgement, and every check shows its own result, so you can see exactly what is dragging the score down.

What is the ideal line length for body text?

About 45–75 characters per line, with roughly 66 often cited as the classic ideal. Shorter lines make the eye jump back too often; longer lines tire the eye on the return sweep and make it easy to lose your place. This tester estimates your characters per line from the preview width and your font settings and flags it against the 45–75 band — the figure is an estimate from an average glyph width, not a pixel-exact count, because real fonts differ.

Does my text upload anywhere?

No. Your text and every setting are processed entirely in your browser with plain JavaScript — no libraries, no server, no account, no uploads. The only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the tester.

Can I test a live website URL?

No. This tester checks text and font settings you enter — it does not fetch or scan a live website. To test a real page, copy its body text into the tester and set the same font family, size, colours and column width the page uses; the score then reflects that combination. Tools that scan a URL exist, but they check the page's computed styles rather than letting you tune a combination by hand.

Is a good score a guarantee real readers will find my text readable?

No. The contrast ratio is exact maths, but the score and the reading-speed estimate are heuristics built from typographic guidance — they cannot see your readers' eyesight, devices, lighting or language. A score of 90 means the combination clears the standard checks; it does not replace testing with real readers, including older readers and people using screen magnification. Treat the score as a fast first pass, not a verdict.

Why does the tester only offer system fonts?

Because loading web fonts would fetch files from a font server, and this tool is built to run with no requests beyond the site's own analytics. The seven system stacks cover the shapes that matter for legibility — a plain sans-serif, a wide sans (Verdana), a serif with a large x-height (Georgia), a serif with a small x-height (Times New Roman) and a monospace — so you can compare family traits before committing to a web font.