Your Shopify App Stack Is Costing More Than You Think. Here's How to Find Out.

1. What is Shopify app bloat and why does it happen?
2. How do I know if my store has an app bloat problem?
3. How do I know which apps are affecting my page speed?
4. What does app bloat actually cost per year?
5. How do I find and remove ghost code from my Shopify theme?
6. What's the difference between uninstalling an app and removing its code?

What is Shopify app bloat and why does it happen?

App bloat is what happens when a Shopify store accumulates more apps than it actively needs: each one loading its own JavaScript, each one billing monthly, most of them never revisited.

It rarely traces to one bad decision. A team adds an app to test a promotion. A previous agency installs three apps to solve one problem. Someone tries a subscription tool, decides against it, and moves on, but never gets around to uninstalling it. Eighteen months later, the store is carrying software nobody remembers approving.

The Shopify App Store lists thousands of apps, and the business model rewards adding apps, not removing them. Every developer wants an active subscription. No one in that chain has a financial reason to help you run fewer apps. So they compound. Many mid-market Plus stores end up with more apps installed than they use, and some of them overlap: two or three apps doing the same job in slightly different ways.

App bloat doesn't crash a store. It degrades it, one install at a time, until slow feels normal.

How do I know if my store has an app bloat problem?

A few signs are reliable enough to check yourself, before running any tooling:

• You can't name every app in your admin without opening the list. That's a common starting point for this whole exercise.
• More than one app does the same job. Two review apps. A bundle tool and a page builder both rendering upsells.
• You've uninstalled apps in the last year. Uninstalling doesn't always remove an app's code. Apps that wrote straight into your theme leave it behind, so past removals are a strong signal that ghost code may already be present. More on that below.
• Your monthly app bill has grown steadily with no feature you'd point to as the reason. That pattern points to accumulation, not investment.
• Page load feels slower than it did a year ago, and nobody changed the theme. Apps are a likely cause of that kind of drift.

Two or more of these, and the next step is finding out which specific apps are responsible.

How do I know which apps are affecting my page speed?

Not every app affects performance the same way, and the ones costing you the most speed aren't always the ones you'd suspect. The reliable way to check is Chrome DevTools' Network tab: load a product page in an incognito window, filter by JS, and look at what's requesting data before the page finishes rendering.

Three patterns show up consistently:

• Apps that inject scripts sitewide by default, even on pages where their functionality isn't used. A review widget loading on every page instead of only product pages is the classic example.
• Apps loading synchronously in the head, blocking the browser from rendering anything until that script finishes downloading and executing.
• Multiple apps loading their own version of the same library. jQuery is the classic example. Each one adds weight the browser processes independently.

The average storefront app now loads about 120KB of JavaScript, up from 95KB in 2024, and review apps typically add 50 to 500KB on their own. On a store running dozens of apps, a real share of that weight does nothing on the pages it loads on.

You can run this check yourself in about 30 minutes with nothing but DevTools open. It tells you where to look. Confirming what's safe to remove takes a separate dependency check.

What does app bloat actually cost per year?

Two costs are worth separating: what you're paying in subscriptions, and what slower pages are costing you in revenue.

Subscription cost. Add up your monthly app bills and multiply by 12. That's the subscription cost alone.

Performance cost.This cost hides inside your conversion rate. A slightly lower number gets attributed to ad creative or seasonality, when the actual cause is infrastructure. In an A/B test at the online fashion retailer Zalando, a 100 ms improvement in loading time led to a 0.7% uplift in revenue per session. That's one retailer's test, so I won't turn it into a dollar figure for your store.

The overlap tax. When apps in a stack do the same job, you're paying twice for the same job: once in subscription fees, once in the performance cost of loading both.

How do I find and remove ghost code from my Shopify theme?

Ghost code is what's left behind after an app is uninstalled: Liquid snippets and asset files an app wrote straight into your theme files during installation. Apps built on Shopify's newer app system (app blocks and app embeds) take their code with them when they're uninstalled, and Shopify removes an app's script tags too. Code written straight into theme files stays until someone removes it.

Finding ghost code reliably means checking two places:

1. Theme snippets and render tags. Search your theme code for {% render %} or {% include %} calls referencing snippet files tied to an app that's no longer installed. The snippet still loads, with nothing left to render.
2. config/settings_data.json. Old app configuration blocks frequently persist here even after the app itself is gone, sometimes still triggering asset loads.

Before deleting anything, confirm nothing else in the theme depends on that snippet or script. A five-minute mistake here can break a page that looked unrelated. Whether you do this yourself or bring someone in, that's the step worth being careful with.

What's the difference between uninstalling an app and removing its code?

Uninstalling stops the subscription and removes the app from your Shopify admin. Apps built on Shopify's newer app system (app blocks and app embeds) take their code with them. Apps that wrote straight into your theme files, which older apps did and developers often did by hand, leave those snippets and files exactly where they were.

This is the gap that produces ghost code. Cleaning up what was written is a separate, deliberate action that has to happen after the uninstall.

A store that's uninstalled ten apps over two years, but never gone back to clean up the code, is still carrying the performance cost of some or all of those ten while showing zero of them in the current app list. The admin looks clean. The theme isn't.