PERFORMANCE · SEO GLOSSARY
Resource Hints
HTML link elements that instruct browsers to prefetch, preconnect, preload, or prerender resources — used to improve page loading performance by initiating connections and resource downloads earlier than they would otherwise begin, reducing the impact of network latency on LCP and other Core Web Vitals.
Definition
Resource hints are HTML link elements placed in the page `<head>` that communicate to the browser that certain resources will be needed, enabling the browser to take early action — establishing connections, downloading resources, or even rendering pages in the background — before the resources are explicitly referenced later in the page load. Resource hint types: (1) **`<link rel="preload">`**: instructs the browser to download a specific resource as high priority, even before it would normally be discovered. Most commonly used for LCP images and critical fonts. A preloaded LCP image starts downloading at the very beginning of the page load rather than after the CSS and JavaScript are parsed. Required attributes: href (resource URL), as (resource type: image, font, script, style). (2) **`<link rel="preconnect">`**: establishes a connection (TCP handshake + TLS negotiation) to a specified origin before any requests are made from that origin. Used for third-party origins from which critical resources will be loaded (CDN, font provider, analytics). Reduces connection establishment time when those resources are requested. (3) **`<link rel="dns-prefetch">`**: performs DNS lookup for a specified origin in advance. Lower cost than preconnect (no TCP/TLS, just DNS); appropriate for third-party origins that are used but not critical-path. (4) **`<link rel="prefetch">`**: low-priority download of a resource expected to be needed in the future (e.g., the next page in a paginated sequence). Browser may or may not honour based on network conditions. (5) **`<link rel="prerender">`**: deprecated; browser-specific support only. Prefetch is the modern replacement for speculative loading. Resource hint priority: preload for current page critical resources; preconnect for critical-path third-party origins; dns-prefetch for non-critical third-party origins; prefetch for next-page resources. Overuse of resource hints (preloading everything) reduces their benefit by competing for early bandwidth.
Why it matters for SEO
Resource hints are among the highest-impact performance optimisations for LCP — the Core Web Vitals metric most strongly correlated with page experience ranking signals. A `<link rel="preload">` for the LCP image can reduce LCP by hundreds of milliseconds on typical page loads by starting the image download at the earliest possible moment. `preconnect` for critical CDN or font origins reduces connection latency for resources that would otherwise wait for connection establishment. Correct resource hint implementation often produces meaningful CrUX LCP improvements.
How DeepSEOAnalysis checks this
DeepSEOAnalysis audits resource hint usage: checking for preload hints on LCP images (confirming the LCP element has a `<link rel="preload" as="image">` in the page head), checking for preconnect hints on critical third-party origins, and identifying preloads for resources that never appear on the page (wasted preloads that consume bandwidth). CrUX LCP field data reflects the real-world impact of resource hint configuration.
GLOSSARY
Related terms
performance
LCP Image
The image element identified by Chrome as the Largest Contentful Paint (LCP) candidate on a page — the largest visible image in the initial viewport that determines the LCP timing score, typically the hero image, product thumbnail, or featured photo at the top of the page.
Read definition →performance
Lazy Loading SEO
The SEO implications of lazy loading — deferring loading of images and other resources until they enter the viewport — which improves initial page load performance but can harm LCP if the main content image is lazy-loaded, and can prevent off-screen content from being indexed if text content is lazy-loaded.
Read definition →performance
Render-Blocking Resources (SEO)
CSS stylesheets and JavaScript files that block the browser from rendering page content until they are downloaded and processed — a primary cause of poor LCP and FCP (First Contentful Paint) scores, requiring deferral, async loading, or inline critical CSS strategies to resolve.
Read definition →performance
Performance Budget
A predefined set of constraints on web page performance metrics — such as maximum JavaScript bundle size, maximum LCP time, or maximum total blocking time — used to prevent performance regression as a website evolves, by alerting or failing builds when the page\'s performance metrics would exceed the defined thresholds.
Read definition →performance
DNS Prefetch (SEO)
The `<link rel="dns-prefetch">` resource hint that instructs the browser to perform DNS resolution for a specified origin in advance — reducing the DNS lookup latency for third-party origins that aren\'t critical enough to warrant a full preconnect but still contribute to page load time.
Read definition →See how your site scores on Resource Hints.
The free DeepSEOAnalysis audit checks resource hints and 100+ other signals. Full report, no signup.
Run a free audit →