Core Web Vitals for Shopify: Complete Guide (2026)

Shopify stores pass Core Web Vitals more often than most sites. What fails on yours, and what to switch in the theme editor, the apps and the theme code.

Arjen Karel
Updated · 11 min read
Share

Core Web Vitals on Shopify in short

Shopify runs the server, and according to the State of Web Vitals 84.8% of Shopify stores pass the Core Web Vitals on mobile; across all sites it is 69.7%. Stores that fail usually fail on what was added to them. Put the hero banner in the first section, switch off App embeds you don't need and reserve space for app blocks.

How do Shopify stores compare on Core Web Vitals?

Shopify stores do better than the average site on every metric, and the lead is smallest on INP. The State of Web Vitals, a benchmark built on Chrome's real-user data, compares the 9,826 Shopify stores in its crawl with all 242,967 sites on phones, for LCP (when the largest image or text appears), INP (how fast a tap gets a response) and CLS (how much the page jumps):

On phones Shopify All sites
Pass all three 84.8% 69.7%
Good LCP 95.2% 81.9%
Good INP 93.0% 91.8%
Good CLS 94.0% 88.9%
Good TTFB 95.7% 59.2%

The TTFB (Time to First Byte, how fast the server answers) is good because Shopify runs the servers, and it is where Shopify and WordPress differ most: only 32.1% of WordPress sites reach a good TTFB, and 62.6% of WordPress sites pass all three. A WordPress site usually fails on its server, and Core Web Vitals for WordPress starts there. A Shopify store that fails, fails on the theme and the apps. The figures for every metric are on the Shopify page of the State of Web Vitals.

Where does the Shopify admin show your Core Web Vitals?

Shopify's Web performance dashboard shows LCP, INP and CLS from your own store's visitors at the 75th percentile, rated Good, Moderate or Poor against the Core Web Vitals thresholds. Its summary of the last 30 days sits on the Online Store > Themes page, and the full Web performance reports are under Analytics > Reports, split by page type, page URL, device and over time. The dashboard replaced the old Speed score, a lab number, in 2024.

Google ranks on its own field data, collected from Chrome users only, so its numbers can differ from Shopify's. Search Console's Core Web Vitals report groups your URLs by Chrome's field data (CrUX) over the last 28 days, and PageSpeed Insights shows the same data for one URL at the top of the page. "Core Web Vitals Assessment: Failed" there means at least one of LCP, INP and CLS missed its threshold at the 75th percentile. The Lighthouse score below it is a single lab test; the assessment is your visitors' field data.

Two causes are common on failing stores: apps that inject scripts on every template, and a hero slider that hides the LCP image from the browser until the slider script runs. To get a failing Shopify store to pass, improve it in this order:

  1. LCP: the hero image on the home, collection and product pages.
  2. LCP and INP: the apps, and the files each one adds to every page.
  3. INP: the theme's click code for add to cart, the cart drawer and the filters.
  4. CLS: app blocks, images and fonts that move the page.

How to pass the Core Web Vitals gives the order for a site on any platform.

What does Shopify handle, and what is yours to fix?

You can't change the Shopify platform itself, but the theme, the apps and the scripts they add are yours, and on a failing store that is where the problems are.

  • Shopify's: the server and its page cache, the CDN, HTTP/3, compression of the HTML, 103 Early Hints (the head's stylesheets and scripts start downloading before the HTML arrives), and the image format: your images go out as WebP.
  • Yours: the theme and its code, the apps with their embeds and blocks, the sections and images you add, scripts pasted into the theme, and your redirects.

Every theme prints {{ content_for_header }} in its head. Shopify fills it with its own scripts and those of your apps, and you can't edit it. Those scripts load async or deferred, so none of them blocks the first paint. On all five stores I checked, it also added one render-blocking stylesheet for accelerated checkout: that is the platform, so leave it.

A slow server response on Shopify comes from redirects, or from slow Liquid (Shopify's template code) in the theme and the snippets apps add to it: Shopify Theme Inspector for Chrome shows a developer which part renders slowly, and Time to First Byte (TTFB) has the rest.

Without a developer you can change the App embeds, the order of the sections, the theme settings and the images you upload. Code in the theme takes a Shopify developer: deferring the scripts written into a normal theme is half a day to a day of work, and trimming the theme's own stylesheet takes several days.

Why is the hero image late on Shopify (LCP), and how do you fix it?

The browser starts the hero image late on Shopify when the banner isn't in the template's first section, when the theme lazy-loads it instead of eager loading, or when a slider or an app builds it with JavaScript. Dawn, Horizon and the themes built on them give the image in the first section fetchpriority="high" and leave it out of lazy loading, so make the image banner or slideshow the first section.

According to the State of Web Vitals, the load delay, the wait between the HTML arriving and the browser requesting the image, is the largest of the four LCP parts on 66.7% of Shopify stores with an image LCP, against 21.9% of all sites. The server's part is the largest on only 13.7%. On 31.0% of Shopify stores the LCP image has loading="lazy".

Bar chart of which of the four LCP parts is the largest on phones, Shopify stores against all sites, State of Web Vitals November 2026: load delay 66.7% against 21.9%, time to first byte 13.7% against 67.6%, render delay 16.7% against 8.4%, download of the image 3.0% against 2.1%.

The largest LCP part on phones, share of sites with an image LCP. Data: State of Web Vitals (corewebvitals.io)

In the theme editor, without code:

  • Section order: drag the image banner or slideshow to the top of the home page and of each landing page template.
  • A theme section for the hero: a hero or slider that an app builds with JavaScript starts late whatever the theme does. Use the theme's own banner section instead.
  • Animations: under Theme settings > Animations, Dawn's "Reveal sections on scroll" starts its fade from almost visible, which is fine. A theme whose reveal starts fully transparent holds the downloaded image back until the fade ends: switch the setting off and measure LCP again. LCP breakdown shows that wait as render delay.

For a developer: Dawn's main product photo has no fetchpriority. In snippets/product-thumbnail.liquid, add fetchpriority: 'high' to the image_tag when lazy_load is false, and check it again after a theme update, which can replace the file. In other themes, set the priority on the section's place (section.index == 1); the Liquid is on LCP request discovery. A hero set as a CSS background becomes an <img> through image_tag in a theme section.

The trap is image_tag's preload: true. Shopify sends at most ten preloads per page, its own preloads of the scripts and stylesheets in your head take the first places, and an image preload comes last, so on a theme with many head files it is the first to be dropped. Shopify's own advice is one or two preloads at most, and the first section's image doesn't need one.

The file itself is rarely the problem on Shopify: the CDN serves WebP at the width the theme asks for. Upload photos 2,048 to 2,560 pixels wide; Improve image delivery has what Shopify does with them.

Which apps and third-party scripts slow down your Shopify store?

An app slows every page its embed loads on: the embed adds a script and often a stylesheet to each of those pages, and that script also listens to clicks that have nothing to do with the app. Those scripts compete with the hero image for LCP and with your add to cart for INP. Switch the App embeds off one at a time and test the slow page again after each one: the app that matters is the one whose switch changes the result.

The App embeds are under Online Store > Themes > Customize, in the left bar. Save after each switch, then test in PageSpeed Insights or watch your field data.

Shopify theme editor, App embeds panel: the CoreDash Tracking app embed switched off

App embeds in the theme editor: one switch per app, for the whole theme.

  • App blocks you placed in a section stay on when the embed is off: remove them in that section.
  • Uninstalled apps can leave code in theme.liquid and the snippets. Search the theme code for the app's name, or ask its maker to remove it.
  • For a developer: in the network waterfall, /cdn/shop/t/ in a file's URL is your theme and /extensions/ is an app, with its name in the path. Render-blocking requests goes through the files apps put in the head.

According to the State of Web Vitals, Shopify stores that load 2 to 4 third-party providers pass all three metrics at 94%, and stores with 9 or more at 78%. That is a correlation. The number of apps matters less than which files each app adds to which pages: a review app whose script loads only on product pages adds nothing to your home page.

Speed apps that delay every script until the visitor's first tap or scroll raise the Lighthouse score, since Lighthouse loads the page and never taps it. Your visitor's first tap then waits while all of those scripts download and run, and that tap counts in INP. Leave them off.

What makes add to cart and filters slow on Shopify (INP)?

According to the State of Web Vitals, 93.0% of Shopify stores have a good Interaction to Next Paint (INP) on phones, Shopify's lowest pass rate of the three. A slow tap on Shopify runs the theme's own click code (add to cart, the cart drawer, the filters or the variant picker) together with every app script that listens to the same click.

The slow click I see most often is a product filter. Switch the App embeds off one at a time in the theme editor and repeat the slow tap after each one, to see how much of it the apps add. Find and fix INP walks through finding the slow tap and recording a trace of it. The settings inside an app rarely change what runs in a click. The theme's code decides that: what add to cart does, when the cart drawer renders and which app scripts it loads.

CoreDash table Interaction to Next Paint by Attribution Element (INP) on mobile for acme-pagespeed.com, sorted by sessions: button.product-form__submit (add to cart) 412 ms with a yellow dot (4,836 sessions), facet-filters-form input (the product filter) 538 ms with a red dot (3,214), variant-radios label 226 ms (2,105) and button.quantity__button 248 ms (1,742) with a yellow dot, header-drawer summary 164 ms with a green dot (1,388).

INP on phones per clicked element in CoreDash on acme-pagespeed.com: add to cart (product-form__submit) and the collection filter (facet-filters-form) at the top. Start there.

For a developer: the add-to-cart handler updates the button and the cart count first and does the rest afterwards (yield to the main thread). The cart drawer re-renders only the sections that changed instead of half the page. Hidden filter panels and drawers are built when they first open.

What causes cumulative layout shift (CLS) on Shopify?

Cumulative layout shift on a Shopify store usually comes from app blocks that fill in after the page loads (review stars, announcement bars, upsell widgets), from an image a custom section or app prints without a size, and from the font swap. The theme's own images rarely move: Shopify's image_tag, the tag themes use to output images, writes their width and height. Aim for a CLS of 0.

  • App blocks: give the block's container the height the widget ends up with, in Theme settings > Custom CSS or in the section's own Custom CSS.
  • Bars: an announcement or promo bar that a script inserts at the top pushes the whole page down. Use the theme's announcement bar section, which is in the HTML from the start.
  • Images: a custom section that writes its own <img> needs width="{{ image.width }}" height="{{ image.height }}", or image_tag.
  • Fonts: pick fonts in Theme settings > Typography, which serves them from your store's own domain; a system font never swaps. A fallback font sized to the web font's measurements (metric overrides) goes in the theme's stylesheet under Edit code, where a theme update can remove it. The CSS for it is on Font display.

Every cause with its code: Cumulative Layout Shift (CLS).

Does your Shopify theme decide your Core Web Vitals?

Yes, the theme decides more than any app setting: how the hero loads, what add to cart runs, and how much CSS and JavaScript every page carries. Shopify's own Dawn and Horizon load the first section's image early.

Before you buy a theme, look at its field data. ThemeVitals shows real-user Core Web Vitals per Shopify theme, for phones and desktop, from the stores that run it. The Theme Store asks for a Lighthouse score of 60, a lab test on Shopify's own benchmark store that says little about your visitors.

Switch themes when the theme's own code is the cause: if a slow page stays slow with every App embed off and its app blocks removed, it is the theme. A theme update arrives as a draft copy that keeps your code edits unless they conflict with the new version, so some changes have to go in again. Check the hero and the cart drawer in the draft before you publish it.

How do you check a Shopify fix, and when does it show?

Run Lighthouse again in PageSpeed Insights, on the mobile tab, for one page of each page type you changed. Then watch your field data: the over-time view of Shopify's Web performance reports, filtered on that page type, shows the change after a day or two, because its data can be up to 36 hours late. Search Console takes up to 28 days to show it in full.

CoreDash, which installs on Shopify as an app embed, shows LCP per page and INP per clicked element as soon as new visitors come in, so you see whether the slow tap went away.

Check again after every app install, theme update and campaign: a sale banner or a holiday popup is new code on every page. When the over-time chart jumps on one day, look at what was installed or changed that day.

The theme editor can't fix a cart drawer that re-renders half the page on every tap, an app your store needs whose script runs on every click, or a hero the theme sets as a CSS background. Who can fix them? A Shopify developer, once a performance specialist has found which one slows your store. When your store keeps failing on mobile with the hero in the first section, the apps checked and the theme settings right, a power hour finds the cause and gives you what to ask your developer for.

About the author

Arjen Karel is a web performance consultant and the creator of CoreDash, a Real User Monitoring platform that tracks Core Web Vitals data across hundreds of sites. He also built the Core Web Vitals Visualizer Chrome extension. He has helped clients achieve passing Core Web Vitals scores on over 925,000 mobile URLs.

Arjen Karel

Need a faster site?

I'm Arjen, and I've been fixing slow sites for 17 years. If you're running into issues you can't fix yourself, send me your URL and let's have a chat.

Send me your URL
Arjen Karel
Arjen Karel, Web performance consultant since 2009

Why isn't our fix working?

Sometimes the CDN still serves the old HTML, or the fix went into the desktop template and mobile uses another one. Send me your URL and the problem, and I reply with a few times. I check your field data first, then we spend one hour on your site, and within a day you have my notes in writing. €350 excl. VAT.

Send me your URL

No developer to build the fix? I do the work myself, on a copy of your site.

Arjen KarelCore Web Vitals still red on mobile?Send me your URL