Skip to content

Technical SEO

How to Fix Largest Contentful Paint on Image-Heavy Pages

By Shayan Ahmad · · 6 min read

How to Fix Largest Contentful Paint on Image-Heavy Pages (WhiteLinko blog banner)

Largest Contentful Paint is usually the first Core Web Vital people notice, because it matches what they feel: the main thing on the screen took too long to appear. On image-heavy pages that "main thing" is almost always a photograph, a hero banner or a large product image. If LCP is poor, the usual causes are how that image is requested, how large it is, and what else is blocking it. This guide is for developers who need to get that first image on screen sooner.

Google currently treats an LCP of 2.5 seconds or less as good, and anything above 4 seconds as poor. Lab tests help you debug. Field data in Search Console tells you whether real users are still waiting.

Confirm What the LCP Element Actually Is

Do not assume it is the hero. On some templates the LCP element is a heading, a poster image, a late-loading carousel slide, or even a cookie banner. In Chrome, inspect a representative page, look at the LCP element in the Performance panel or a Lighthouse-style report, and note whether it is an image, text, or something injected after load.

Then check the same template on mobile. The LCP element often changes when the layout changes. A desktop hero may not be the largest element on a phone, and a mobile-only image may be the one that needs the work. Our free page speed check is a useful first look, but you should still confirm the element on the live template you are about to change.

If Search Console shows a whole URL group as poor, fix the template, not a single landing page. Product, category and article headers are the usual sources on image-heavy sites.

Request the Hero Image Earlier

The most common LCP failure on an image-heavy page is a late request. The browser spends the first moments on HTML, fonts, CSS or scripts, and only then discovers the hero image. By the time the file starts downloading, the budget is already nearly gone.

Preload the real LCP image

Once you know the LCP image URL, preload it in the head, with an appropriate imagesrcset and imagesizes when you serve responsive files. Preload the image that will actually be displayed on that device, not every art-directed variant. A preload that points at a desktop hero on a mobile template can waste bandwidth and miss the element that matters.

Make sure the preload matches the image the page will use, including the format. Preloading a JPEG and then rendering a WebP of a different URL means you have fetched the wrong file.

Do not hide the image behind CSS or JavaScript

Background images in CSS cannot be discovered as early as a normal img in the HTML, and they are a weaker LCP pattern. Carousels that wait to initialise before showing the first slide are worse. Render the first, visible image in the HTML, and treat anything after it as enhancement. If a slider is required, give the first slide a real image tag, the right dimensions, and no dependency on the slider script for its first paint.

Priority hints can help when used carefully. Mark the LCP image as high priority, and avoid giving that status to logos, icons and below-the-fold photos that then compete with it.

Serve a Sensibly Sized, Modern File

An early request still fails if the file is huge. Compress the image, serve a modern format such as WebP or AVIF where it is supported, and ship a size that matches the display width. A 3,000-pixel photo in a 400-pixel slot is still a common cause of poor LCP on product and magazine pages.

  • Generate responsive sources for mobile, tablet and desktop, and set sizes so the browser can pick one.
  • Trim decorative padding in the asset itself if a designer has exported a large canvas around a small subject.
  • Avoid transcoding on the fly in a way that delays the first byte of the image.
  • Cache the file so repeat views are cheap, but do not rely on cache alone to fix first-time LCP.

Do not lazy-load the LCP image. Lazy-loading is for content below the first screen. If the hero has loading="lazy", the browser may wait longer than it should before requesting it. That single attribute is a frequent regression after a theme or app change, and it is one of the first things we check in a technical SEO review of slow templates.

Get Other Resources Out of the Way

Even a well-prepared image can be delayed by what happens around it.

  • Render-blocking CSS and fonts. Inline or prioritise the CSS needed for the first screen, and load decorative fonts in a way that does not hold back a heading if the heading is the LCP element. If a font swap later changes the element, watch CLS as well as LCP.
  • JavaScript in the head. Heavy scripts that run before the image is requested push LCP out. Defer what you can, and keep tag managers from delaying the hero.
  • Server and TTFB. If the HTML itself is slow to arrive, the image request cannot start early. Caching, a nearby server or a lighter first response can matter as much as image work.
  • Cookie banners and overlays. If an overlay becomes the LCP element, you have a design problem as well as a speed problem. The main content should be the element you are measuring.

After you ship, re-test the template on a throttled mobile connection and wait for Search Console field data to move. LCP improvements on a template can take time to show in the report, but you should see a clearer first screen immediately if the fix is real. This kind of template-level work is also what we look for when comparing technical SEO approaches, rather than one-off landing page tweaks.

On stores, product images deserve the same treatment as marketing heroes, because they are often the LCP element on the URLs that make money. That is as much a selling issue as a ranking one, which is why it often sits beside web design and development work on new themes, not only in a later SEO pass.

FAQs

Should I preload every image in the hero area?

No. Preload the LCP image, and only the variant the current page will display. Preloading several large files competes for bandwidth and can make LCP worse, especially on mobile.

Is a CDN enough to fix LCP?

A CDN can help if the file or the HTML is slow to reach the user. It will not fix a late-discovered image, a lazy-loaded hero, or a 3,000-pixel asset in a small slot. Check discovery and file size first.

Why is LCP worse on mobile than on desktop?

The LCP element may be different, the image file may still be the desktop size, the connection and CPU are often weaker, and mobile layouts sometimes load extra components in the first screen. Always debug the mobile template separately.

Can I ignore LCP if the rest of the page is fast?

Not if field data is poor. LCP is about the first main content, which is what many users judge the page by. A fast footer does not help someone staring at a blank hero.

Want an Image-Heavy Template Checked?

If your product, blog or campaign templates fail LCP and you are not sure whether the problem is preload, sizing or something blocking the request, a technical pass will isolate it quickly. Start with a free SEO audit and we will tell you what is holding the largest element back.

  • lcp
  • core web vitals
  • images
  • page speed
  • technical seo

Have a question about this for your own site?

A 15-minute call is usually enough to tell whether it applies to you and what to do first.

Book a 15-min callGet My Free SEO Audit

Related posts

Core Web Vitals Explained for Business Owners (WhiteLinko blog banner)

Technical SEO

Core Web Vitals Explained for Business Owners

LCP, INP and CLS explained in plain English for business owners: what each Core Web Vital measures, why it matters for sales, and how to read a report.

All blog posts →

Talk to WhiteLinko

Want this applied to your site?

Book a 15-minute call to talk through your goals, or start with a free SEO audit: a prioritised list of fixes, reviewed by a specialist.

Free PDF · 2026 edition

The WhiteLinko SEO Checklist

Six pages of tick boxes: technical, on-page, content, local, links, AI search and GA4.

Get the checklist
Free SEO Audit