Key resources not preloaded — the fix
The page declares its own web fonts (@font-face) and preloads none of them. The browser only requests such a font once layout needs it, so text waits or reflows. Only fonts are checked: stylesheets in <head> are already found first and need no preload, and Google Fonts files cannot be preloaded (preconnect instead).
Where this fits: performance in SEO
Performance is both a ranking signal (Core Web Vitals) and a conversion multiplier. Google measures real-user loading (LCP), interactivity (INP), and visual stability (CLS) — and slow sites lose visitors before analytics even registers them. Most performance issues concentrate in a few repeat offenders: unoptimised images, render-blocking resources, and third-party scripts. Fixing the top three usually moves the needle more than fixing the next thirty.
Why key resources not preloaded hurts your rankings
Without preloading, the browser discovers critical resources late in the parsing process, delaying their download. Fonts discovered through CSS @font-face rules, hero images referenced in CSS, and key scripts imported by other scripts all benefit from preloading. This directly impacts LCP and visual stability.
This is a low-severity issue: a polish item. Fix it in batches during scheduled maintenance; the win is cumulative quality, not a step change.
How to fix it
Add <link rel="preload" as="font" crossorigin> for the one or two fonts used above the fold. Preload only what the browser would find late: preloading everything makes the hints compete and helps nothing.
<link rel="preload" href="/fonts/brand.woff2" as="font" type="font/woff2" crossorigin />
<link rel="preload" href="/images/hero.webp" as="image" />Performance best practices
- Serve images in modern formats (WebP/AVIF), sized to their container, with explicit dimensions.
- Inline critical CSS and defer everything else; eliminate render-blocking third parties.
- Set far-future cache headers on static assets and an ETag on everything.
- Preload the fonts and hero image; font-display: swap to avoid invisible text.
- Measure with real-user Core Web Vitals, not just lab scores — Google ranks on field data.
The full library: SEO best practices, by category.
Frequently asked questions
What does "Key resources not preloaded" mean?
The page declares its own web fonts (@font-face) and preloads none of them. The browser only requests such a font once layout needs it, so text waits or reflows. Only fonts are checked: stylesheets in <head> are already found first and need no preload, and Google Fonts files cannot be preloaded (preconnect instead).
Why does key resources not preloaded matter for SEO?
Without preloading, the browser discovers critical resources late in the parsing process, delaying their download. Fonts discovered through CSS @font-face rules, hero images referenced in CSS, and key scripts imported by other scripts all benefit from preloading. This directly impacts LCP and visual stability.
How do I fix key resources not preloaded?
Add <link rel="preload" as="font" crossorigin> for the one or two fonts used above the fold. Preload only what the browser would find late: preloading everything makes the hints compete and helps nothing.
How serious is this issue?
This is a low-severity issue: a polish item. Fix it in batches during scheduled maintenance; the win is cumulative quality, not a step change. It belongs to the performance family of checks.
How do I find every page affected by this on my site?
Run a free Dr Urls audit: it crawls your site, detects key resources not preloaded on every affected page, shows example URLs, and generates a ready-to-use fix task. Re-scan after fixing to verify the issue is gone.
Does your site have this issue?
A free Dr Urls audit crawls your site, finds every page affected by key resources not preloaded, and hands you a ready-made fix task.
Check my site free