How to Fix: Hero image not lazy

Hero image not lazy is an SEO check in the Image SEO category, and it is a medium priority with a direct line to your Core Web Vitals. It catches a subtle, common mistake: lazy-loading the one image you should be rushing to the screen. Get this wrong and you slow down the exact moment Google measures.

What this check actually looks for

It verifies that your above-the-fold hero image is not set to loading="lazy". Lazy loading is the right default for images further down the page — it saves bandwidth by deferring what the user has not scrolled to yet. But applied to the hero, the large image visible on first paint, it does the opposite of its job: it tells the browser to wait before fetching the very thing the visitor is waiting to see.

Why it matters for SEO

On most pages the hero image is your Largest Contentful Paint element, and LCP is a ranking-relevant Core Web Vital. Lazy-loading it forces the browser to first render the page, then discover the image is needed, then start the download — a chain of delays that can push LCP well past the 2.5-second “good” threshold. The fix routinely takes a second or more off LCP on image-led pages. This is one of those rare cases where a one-line change moves a metric Google actually counts.

Load order was always the whole game

I learned this discipline in the Flash era, building preloaders. A Flash movie could not show anything until enough of it had streamed in, so the first real engineering decision on every project was load order: what do we fetch first, what do we defer, and what does the user stare at while they wait? You put the hero art and the first interaction at the front of the queue and let the deep assets stream in behind. Getting the order wrong meant a beautiful site that showed a blank stage for four seconds — technically all there, practically a failure.

Lazy-loading a hero image is that same mistake in modern clothing: you have shoved the most important asset to the back of the queue. LCP is just the browser measuring the thing preloaders taught us to obsess over — how fast the important pixel arrives. The tools changed from a Flash preloader to fetchpriority, but the instinct is identical: fetch what the user is waiting for first, defer the rest, and never let the marquee asset wait in line behind a footer icon.

How to Fix This in WordPress

Difficulty Level: MEDIUM – This fix requires some technical knowledge or familiarity with WordPress settings and plugins.

Estimated Time: 30 min

1. Identify the hero — the large image at the top of the page — with a Lighthouse or PageSpeed Insights run, which will name your LCP element directly.
2. Remove loading="lazy" from that image. WordPress 5.5+ adds it automatically, so you may need to override it; many themes and page builders expose an “eager load” or “disable lazy load for this image” toggle.
3. Add fetchpriority="high" to the hero <img> so the browser fetches it ahead of lower-priority resources.
4. Keep lazy loading on for everything below the fold — that part is doing its job.
5. Serve the hero in a modern format (WebP/AVIF) at the right dimensions, then re-test LCP in PageSpeed Insights to confirm the improvement.

Recommended Tools & Plugins

• Yoast SEO – Comprehensive SEO plugin with built-in checks
• Rank Math – Feature-rich SEO plugin with detailed analysis
• Google Search Console – Free tool to monitor your site’s search presence
• SEO Roadmap – Complete SEO audit and action plan tool

Common Mistakes to Avoid

• Disabling lazy loading site-wide to “fix” the hero — that re-slows every below-the-fold image and hurts overall load.
• Removing lazy load but forgetting fetchpriority="high", leaving the hero to compete with scripts and fonts for bandwidth.
• A hero image that is enormous and uncompressed — eager-loading a 2 MB JPEG just delivers the problem faster.
• An aggressive optimization plugin that re-adds loading="lazy" to the hero after you removed it; check the rendered HTML, not just the setting.

This guide is part of the SEO Roadmap knowledge base – your complete resource for WordPress SEO optimization.