text‑rendering Tester - Online Optimize Legibility
Compare text‑rendering: auto, optimizeSpeed, optimizeLegibility, geometricPrecision. See kerning and ligature changes live.
UD5 Toolkit
Compare FOIT (Flash of Invisible Text) and FOUT (Flash of Unstyled Text) in real time. Load custom fonts, simulate network delays, and see exactly how users experience your typography before and after font loading.
font-display property controls how a font is displayed during loading. Values include auto, block (FOIT), swap (FOUT), fallback, and optional. For example, font-display: swap immediately shows the fallback and swaps later, improving perceived performance.
font-display: swap is recommended because it avoids invisible text and reduces LCP (Largest Contentful Paint) delay. Google recommends ensuring text remains visible during webfont load. Use optional only if the custom font is not critical.
.woff2 file. If you see a network error, try hosting the font on the same domain or using a CDN that allows CORS (like jsDelivr or Google Fonts gstatic). Our preset fonts are CORS-enabled.
font-display: block vs swap.
<link rel="preload">. Use font-display: swap or optional. Match fallback font metrics to the custom font using size-adjust, ascent-override, and descent-override in @font-face to reduce layout shift (CLS).
Compare text‑rendering: auto, optimizeSpeed, optimizeLegibility, geometricPrecision. See kerning and ligature changes live.
Detect browser support for font‑tech() and font‑format() values in @font‑face src. Check COLRv1, variable, etc.
Enter a URL and extract the font stacks and web font URLs used on that page. Quick typography research.