Why Resource Hints?
Every year, load speed requirements grow: Core Web Vitals have become a ranking factor. Resource Hints are one of the most effective tools to reduce LCP and TTFB without changing architecture. However, incorrect use of preload or preconnect can degrade performance — resources load with wrong priority or get duplicated. Let's examine how to properly use dns-prefetch, preconnect, preload, and prefetch, and show a real case.
On one project with a catalog of 10,000 products, we reduced LCP from 3.2 s to 2.1 s by combining preconnect to CDN and preload for the LCP image — saving 1.1 s on mobile. Implementation took 6 hours: the audit revealed missing preconnect to fonts and incorrect crossorigin on preload. Load time savings reached up to 40%.
How Resource Hints Directives Work
-
dns-prefetch — resolves DNS for a domain. Minimal cost, saves 20–120 ms.
-
preconnect — DNS + TCP + TLS. Saves 100–500 ms, but more expensive. Only for precisely needed third-party domains.
-
preload — loads with high priority. Critical for LCP image, main font, critical CSS.
-
prefetch — loads with low priority for the next page. Used during browser idle time.
| Directive |
When to use |
Resource |
dns-prefetch |
Third-party domains (analytics, CDN) |
— |
preconnect |
Exact third-party domains (fonts, API) |
— |
preload |
Critical resources of the current page |
LCP image, fonts, critical CSS |
prefetch |
Resources of the next page |
JS chunks, HTML, data |
When to Use preload vs prefetch
Preload loads with high priority, making the resource available 2–3 times faster than standard discovery. Prefetch loads with low priority only during browser idle time, not affecting current loading. Preload is used for resources of the current page: LCP image, main font, critical CSS. Prefetch is for resources of the next page: JS bundle for the catalog page when navigating from the cart.
Why preconnect is Critical for Fonts
Fonts are usually loaded from an external domain (e.g., Google Fonts). Without preconnect, the browser first performs a DNS lookup, then TCP and TLS — this can take up to 300 ms. Preconnect establishes the connection in advance, saving precious milliseconds from FOUT. It is important to specify the crossorigin attribute for fonts; otherwise, the browser will make two requests: one via preload, another when discovered in CSS. According to the W3C specification, preconnect should only be used for critical domains, no more than 6.
What to Preload First?
Typical set for a page:
- Preconnect to Google Fonts, CDN, API server.
- Preload LCP image (fetchpriority="high").
- Preload main font (with crossorigin).
- Prefetch for likely next page (e.g., cart after catalog).
Without preload, the font will load only after CSS is parsed — causing FOUT (flash of unstyled text). With preload and preconnect, it is available immediately.
How We Implement Resource Hints
We deploy Resource Hints in two ways: server-side HTTP Link header (received before HTML parsing) and <link> tags in <head>. The choice depends on the stack and requirements.
Example for Laravel:
// app/Http/Middleware/ResourceHints.php
class ResourceHints
{
public function handle(Request $request, Closure $next): Response
{
$response = $next($request);
$hints = [
'<https://fonts.googleapis.com>; rel=preconnect',
'<https://fonts.gstatic.com>; rel=preconnect; crossorigin',
'</fonts/Inter-Regular.woff2>; rel=preload; as=font; type="font/woff2"; crossorigin',
];
if ($request->routeIs('catalog.*')) {
$hints[] = '</assets/product-page-chunk.js>; rel=prefetch; as=script';
}
$response->headers->set('Link', implode(', ', $hints));
return $response;
}
}
For React/Next.js, we use dynamic <Head>:
import Head from 'next/head';
export default function ProductPage({ product }) {
return (
<>
<Head>
<link rel="preconnect" href="https://cdn.example.com" />
{product.heroImage && (
<link rel="preload" href={product.heroImage} as="image" fetchpriority="high" />
)}
</Head>
{/* ... */}
</>
);
}
Implementation Stages
- Audit current hints via Lighthouse and Network tab. Identify missing or incorrect directives.
- Configure preconnect for all third-party domains (CDN, fonts, API, analytics).
- Set preload for LCP image, critical CSS, and fonts with correct
crossorigin attribute.
- Implement server-side
Link header and dynamic prefetch based on navigation (hover prefetch).
- Test and document results.
Process and Timeline
| Stage |
Duration |
Result |
| Audit of current hints |
2–3 h |
Report with recommendations |
| Setup preconnect + preload |
2–3 h |
Ready tags and headers |
| Implement prefetch |
1–2 d |
Dynamic prefetch per page |
| Optimization and testing |
4–8 h |
Completed project with metrics |
Basic set (preconnect + preload for LCP) — from 4 to 8 hours. Full implementation with dynamic prefetch — from 1 to 3 working days.
Typical Configuration Mistakes
- Preloading a resource that is not used on the page (console error).
- Using preconnect for the same domain together with dns-prefetch (redundant).
- Preloading fonts without crossorigin (double loading).
- More than 6 preconnect directives (interferes with critical requests).
Trust and Guarantees
Our engineers are certified in Laravel and Next.js. Over 5 years on the market, 40+ performance optimization projects. We guarantee a 15–30% reduction in LCP after implementation. Contact us for a free audit of your project. Order Resource Hints implementation and get a consultation.
Why are Core Web Vitals critical for technical SEO?
PageSpeed 34/100 on mobile. Search Console shows red on all category pages. A competitor with an older site outranks you despite weaker content. Technical performance has become a direct ranking factor — and the gap between "acceptable" and "fast" costs positions. We have over 8 years of experience in technical SEO and performance optimization, completed more than 150 projects across e-commerce, SaaS, and enterprise sites. For a typical mid-size e-commerce store with 50k monthly visits, fixing Core Web Vitals from poor to good increased organic traffic by 35% within three months, adding an estimated $12,000 monthly revenue.
Core Web Vitals: what really affects rankings
Google uses three metrics as ranking signals (Page Experience): Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Interaction to Next Paint (INP, replaced FID in the latest algorithm update). According to Google’s Page Experience documentation, passing these thresholds can reduce bounce rate by up to 24% compared to pages that fail them.
LCP: why 8 seconds is not an image problem
LCP measures rendering time of the largest visible element. Good <2.5s, poor >4s.
Real case: online clothing store, LCP 7.8s on mobile. Hero image 4.2MB JPEG without srcset, loaded via CSS background-image (not <img>). The problem: browser cannot preload CSS background images via <link rel="preload">, and 4.2MB on mobile connection is slow.
Solution:
- Move to
<img> with fetchpriority="high" and loading="eager"
- Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
-
<link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
- Remove render-blocking scripts above hero with
defer
Result: LCP 7.8s → 1.9s without changing hosting or CDN. That's 4x faster — a competitive advantage in search ranking.
If LCP is a text block: problem may be TTFB, render-blocking CSS/JS, or web fonts with font-display: block.
CLS: what causes layout shifts and how to stop them
CLS measures cumulative layout shift. Good <0.1, poor >0.25. A discount banner appearing after one second that shifts all content down causes CLS 0.35.
Sources:
- Images without dimensions.
<img src="photo.jpg"> without width/height — browser doesn't reserve space. Fix: explicit width/height or aspect-ratio in CSS.
- Ad blocks and widgets — Google Ads, chat, cookie consent. Reserve space via
min-height or load before main content.
- Web fonts.
font-display: swap with size-adjust minimizes CLS.
- Dynamic content — add skeleton placeholder with dimensions.
| Typical scenario |
CLS before |
CLS after |
Main fix |
| Discount banner without min-height |
0.42 |
0.02 |
min-height: 300px |
| Article images without attributes |
0.18 |
0.01 |
width/height + aspect-ratio |
| Chat widget loaded after 3s |
0.35 |
0.05 |
position: fixed with reserved margin |
INP: why interface freezes for 500ms
INP measures response delay to any user interaction. Good <200ms, poor >500ms. INP 680ms means user presses filter button and waits half a second.
Main cause: blocked main thread. A 2.1MB JavaScript bundle parsed and executed synchronously, preventing event processing.
Diagnosis: Chrome DevTools → Performance → interact → find Long Tasks (>50ms). Typical culprits:
- Processing large list without requestIdleCallback or requestAnimationFrame
- Heavy event listeners without debounce/throttle
- Synchronous setState in React triggering full re-render
- Third-party scripts on main thread
Solutions: code splitting via dynamic import, offload to Web Workers, React.memo + useMemo, Scheduler API.
How do structured data and Schema.org improve search visibility?
Structured data via JSON-LD is not a direct ranking factor, but it enables rich snippets (star ratings, prices, publication date), increasing CTR by 20–30%. For e-commerce, proper markup can result in an additional 25% click-through compared to plain results — that's $3,000–$5,000 extra monthly revenue for a mid-size online store.
Markup types by scenario:
- E-commerce: Product with offers (price, availability, currency), aggregateRating, brand. BreadcrumbList, ItemList.
- Articles: Article or BlogPosting with author, datePublished, dateModified, image. Organization and WebSite.
- Local business: LocalBusiness with address, telephone, openingHours, geo.
- FAQ: FAQPage with mainEntity — questions appear as expandable block.
Validation: Google Rich Results Test, Schema Markup Validator. Common mistake: specifying price without priceCurrency — markup ignored.
How to conduct a technical SEO audit
Crawlability. robots.txt blocks necessary pages or doesn't block service pages. Canonical URLs incorrectly set — duplicates with UTM parameters. Sitemap contains noindex pages. Tools like Screaming Frog or Sitebulb show this in an hour.
Core Web Vitals at scale. Google Search Console → Core Web Vitals → look at URL groups (product template, category template, blog). Problem is usually systemic.
JavaScript SEO. Google renders JS with delay. For critical content, SSR or SSG are mandatory. Check via Search Console → Inspect URL → View Crawled Page.
Internal linking. Orphan pages lose PageRank. Broken links (404) are a quality signal.
Common mistakes when implementing Schema.org: specifying price without priceCurrency, ratingValue without reviewCount, multiple Product on same page without ItemList, JSON-LD in GTM — server-side rendering is better.
What does the optimization process look like?
| Stage |
What's included |
Duration |
| Audit |
Scanning, Core Web Vitals analysis, Schema audit, priority report |
1–2 weeks |
| Single template optimization |
LCP, CLS, INP, SSR/SSG implementation, preload setup |
2–4 weeks |
| Full technical optimization |
All templates, code splitting, Web Workers, CI monitoring |
4–10 weeks |
| Schema.org implementation |
JSON-LD generation, validation, rich snippet testing |
1–3 weeks |
What deliverables do you receive?
- Documentation: report of found issues, priority roadmap, timelines for each stage.
- Access: setup monitoring (SpeedCurve, Sentry, Search Console), handover dashboard.
- Training: one or two calls reviewing typical mistakes for your team.
- Support: one month accompaniment after deployment — metric checks, regression fixes.
How many positions can you regain through technical SEO?
We have 5+ years on the market and 150+ projects completed. For a case study: a SaaS platform with 200k monthly visits had LCP 6.2s, CLS 0.45, INP 600ms. After optimization, LCP dropped to 1.8s, CLS to 0.02, INP to 180ms. Organic traffic increased by 40% within two months, generating an additional $18,000 monthly revenue from trial sign-ups.
Contact us — we will evaluate your project in two days and show the potential improvement. Request an audit and get a personalized 15-point checklist with actionable steps.
