Technical SEO & AI Search

Core Web Vitals for Shopify: What Actually Moves LCP

Why Shopify product and collection pages fail LCP, the fixes that move it (discovery, priority, sizing, render delay) and how to diagnose each template.

TL;DR
  • On most Shopify stores, the LCP element is the hero or main product image, and the biggest delay is usually how late the browser starts downloading it, not the file size.
  • The fixes that move LCP are making the image discoverable in the HTML, never lazy-loading it, giving it high priority and sizing it correctly with Shopify's image filters.
  • Judge results on field data from real visitors, template by template, and expect changes to take weeks to show in Google's reports.

How does Google measure Core Web Vitals on a Shopify store?

Core Web Vitals are three metrics Google uses to describe real-user page experience. Each has a “good” threshold:

Metric Good What it measures Typical Shopify culprit
Largest Contentful Paint (LCP) 2.5 s or less When the main content appears Hero or product image found late or lazy-loaded
Interaction to Next Paint (INP) 200 ms or less How fast the page responds to taps and clicks App scripts, heavy filters, variant pickers
Cumulative Layout Shift (CLS) 0.1 or less How much content jumps while loading Late banners, review widgets, images without dimensions

Google assesses each metric at the 75th percentile of real visits, so three out of four visits need to hit the threshold. That field data comes from the Chrome User Experience Report and covers a rolling 28-day period. You’ll see it in Search Console’s Core Web Vitals report and at the top of PageSpeed Insights.

Shopify also has its own web performance reports on the Themes page of the admin. They’re based on your visitors’ real sessions and replaced the old speed score in 2024. Use them to spot trends. Use Search Console to see which URL groups Google considers poor.

Lab tests, such as the Lighthouse score in PageSpeed Insights, run one simulated visit. They’re good for diagnosing a problem. They aren’t what Google uses to assess your pages, so a lab score of 45 with passing field data isn’t an emergency, and a lab score of 90 with failing field data is.

Why is LCP the hardest metric to pass on Shopify?

On a typical store, the LCP element is an image: the hero banner on the home page and collections, and the main product image on product pages. Product pages are where buying happens, and they’re often the slowest template, so start there.

Google breaks LCP into four parts:

  1. Time to first byte (TTFB): until the browser receives the first byte of HTML.
  2. Resource load delay: from TTFB until the browser starts downloading the LCP image.
  3. Resource load duration: downloading the image itself.
  4. Element render delay: from download finished until the image is actually painted.

The instinct is to compress images. But Google’s Chrome team analyzed field data and found that the median site with poor LCP spends almost four times as long waiting to start downloading the LCP image as it does downloading it. On Shopify, that waiting usually comes from theme and app choices, which is good news, because those are things you control.

What actually moves LCP on Shopify?

Work through these in order. The first three address load delay, which is usually the biggest part.

1. Make the LCP image discoverable in the HTML

The browser’s preload scanner reads the HTML and starts fetching images early, but only images it can see. It misses:

  • Images injected by a JavaScript slider or carousel after the page loads.
  • Lazy-loading libraries that swap src for data-src, hiding the real URL.
  • Hero images set as CSS backgrounds.

Render the first hero slide or main product image as a normal <img> with a real src in the section’s Liquid. If your hero is a slideshow, consider whether a single static image would serve the page better.

2. Never lazy-load the LCP image

Shopify’s image_tag filter handles this by default. It sets loading="eager" for images in the first three sections of a template and loading="lazy" further down. Shopify’s own guidance is not to set the loading attribute when you rely on that default.

Problems appear when a theme customization or app hard-codes loading="lazy" on every image, including the first one. Search your theme code for it, and check sections added by page builders.

3. Give the LCP image high priority

Add fetchpriority="high" to the main product image and the first hero image, so the browser moves them ahead of less important downloads. Shopify’s performance guidance uses fetchpriority: 'high' with image_tag for the first section’s LCP image.

The image_tag filter also has a preload parameter, which adds a preload hint in the HTTP Link header. Shopify says to use it sparingly, for above-the-fold images only. Preloading several images makes them compete with each other.

4. Size the image correctly

Pipe images through image_url and then image_tag rather than building URLs by hand. That combination generates a srcset with several widths, adds width and height attributes from the aspect ratio (which also prevents layout shift) and lets Shopify’s CDN serve WebP or AVIF automatically when the browser supports them.

Two consequences:

  • Converting product photos to WebP before upload rarely helps, because the CDN already negotiates the format.
  • The sizes attribute matters. Without it, a phone may download an image sized for a desktop screen. Set sizes to match how wide the image is actually displayed.

5. Cut element render delay

The image can finish downloading and still wait to paint. Common causes:

  • Render-blocking CSS and JavaScript in theme.liquid, including app embeds that load in the head.
  • Testing or personalization scripts that hide the page until they run, often used for A/B testing.
  • Fade-in animations on the hero that delay its first paint.

Audit app embeds under Online Store > Themes > Customize > App embeds, and remove what you no longer use. Uninstalling an app doesn’t always remove code it added to the theme, so check for leftovers.

6. Then look at TTFB

Shopify hosts and caches your storefront, so TTFB is less in your hands than on WooCommerce or Magento. What you can influence: heavy Liquid logic (large loops over collections or metafields), redirect chains from ad and email links, and how many apps alter the page server-side. Check TTFB by country in your field data if you sell internationally.

How do you diagnose LCP on a single template?

A worked example of the process, using a product page:

  1. Pick the URL group. In Search Console’s Core Web Vitals report, open the “poor” or “needs improvement” group for mobile and note a sample product URL.
  2. Check field data. Run that URL in PageSpeed Insights. Confirm LCP is the failing metric in the field section, not just the lab score.
  3. Find the LCP element. In the lab diagnostics, PageSpeed Insights names the element. On a product page it should be the main product image. If it’s a cookie banner or a promo bar, that’s a finding in itself.
  4. Read the breakdown. Record the page load in the Performance panel of Chrome DevTools and open the LCP breakdown insight to see which of the four subparts is largest.
  5. Match the subpart to a fix:
Largest subpart Likely Shopify cause Fix
Resource load delay Image injected by JavaScript, lazy-loaded or a CSS background Static <img> in HTML, eager loading, fetchpriority="high"
Resource load duration Oversized image, missing sizes, too many competing downloads image_url + image_tag with correct sizes; fewer preloads
Element render delay Render-blocking scripts, anti-flicker snippets, animations Defer or remove app embeds; drop fade-ins on the hero
Time to first byte Redirect chains, heavy Liquid logic Link directly to final URLs; simplify section loops
  1. Ship, then wait. Field data covers 28 days, so a fix shows up gradually. Validate the fix in Search Console once the data has caught up.

What about INP and CLS?

These matter too, and the causes on Shopify are predictable.

INP usually suffers from third-party JavaScript: review, chat, upsell and tracking apps all compete for the main thread. Variant pickers and collection filters that re-render large parts of the page are the other common source. Every app you remove helps.

CLS comes from things that appear late and push content down: announcement bars inserted by scripts, review stars loading after the price, and images without dimensions. Reserve space for widgets in CSS, and use image_tag so width and height are set.

Both affect what shoppers feel, which shows up in conversion rate as well as in search. Treat speed as part of technical SEO and conversion work at the same time.

What should you check first?

  • [ ] Search Console shows which mobile URL groups fail, and on which metric.
  • [ ] The LCP element on product, collection and home templates is identified.
  • [ ] The LCP image is a plain <img> in the HTML, not injected by JavaScript or set as a CSS background.
  • [ ] Nothing hard-codes loading="lazy" on the first image of a template.
  • [ ] The main product and hero images have fetchpriority="high".
  • [ ] Images use image_url and image_tag with an accurate sizes attribute.
  • [ ] Unused app embeds and leftover app code are removed.
  • [ ] Results are checked in field data after the 28-day window, not in a single lab run.

FAQ

Do Core Web Vitals affect Shopify rankings?

They’re part of the page experience signals Google uses, but relevance and content quality matter more. Passing won’t rescue a weak page, though for competing pages of similar quality it can help. The stronger case is commercial: slow product pages lose shoppers.

Should I install a Shopify speed optimization app?

Be careful. Some apps add their own scripts or lazy-load every image, including the LCP image, which can make things worse. Check exactly what an app changes, and test field data before and after.

Do I need a headless storefront to pass Core Web Vitals?

Usually not. Most Shopify themes can pass with the fixes above. A headless build gives you more control but adds cost and complexity, so weigh it carefully. We cover that decision in headless commerce: who needs it.

Turn this into a plan for your store

The Free Profit Audit scans your store, sizes your biggest profit leaks and builds a 90-day plan.

Free Profit Audit