<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Zaid Ahmad</title>
    <description>The latest articles on DEV Community by Zaid Ahmad (@zaidahmaddev).</description>
    <link>https://dev.to/zaidahmaddev</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F780771%2F6ad832db-cd42-4fc1-9202-f9c1ebd4cdc9.webp</url>
      <title>DEV Community: Zaid Ahmad</title>
      <link>https://dev.to/zaidahmaddev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zaidahmaddev"/>
    <language>en</language>
    <item>
      <title>Why Your Shopify Store's LCP Is Still Over 3 Seconds (And the Fix Order I Use)</title>
      <dc:creator>Zaid Ahmad</dc:creator>
      <pubDate>Tue, 12 May 2026 20:09:30 +0000</pubDate>
      <link>https://dev.to/zaidahmaddev/why-your-shopify-stores-lcp-is-still-over-3-seconds-and-the-fix-order-i-use-2lib</link>
      <guid>https://dev.to/zaidahmaddev/why-your-shopify-stores-lcp-is-still-over-3-seconds-and-the-fix-order-i-use-2lib</guid>
      <description>&lt;p&gt;Most "Shopify speed optimization" advice tells you to compress images and &lt;br&gt;
call it done. After working on 50+ Shopify storefronts, I can tell you &lt;br&gt;
images are rarely the problem. The real LCP killers are usually further &lt;br&gt;
down the stack — and you have to fix them in the right order, or you &lt;br&gt;
waste hours on changes that don't move the needle.&lt;/p&gt;

&lt;p&gt;Here's the exact triage order I follow.&lt;/p&gt;

&lt;h4&gt;
  
  
  1. Audit, don't guess
&lt;/h4&gt;

&lt;p&gt;Before touching anything, run the page through PageSpeed Insights AND &lt;br&gt;
WebPageTest. PSI gives you the Core Web Vitals number Google cares about. &lt;br&gt;
WebPageTest gives you a waterfall that tells you &lt;em&gt;why&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;Look for these in the waterfall:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Render-blocking scripts in the &lt;/li&gt;
&lt;li&gt;Large hero images without &lt;code&gt;fetchpriority="high"&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Third-party scripts loaded synchronously (the usual suspects: chat 
widgets, review apps, analytics stacks)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  2. App audit — the 80/20 of Shopify performance
&lt;/h2&gt;

&lt;p&gt;Open your theme's &lt;code&gt;theme.liquid&lt;/code&gt; and search for every &lt;code&gt;&amp;lt;script&amp;gt;&lt;/code&gt; tag &lt;br&gt;
injected by an app. Each one is a candidate for removal or deferral.&lt;/p&gt;

&lt;p&gt;A pattern I see constantly: stores running 4–5 review apps, 2 popup &lt;br&gt;
apps, and 3 "AI personalization" apps. Each one loads ~50–200KB of JS &lt;br&gt;
on every page. That's your problem.&lt;/p&gt;

&lt;p&gt;What I actually do:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Uninstall apps that aren't generating revenue you can measure&lt;/li&gt;
&lt;li&gt;For apps you keep, ask the dev support team if they have an async or 
deferred loading option (about half do; you just have to ask)&lt;/li&gt;
&lt;li&gt;Move non-critical scripts to load on &lt;code&gt;requestIdleCallback&lt;/code&gt; or after 
user interaction&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  3. Fix the hero image properly
&lt;/h2&gt;

&lt;p&gt;If the LCP element is a hero image (it usually is on Shopify):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Add &lt;code&gt;loading="eager"&lt;/code&gt; and &lt;code&gt;fetchpriority="high"&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Serve it as WebP at the actual display dimensions (not the source size)&lt;/li&gt;
&lt;li&gt;Preload it: &lt;code&gt;&amp;lt;link rel="preload" as="image" href="..." fetchpriority="high"&amp;gt;&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This alone usually drops LCP by 600–1,200ms on a typical Dawn-based &lt;br&gt;
theme.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Liquid render time
&lt;/h2&gt;

&lt;p&gt;The often-missed one. If your collection or product page is slow even &lt;br&gt;
on a fast connection, your Liquid is doing too much work per request. &lt;br&gt;
Common culprits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Nested &lt;code&gt;for&lt;/code&gt; loops over &lt;code&gt;all_products&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Unbounded metafield iteration&lt;/li&gt;
&lt;li&gt;Custom snippets that re-render the same data&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Use the Shopify theme inspector to find slow blocks. Cache what you can &lt;br&gt;
in section data.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Fonts
&lt;/h2&gt;

&lt;p&gt;Self-host critical fonts. Use &lt;code&gt;font-display: swap&lt;/code&gt;. Subset to the &lt;br&gt;
characters you actually use. This is the boring last 10% that takes &lt;br&gt;
you from "fast enough" to "fast."&lt;/p&gt;




&lt;p&gt;What I don't recommend: the dozens of "speed optimization" apps in the &lt;br&gt;
Shopify App Store. Most of them just add another script to the page &lt;br&gt;
they claim to make faster. The fix is almost always removing things, &lt;br&gt;
not adding things.&lt;/p&gt;

&lt;p&gt;If you're stuck on a specific Shopify store and want a second pair of &lt;br&gt;
eyes, I write about this kind of work at &lt;a href="https://zaidahmaddev.com" rel="noopener noreferrer"&gt;zaidahmaddev.com&lt;/a&gt; &lt;br&gt;
— happy to take a look.&lt;/p&gt;

</description>
      <category>shopify</category>
      <category>javascript</category>
      <category>webdev</category>
      <category>performance</category>
    </item>
  </channel>
</rss>
