JS & SSR Engineering Playbook Updated 2026-11-16 3 min read Google CrUX · Lighthouse · Core Web Vitals

Engineering Sub-1.5s LCP: fetchpriority, Preload Scanning & Image Pipelines

Adding loading="lazy" to above-the-fold hero visuals routinely adds 900ms+ to Largest Contentful Paint. Prioritize the exact LCP element in initial HTML.

Dmitry K., Technical SEO Lead · SEO Space

Indexation benchmark targets

Target CrUX LCP
<= 1.5s (p75 mobile)
Hero attribute
fetchpriority="high"
Hero lazy load
Strict loading="eager"

Breaking Down the Four Sub-Parts of Largest Contentful Paint

Most performance audits stare only at final LCP milliseconds without isolating where time disappears: Time to First Byte (TTFB), Resource Load Delay, Resource Load Duration, and Element Render Delay.

Even when an image weighs just 45 KB, hiding its URL inside a CSS background property, JavaScript carousel, or `loading="lazy"` attribute forces the browser to wait for full layout calculation before starting the download—creating massive Resource Load Delay.

  • Inspect CrUX field data and Chrome DevTools Performance panel to identify the exact LCP DOM node on mobile and desktop.
  • Keep the LCP image directly inside an HTML `<img>` element in initial SSR markup rather than CSS `background-image`.
  • Never apply `loading="lazy"` to hero images, product gallery main photos, or above-the-fold banners.

Using fetchpriority="high" & Responsive srcset Correctly

The browser preload scanner inspects raw HTML before CSS or JS executes. Exposing `<img fetchpriority="high" decoding="async">` or a matching `<link rel="preload" as="image" imagesrcset="...">` moves your hero visual ahead of secondary scripts and tracking pixels on the network waterfall.

Never over-preload: preloading 6 different fonts, icons, and secondary thumbnails steals bandwidth from the actual LCP element.

<!-- In <head> when hero image sits deeper in DOM -->
<link
  rel="preload"
  as="image"
  href="/media/hero-800.avif"
  imagesrcset="/media/hero-480.avif 480w, /media/hero-800.avif 800w, /media/hero-1200.avif 1200w"
  imagesizes="(max-width: 768px) 92vw, 640px"
  fetchpriority="high"
/>

<!-- In hero component -->
<img src="/media/hero-800.avif" width="800" height="520" fetchpriority="high" decoding="async" alt="Architecture overview" />

Eliminating Render Delay from Blocking Scripts & Fonts

Even if your hero image arrives in 200ms, the browser cannot paint it while synchronous CSS stylesheets or blocking `<head>` scripts freeze the main thread. Inline critical above-the-fold CSS, defer non-essential bundles, and keep `font-display: swap` active so text LCP elements render immediately.

LCP Sub-Part Target Share Primary Engineering Fix
TTFB < 40% (< 400ms) CDN edge HTML cache + HTTP/3 + Early Hints
Resource Load Delay < 10% (< 100ms) Remove lazy load, avoid JS-injected hero img
Resource Load Time < 40% (< 500ms) Serve AVIF/WebP sized via srcset + CDN
Element Render Delay < 10% (< 100ms) Remove render-blocking JS & oversized CSS

Need this indexation setup audited on your domain?

Send your website URL. We check raw HTML parity, log crawl hits, canonical discipline, and sitemap architecture manually within 24 hours.