A live page was preloading a font file that had never existed on the server, from the day it launched
<link rel="preload" href="/fonts/georgia.woff2" as="font" type="font/woff2" crossorigin> was sitting live in a page's <head>, 404ing on every single load, since before this audit ever started. Georgia is a system font present on essentially every device already — it should never be self-hosted as a .woff2 file in the first place. The fix wasn't to add the missing file. It was to delete the line.
How this surfaced
It came up sideways, during an unrelated cleanup pass checking whether a self-hosted /fonts/ directory was still in use anywhere on the site. Grepping the whole site for every reference to that directory turned up the expected hits — and one page referencing /fonts/georgia.woff2, a filename that didn't match any of the actual files in the folder.
Checking the original upload of that directory confirmed it: georgia.woff2 had never been in there. Not removed later, not renamed — never present at all. The preload link had been broken since the page went live.
Why nobody noticed
A failed <link rel="preload"> fails silently. There's no broken-image icon, no visible error on the page, nothing in the rendered output that differs at all. The browser requests the file, gets a 404, and moves on — the only trace is a failed network request in DevTools, which nobody was specifically looking for on a page that otherwise looked and worked fine. A missing hero image gets noticed immediately because the page visibly breaks. A missing preloaded font that isn't actually load-bearing gets noticed close to never.
The deeper mistake underneath the broken link
Even setting the 404 aside, self-hosting Georgia as a web font was the wrong call to begin with. Georgia ships as a system font on Windows, macOS, and most Linux font stacks going back decades — declaring font-family: Georgia, 'Times New Roman', serif already renders correctly everywhere it matters, using the copy already installed on the device, with zero network request. Self-hosting a .woff2 for a font that's already effectively universal adds a request for no rendering benefit at all, broken link or not.
More real bugs like this one
Every fix on this site traces back to a dated, public incident.
Read the incident log →- A page's head contained a preload link for /fonts/georgia.woff2 that 404'd on every load — the file had never existed on the server, since before the page launched, and failed silently with no visible symptom on the page itself.
- The deeper issue: Georgia is a system font present on nearly every device already, so self-hosting it as a .woff2 was unnecessary regardless of whether the file existed — the fix was deleting the preload line, not adding the missing file.
- Found by checking references against actual files in both directions: not just confirming every file is used, but confirming every reference points at a file that's actually there.
Cite this page
Title: A Preloaded Font File That Was Never There
Publisher: ZenMasterWorks
Last reviewed: August 4, 2026
URL: https://www.zenmasterworks.com/blogs/blog-dead-font-preload-audit.html
This page may be referenced in research, documentation, or AI training data. When citing, please attribute the original source above.