CriticalSpeedMeasured

Slow page load

Shoppers wait for the main content to appear, and some leave before they see a product.

Checked on: every page the audit scans · Zolvio’s check: “Slow page load time”

Why it costs you sales

Speed is the first thing a shopper experiences. Until the main image or headline has loaded there is nothing to decide on, and visitors on mobile connections feel every extra second.

Largest Contentful Paint (LCP), the moment a page’s main content appears, is one of Google’s Core Web Vitals, and Google treats 2.5 seconds or less as a good score.

How Zolvio detects it

Zolvio first reads what real visitors waited, from Google’s Chrome UX Report: the Largest Contentful Paint at the 75th percentile of the last 28 days, for the page itself when enough Chrome users visited it, otherwise for the whole store, on phones first, then on computers. A page is flagged when real visitors waited more than 2.5 seconds for its main content; over 4 seconds, Google’s line for a poor page, is critical. Google’s report covers Chrome on Android and on computers, not iPhones.

When Google has no real-visitor data for the store (too few Chrome visits), Zolvio loads each page on its own in a real browser and reads two timings: Largest Contentful Paint and the moment the page finishes loading. The page is flagged when its LCP is over 2.5 seconds or it takes more than 5 seconds to finish loading, and a slow reading is measured a second time, keeping the faster of the two, so a single hiccup doesn’t raise an issue.

Some A/B-testing apps (Absolutely, Google Optimize, VWO) hide the page until their script runs. The audit’s browser doesn’t load other companies’ files, so on a page with such a snippet it sees the page only when the snippet stops waiting: there only the load time is judged, not LCP.

This is a direct measurement, so it’s reported on every plan, including Free and audits with AI turned off. With AI review on, the AI agent also checks it against the audit’s evidence before it reaches your issue list.

How to fix it

  1. Run the page through Google PageSpeed Insights and note its LCP element, usually the hero image or the first product image.
  2. Make that element load early: don’t lazy-load it, and request it at the size it’s shown with Shopify’s image_url filter.
  3. Remove apps you don’t use, and check layout/theme.liquid for code left behind by apps you’ve uninstalled.
  4. Defer scripts and stylesheets that aren’t needed for the first screen, so the browser can draw the page sooner.

In Zolvio: on paid plans with AI turned on, the guided fix writes these steps for your own store and theme: where to click in Shopify admin or the theme editor, or which file to open, the line to find and the code to add. Each file opens in Shopify’s code editor. Zolvio never edits your theme: you make the change, then Verify fix checks your published theme for code changes (or you mark it fixed), and later audits confirm the problem is gone.

Common questions

Why does “Slow page load” cost a Shopify store sales?

Speed is the first thing a shopper experiences. Until the main image or headline has loaded there is nothing to decide on, and visitors on mobile connections feel every extra second. Largest Contentful Paint (LCP), the moment a page’s main content appears, is one of Google’s Core Web Vitals, and Google treats 2.5 seconds or less as a good score.

How does Zolvio detect “Slow page load”?

Zolvio first reads what real visitors waited, from Google’s Chrome UX Report: the Largest Contentful Paint at the 75th percentile of the last 28 days, for the page itself when enough Chrome users visited it, otherwise for the whole store, on phones first, then on computers. A page is flagged when real visitors waited more than 2.5 seconds for its main content; over 4 seconds, Google’s line for a poor page, is critical. Google’s report covers Chrome on Android and on computers, not iPhones. When Google has no real-visitor data for the store (too few Chrome visits), Zolvio loads each page on its own in a real browser and reads two timings: Largest Contentful Paint and the moment the page finishes loading. The page is flagged when its LCP is over 2.5 seconds or it takes more than 5 seconds to finish loading, and a slow reading is measured a second time, keeping the faster of the two, so a single hiccup doesn’t raise an issue. Some A/B-testing apps (Absolutely, Google Optimize, VWO) hide the page until their script runs. The audit’s browser doesn’t load other companies’ files, so on a page with such a snippet it sees the page only when the snippet stops waiting: there only the load time is judged, not LCP.

How do I fix “Slow page load” on Shopify?

Run the page through Google PageSpeed Insights and note its LCP element, usually the hero image or the first product image. Make that element load early: don’t lazy-load it, and request it at the size it’s shown with Shopify’s image_url filter. Remove apps you don’t use, and check layout/theme.liquid for code left behind by apps you’ve uninstalled. Defer scripts and stylesheets that aren’t needed for the first screen, so the browser can draw the page sooner.

Related

Documentation

  • How audits work — What an audit scans and how findings become issues.
  • Guided fixes — Step-by-step fixes written for your theme, with links into the code editor.
  • Workflows — Go from an issue to its heatmap and recordings before you change anything.