Resource Hints
Checks for dns-prefetch, preload, and prefetch hints for performance.
What this check measures
We look for `<link rel="dns-prefetch">`, `<link rel="preload">`, and `<link rel="prefetch">` usage. These help prioritize critical resources and pre-load likely-next resources.
Why it matters
Well-placed preload for the LCP image can cut LCP by 300-800ms. Overused or incorrect hints waste bandwidth and confuse the browser's scheduler.
How our audit detects it
Parse link tags with rel=dns-prefetch/preload/prefetch. Validate that preloaded assets are actually used above the fold.
Typical findings
- error_outlineHero image not preloaded — unnecessary 500ms LCP.
- error_outlinePreload on a font never used on the page.
- error_outlinePreload without `as` attribute — browser ignores it.
How to fix
Preload the LCP image and critical fonts only. Do not preload everything — it dilutes priority. Always include `as="image"` or `as="font"`.
Frequently asked questions
Preload or prefetch?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
SSR / Pre-rendering
Checks if the page is server-rendered or statically pre-rendered.
TechnicalHTTP Status Codes
Checks that pages return proper status codes — 200 for live, 404 for missing, 301 for moved.
TechnicalNo Client-Side Redirects
Checks that redirects happen server-side, not via JavaScript.
TechnicalViewport Meta Tag
Checks for <meta name="viewport" content="width=device-width, initial-scale=1">.