Shopify Speed: Rebuilding a Plus Theme for Core Web Vitals
App bloat is the silent conversion killer. How an enterprise Shopify Plus theme was rebuilt for speed. The audit, the removals and the architecture behind it.
An enterprise Shopify Plus brand asked us why conversion kept sliding despite steady traffic. The first Lighthouse run answered it: a mobile performance score deep in the red, a Largest Contentful Paint well outside the good threshold, and a large installed-app footprint, most of which injected JavaScript into every page load.
The app-bloat audit
Every Shopify app you install can add script tags, stylesheets and third-party calls to your storefront. Many keep injecting code even after you stop using them. We audit each app against one question: does the revenue this app produces exceed the conversion cost of the weight it adds? For most of the apps on this store the honest answer was no. Their functionality was either unused or replaceable with a few lines of Liquid.
The rebuild, in order
- Rebuilt the theme on clean OS 2.0 architecture: sections and snippets with zero dead code carried over.
- Replaced app functionality with native Liquid where feasible: badges, size guides, simple upsells rarely need an app.
- Deferred every non-critical script; inlined critical CSS; converted the media pipeline to responsive WebP.
- Rebuilt the GTM datalayer with a documented GA4 event schema, so analytics stopped depending on five overlapping pixel apps.
Speed is a conversion feature, not an IT metric
Every large-scale study agrees: mobile conversion drops measurably with each additional second of load time. But the mechanism matters more than the statistic, slow stores feel untrustworthy at the exact moment a buyer decides whether to type in a card number. The improvement here required no persuasion tactics at all. The store just stopped getting in its own way.
How to know if this is your problem
- Run PageSpeed Insights on your top product page (not your homepage), mobile score below 50 means real revenue is leaking.
- Count script tags in your page source. Above 30 is common; above 50 is an emergency.
- Check Core Web Vitals in Search Console: failing CLS or LCP costs you both conversions and rankings.
A rebuild sounds drastic, and it is the kind of project that has to be justified against the specific losses it recovers rather than against a benchmark. We do not publish the before-and-after figures from this engagement: those are released only with the client’s permission and alongside the measurement conditions that make them readable. What is publishable is the method, which is above.