Get a free Shopify store audit

Shopify Speed Optimization: Find and Fix What's Slow

A diagnostic guide to Shopify speed optimization: find which load phase is actually slow, then fix it, instead of a generic checklist.

Shopify Speed Optimization: Find and Fix What's Slow — ASSOSIATIX Journal

Shopify speed optimization starts with finding which load phase — server/Liquid rendering, render-blocking resources, or image delivery — is actually slow for real visitors, then fixing that specific cause instead of working through a generic checklist. Shopify already handles your CDN, compression, and basic image optimization, so most generic speed-test advice doesn't apply to a Shopify store.

What Shopify Already Optimizes for You

Before chasing a low PageSpeed or Lighthouse score, it helps to know what's already built into every Shopify store. Shopify's online store runs on a Cloudflare content delivery network, with assets served over HTTP/2, and sets browser caching for cacheable resources to one year — the maximum possible duration. CSS, JavaScript, and documents are gzip-compressed with Keep-Alive enabled, JPG images are auto-compressed and often served as WebP through the image CDN, and CSS/JS files are auto-minified when requested.

Shopify's performance work focuses on three Core Web Vitals: Largest Contentful Paint (LCP) for loading speed, Cumulative Layout Shift (CLS) for visual stability, and Interaction to Next Paint (INP) for how quickly the page responds to clicks and taps. Google uses these three as a ranking signal, which is part of why a low score is worth taking seriously rather than dismissing as a vanity metric.

That's why Shopify's own help center points to your theme, installed apps, and any manually added third-party code — not server configuration or CDN setup — as the biggest factors that actually move the needle. If a scanner tool tells you to "add a CDN" or "enable compression," that recommendation doesn't apply to a Shopify store; it's already handled. If your goal is simply to speed up your Shopify store without wasting time on inapplicable advice, start by ruling out everything in this list before touching anything else.

If you still can't explain a slowdown after ruling out the built-in optimizations, Shopify's own troubleshooting flow is to verify the issue first, then isolate whether apps, images, or scripts are the cause, before taking action.

Diagnose Before You Fix: Read Your TTFB, FCP, and LCP Gaps

Shopify's own Performance Team is explicit that debugging should start with real-user monitoring (RUM) data, not a lab-based testing tool. The method: pick one page type and one device, then read Time to First Byte (TTFB), First Contentful Paint (FCP), and Largest Contentful Paint (LCP) at the same percentile, using the Shopify Web Performance Dashboard or the free TREO Site Speed tool. Analyze page types and devices separately — a slow mobile product page and a slow desktop homepage are different problems with different fixes, so don't average them together.

Find the largest gap between consecutive metrics and match it to a pattern. A slow TTFB points to a server or Liquid rendering issue. A fast TTFB paired with a slow FCP points to render-blocking resources sitting between the HTML and the first paint. Fast TTFB and FCP but a slow LCP points to an image discovery or rendering issue. And if every gap is slow, look for one shared cause rather than planning three separate fixes.

This diagnostic step — reading the gaps before guessing at a fix — is also where a proper store optimization audit starts, because the fix that actually matters depends entirely on which phase is slow for your specific store.

If your gap analysis points to a slow TTFB specifically, we've broken down why Shopify treats TTFB as a Liquid rendering problem and what to prioritize fixing first.

Fix the Highest-Leverage Items First

Once you know which phase is slow, Shopify's own essential practices for themes give a short, specific list rather than a generic checklist. For LCP: never lazy-load the LCP image, mark it with fetchpriority="high", and don't hide it behind fade-in or reveal animations — all three delay the LCP event even after the image has finished downloading.

For TTFB: render essential content in Liquid and HTML rather than JavaScript, since Liquid renders server-side before the browser does anything, and avoid deeply nested Liquid loops — shopify.dev calls this the most common cause of high TTFB, because loops nested across products, variants, or options grow quadratically with catalog size. For FCP: load first-paint resources like stylesheets and fonts before content_for_header, since anything above it reaches the browser while Liquid is still rendering the rest of the page. Use preload sparingly — one or two resources at most — since overusing it competes with the browser's own prioritization.

Shopify's broader list of performance factors also flags page-level complexity directly: too many sections on a template, or large product collections without pagination activated, both lower web performance independent of any single code fix — worth checking before you go hunting for one root cause.

image_tag and image_url handle most of the mechanics automatically, but they don't catch every mistake — see the LCP mistakes Shopify's image_tag filter won't fix for what still needs manual attention.

Audit Apps with Shopify's Own Decision Framework

Apps are the other half of the equation. Shopify's own render-blocking-apps guidance gives a four-question framework for each app on your store: is it actively used, does it load on every page, is there a lighter native alternative, and can it be deferred rather than loaded immediately? Apps causing 500 milliseconds or more of blocking time are the priority for removal; apps under 100 milliseconds of blocking are low priority even if you'd rather not have them.

Common render-blocking culprits fall into predictable categories: chat widgets, review apps, email-capture popups, analytics and tag-manager scripts, A/B testing tools, and recommendation engines. None of these are inherently bad — the question is always whether a given one is pulling its weight for your store specifically.

Apps that fall in between — occasional use, partial async loading, or conditional load potential — are worth optimizing rather than removing outright: defer the script until after the page is interactive, load it only on the templates where it's actually needed, or use a lightweight facade that only fetches the real widget once a visitor interacts with it.

Third-party scripts add up: the Web Almanac's 2022 third-parties chapter found an average median blocking time of 1.4 seconds across the ten most common third-party scripts — a 2022 figure, not a current benchmark, but a useful reminder that app bloat compounds quickly once you stop auditing it.

Before assuming you need a review app's widget script at all, check whether it already writes to Shopify's standard reviews metafield namespace. If it does, you can render the star rating and count directly from product.metafields.reviews.rating.value.rating and .value.scale_max in Liquid, with no third-party script or render-blocking request at all.

If you want this audit and the fixes done for you, talk to our team.

Frequently asked questions

Does Shopify host images on a CDN automatically?

Yes. Every Shopify online store is served through a Cloudflare CDN over HTTP/2, and the image CDN automatically compresses JPGs and often serves them as WebP, so you don't need a separate image CDN or compression app.

What's a good Shopify Lighthouse score?

Shopify requires a minimum average Lighthouse performance score of 60 across the home, product, and collection pages for a theme to be accepted into the Shopify Theme Store — that's the only official target figure Shopify publishes for themes, and a reasonable baseline to check your own store against.

Does removing apps actually speed things up?

It can, depending on the app. Shopify's own framework prioritizes removing apps that cause 500 milliseconds or more of render-blocking time, while apps under 100 milliseconds are low priority. Note that uninstalling an app doesn't automatically remove its code from your theme files — you may need to clean that up separately.

Should I trust third-party Shopify speed-test recommendations?

Only selectively. Generic scanner advice about CDNs, server headers, or compression settings doesn't apply to Shopify, since those are already handled. Recommendations about your specific images, apps, and theme code are usually the relevant ones worth acting on.

What's the difference between TTFB, FCP, and LCP?

TTFB (Time to First Byte) measures how long the server takes to respond and, on Shopify, is driven mostly by Liquid rendering time. FCP (First Contentful Paint) measures when the first content appears, usually delayed by render-blocking resources. LCP (Largest Contentful Paint) measures when the largest visible element, typically a hero or product image, finishes rendering, and is one of Google's three Core Web Vitals along with CLS and INP.

Sources

Tell us what you're building.

Share a few details and we'll reply within 1–2 business days with questions, a scope and a quote.