There is no right number. An app is one too many when you cannot say, in one sentence, what job it does, what it bills every month, and what it adds to the page a customer is trying to load. Stores collect apps the way a kitchen drawer collects gadgets: each one solved a problem on the day it was installed, and nobody went back to check whether the problem is still there.
Here is what an app actually costs, which ones earn their place, and how to audit the list in an afternoon.
What does an app actually cost?
More than the fee. Each app on a store carries four costs, and only one of them shows up on an invoice.
The monthly charge. App fees are billed through Shopify alongside your plan, which makes them easy to stop noticing. A store that started with two apps and now has fourteen has added a second subscription line it never decided on. How that adds up over a year, next to hosting and the plan itself, is in what a website costs per year.
Speed. An app that shows anything on the storefront loads its own script to do it. Shopify's help page "Improving your online store performance" is direct about this: "Too many apps loading assets on your storefront can slow performance. Review your installed apps and remove any that aren't essential for sales." Many of those scripts load on every page, including the pages where the app does nothing. The other reasons a site is slow are in why your website is slow.
Leftover code. The same Shopify page says: "Uninstalling an app doesn't automatically remove its code from your theme. You might need to contact the app developer for complete removal instructions." An app you removed a year ago can still be loading a script or a stylesheet on your product page. Removing the app stops the bill. It does not always stop the weight.
Dependency. The developer sets the price and can raise it. They decide whether the app keeps working with your next theme. And the data the app holds, whether reviews, loyalty points or subscription contracts, lives in their database, not yours. Who owns your website applies to the apps inside it too.
Which apps earn their place?
The ones that would leave a hole tomorrow if they were gone, and where you can name the hole.
Keep an app that connects the store to a system you actually use: your accounting software, your shipping labels, your email tool. Keep an app your staff open every week. Keep an app that holds customer data you cannot rebuild, such as collected reviews or running subscriptions, at least until you have exported it and know where it is going.
Look hard at everything else. An app installed for a campaign that ended in the spring. An app that shows trust badges or a countdown timer. Two apps doing the same job because the second was installed before anyone remembered the first. And the largest group: apps installed to add a feature the theme did not have at the time, and which the theme now has.
That last group deserves a check before anything is bought. Themes built for Shopify's Online Store 2.0 framework let you add sections and blocks on any page, and a job that needed an app on an older theme may now be a section or a setting. If you moved to a new theme and kept your old app list, check for that overlap first.
Why does a store with twenty apps feel slow?
Because the scripts add up on the page that matters most.
Your product page is where a customer decides. On a store with a long app list, that page is carrying the reviews widget, the wishlist, the size chart, the recommendation carousel, the sticky add-to-cart bar, the pop-up, the chat and the currency converter. Each one is small on its own. Together they are the reason the "Add to cart" button takes a beat to respond on a phone, and a customer on a phone does not wait to find out why.
Shopify's own guidance puts the decision in plain terms: "Evaluate your installed apps and third-party code to ensure that they're creating enough value to offset any potential performance losses." That is the whole test. Not "is this app nice to have", but "is what it adds worth what it costs on the page".
Not every app is built the same way, and it is worth knowing which kind you have. Newer apps built with Shopify's theme app extension framework add their pieces as blocks you place in the theme editor. Shopify's developer documentation, "About theme app extensions", says these apps "don't edit theme code, which decreases the risk of introducing breaking changes to the theme". The block loads where you put it, and removing the app removes the block. Older apps that wrote code into the theme files themselves are the ones that leave things behind. In the theme editor, the newer kind shows up as blocks you can add to a section, or as toggles in the "App embeds" panel. An app that is in neither place yet still shows on the storefront is probably the older kind.
What happens when you uninstall one?
The fee stops. Two other things need checking before you press the button.
The code. After removing an older app, look at the theme, or have someone look at it, for the snippet it left. Shopify's advice is to ask the developer for the removal steps. This is the step that gets skipped, and it is how a store ends up loading more scripts than it has apps.
The data. Export first. Reviews go out as a spreadsheet; check that the format is something another app or your theme can take back in. A subscriptions app is the one to be most careful with, because customers' recurring orders run through it, so ask the developer what happens to active subscriptions before you touch anything. A loyalty app holds points that customers believe they own, and removing it without telling them is a customer-service problem, not a technical one.
Then test checkout, on a phone, as a customer. Add a product, apply a discount code, get to the payment page. Do it after every removal, not once at the end, so that when something breaks you know which app was holding it up.
How do you audit your apps?
In this order, in an afternoon.
- List them. Open the apps list in your Shopify admin settings and write every app down, with its monthly fee from the billing page next to it. Add a column for the last time anyone on your team opened it.
- Name the job. One sentence per app: what it does and where a customer sees it. If the sentence takes more than one try, that is a signal.
- Check the theme. For each app that adds something visible, open the theme editor and see whether a section or setting already does it. Also open the "App embeds" panel and note which apps are switched on there.
- Remove in order. Duplicates first. Then campaign leftovers. Then anything the theme can replace. Export data before each removal, and test checkout after each one.
- Look for leftovers. For anything older that you removed, check the theme for the code it left behind, or ask the developer for the removal steps.
Then look at your product page in a private window on your phone and notice whether it feels different. If it does, you know which app was the weight.
When is the answer a custom feature, not another app?
When you are paying several apps to approximate one thing that is central to how you sell.
This shows up on stores that have grown past the shape Shopify was built for. Wholesale pricing by customer group. A quote flow instead of a cart. Bundles built a specific way. Product options that depend on each other. Each of those can be pushed into place with two or three apps, and Shopify vs Wix vs a custom build says what happens next: the apps take a monthly bite each and occasionally break each other on update.
At that point a custom theme section, or a small private app that does one job for one store, can be the cheaper thing over a couple of years, and it is worth costing both ways. It loads only where it is used. Nobody else sets its price. And it is written for how your store actually works rather than for the average of every store. For wholesale in particular, the pieces that matter are in B2B wholesale online ordering.
What does this cost to fix?
An app audit on an existing store is hours of work, not a project. It is the kind of work that belongs in ongoing upkeep, which is what the developer hours in our care plan are for, from $129 a month for a small site.
Replacing a stack of apps with custom features is a build. Our e-commerce and B2B work runs from $2,900 to $25,000 and beyond depending on scope, and a store that needs a handful of apps turned into one clean feature sits toward the lower end. What sits inside each scope is on e-commerce, and the ranges are on pricing. Whether your store needs that or just a cleanup is the same question as any other site: rebuild or fix walks through how to tell.
If you would rather have someone else count, send us your store URL for a free teardown. We will tell you which apps are loading on your product page, which of them your theme could already replace, and what we would remove first, whether or not you work with us.