Key Findings
- Only 13.9% of law firm sites preload fonts -- the single most impactful optimization for reducing font-related layout shift and invisible text. The vast majority leave font loading entirely to the browser's default behavior.
- 75.2% do not use font-display: swap. Without this CSS property, visitors on slower connections may see invisible text for 1-3 seconds while custom fonts download.
- 34.3% of sites have no detectable custom fonts at all. These sites rely entirely on system fonts or have fonts embedded in ways our scan could not detect.
- The average site loads 5.9 font files -- nearly triple what performance best practices recommend. Sites loading 10+ font files accounted for 15.5% of the sample.
- Open Sans is the most popular Google Font among law firms (6.6%), followed by Montserrat (5.3%) and Roboto (3.3%). The legal industry leans heavily toward clean sans-serif typefaces.
About This Research
Web fonts are one of the most overlooked performance bottlenecks on law firm websites. A single poorly loaded font file can delay text rendering by over a second, cause layout shifts that hurt Core Web Vitals, and create a jarring visual experience that erodes trust before a visitor reads a single word.
Despite this, there is almost no public data on how law firms actually handle font loading. Agency recommendations range from "use Google Fonts" to "self-host everything," but nobody has measured what firms are actually doing in practice. We wanted hard numbers.
In March 2026, we scanned 303 law firm websites and analyzed their font loading strategies, file counts, preloading practices, and font-display usage. Every data point in this article comes directly from that analysis.
Methodology
We collected font loading data from 303 law firm websites using automated browser analysis. For each site, our script examined:
- Google Fonts usage: Whether the site loads fonts from fonts.googleapis.com or fonts.gstatic.com.
- Self-hosted fonts: Whether the site serves font files from its own domain, detected via @font-face declarations and local .woff/.woff2/.ttf file references.
- Font file count: Total number of font files loaded during page render.
- Font families: Number of distinct typeface families in use.
- Preloading: Whether any font files are preloaded using link rel="preload".
- font-display: Whether any @font-face rules use the font-display property (particularly the "swap" value).
Sites were categorized into four groups: Google Fonts only, self-hosted only, both, or none detected. The "none detected" category includes sites using only system fonts, sites with fonts embedded in JavaScript bundles, and sites where our detection methods could not identify the font source.
The Numbers at a Glance
Font Loading Strategy Breakdown
How a site loads its fonts determines latency, reliability, and cache behavior. We categorized every site into one of four groups based on where their font files originate.
| Strategy | Sites | % of Total |
|---|---|---|
| None Detected | 104 | 34.3% |
| Self-Hosted Only | 85 | 28.1% |
| Both (Google + Self-Hosted) | 73 | 24.1% |
| Google Fonts Only | 41 | 13.5% |
The largest group (34.3%) had no detectable custom font loading. Many of these sites use system font stacks, which is actually the fastest possible approach since no font files need to download at all. Others may load fonts through JavaScript or CSS-in-JS frameworks that our static analysis could not detect.
Self-hosted fonts (28.1%) offer the best balance of visual branding and performance when implemented correctly. Loading fonts from your own domain eliminates the extra DNS lookup and TLS handshake required by Google Fonts, and gives you full control over caching, subsetting, and format selection.
The 24.1% of sites using both Google Fonts and self-hosted fonts are in the worst position from a performance standpoint. They pay the latency cost of third-party connections while also serving additional files from their own server. In most cases, this happens because a WordPress theme bundles its own fonts while the site owner separately loads Google Fonts through a plugin or theme customizer.
Google Fonts Usage Patterns
Of the 303 sites analyzed, 114 (37.6%) use Google Fonts in some form. Among those that do, the font family choices cluster tightly around a small set of popular sans-serif typefaces.
| Font Family | Sites | % of All 303 Sites |
|---|---|---|
| Open Sans | 20 | 6.6% |
| Montserrat | 16 | 5.3% |
| Roboto | 10 | 3.3% |
| Lato | 10 | 3.3% |
| Poppins | 9 | 3.0% |
| Playfair Display | 7 | 2.3% |
| Merriweather | 4 | 1.3% |
| Oswald | 3 | 1.0% |
| Mulish | 3 | 1.0% |
| Roboto Slab | 3 | 1.0% |
| Raleway | 3 | 1.0% |
The top five fonts are all sans-serif typefaces optimized for screen readability. Playfair Display is the lone serif font in the top group, often used for headings to add a traditional or authoritative feel. The average site uses just 1.2 font families, suggesting that most firms stick to a single typeface (often with multiple weights) rather than mixing heading and body fonts.
One pattern worth noting: several of these fonts (Open Sans, Roboto, Lato) are legacy choices from the early 2010s. Modern alternatives like Inter, which was specifically designed for screen interfaces, appear on only 0.7% of sites. This suggests many law firm sites are running outdated themes or have not revisited their typography choices in years.
Preloading and font-display Adoption
Font preloading and font-display: swap are the two most impactful optimizations for web font performance. Preloading tells the browser to start downloading font files immediately, before CSS is parsed. The font-display: swap property ensures text remains visible in a fallback font while the custom font loads, preventing the "flash of invisible text" (FOIT) that plagues poorly configured sites.
Adoption of both practices is remarkably low across the legal industry.
| Optimization | Sites | % of Total |
|---|---|---|
| Both Preload + Swap | 23 | 7.6% |
| font-display: swap Only | 52 | 17.2% |
| Preload Only | 19 | 6.3% |
| Neither | 209 | 69.0% |
69.0% of law firm websites use neither font preloading nor font-display: swap. These sites are fully exposed to the default browser behavior for font loading, which typically means invisible text for up to 3 seconds on slow connections (Chrome, Firefox) or immediate fallback with a disruptive swap (Safari).
Only 7.6% of sites implement both optimizations together. This is the recommended best practice and represents the gold standard for font loading performance. For context, Google's own PageSpeed Insights flags missing font-display: swap as a performance issue, yet over 75% of these law firm sites would fail that check.
Font File Count Distribution
Every font file a browser must download adds to page weight and competes for bandwidth during the critical rendering path. Performance best practices recommend limiting font files to 2-4 total. Here is how law firm websites actually stack up.
| Font Files | Sites | % of Total |
|---|---|---|
| 0 (no font files) | 188 | 62.0% |
| 1-3 files | 31 | 10.2% |
| 4-6 files | 24 | 7.9% |
| 7-10 files | 13 | 4.3% |
| 11+ files | 47 | 15.5% |
The most common result is zero detected font files (62.0%), which aligns with the 34.3% using no custom fonts plus sites where fonts are loaded through mechanisms our scanner could not detect (such as JavaScript-injected stylesheets or iframe-embedded content).
Among sites that do load font files, the distribution is bimodal. A small group loads a reasonable 1-3 files (10.2%), while a surprisingly large 15.5% load 11 or more font files. The worst offender in our dataset loaded 113 font files on a single page. Sites in the 11+ category are typically loading every available weight and style of multiple font families, often because a WordPress theme or page builder enqueues fonts broadly rather than loading only what the page actually uses.
The average across all sites is 5.9 font files. Among sites with at least one font file (115 sites), the average jumps to 15.5 files -- well above the recommended ceiling of 4.