The App Tax: Auditing What Your Apps Really Cost

The average Shopify store runs six apps. Stores past a few years of trading often run fifteen or more, most installed for a reason nobody currently remembers.

The monthly fees are the visible cost and usually the smaller one. The real cost is what each app does to the page.

Run the inventory

Open your product page in DevTools, network tab, disable cache, reload. Sort by size, then by time. For each third-party request, identify which app it came from.

Two numbers per app:

• Bytes it adds to the page
• Main thread time it consumes

Then, separately, what revenue it produces. Most apps have some reporting; the ones that do not are the ones to be most suspicious of.

The three categories

Earning their place. Clear revenue attribution, cost proportionate. Reviews on a store where reviews drive conversion. A subscription app on a subscription business. Keep and leave alone.

Replaceable. Doing something real that a theme section could do at zero runtime cost. Announcement bars, size charts, basic FAQ accordions, simple badges, trust seals. Almost always worth replacing.

Dead weight. Installed for a campaign two years ago, still loading on every page. Uninstall.

The leftovers problem

Uninstalling a Shopify app does not always remove its code. Apps that injected script tags into theme.liquid — the older pattern — frequently leave them behind.

Search your theme files for the app's name and any script domains you do not recognise. It is common to find code from three or four apps that are no longer installed and no longer paid for, still executing on every page view.

That is free performance sitting in your theme right now.

Measuring properly

Do not guess at the impact. Duplicate your live theme, remove one app's code, and compare:

• Page weight
• LCP on a throttled mobile profile
• Main thread blocking time

Do it one app at a time or you will not know which change did what.

The replacement calculation

Whether to replace an app with theme code is arithmetic:

• App: monthly fee × 12, plus the performance cost, plus the risk that it breaks or changes pricing
• Theme code: one-off development cost, plus a small maintenance burden

A £40/month app is £480 a year. If a developer can replicate the useful 80% of it in a day, that pays back inside a year and keeps paying — and the page gets faster.

This calculation flips as stores grow. At £5k/month revenue, apps are the right answer for nearly everything. At £150k/month, an app stack costing £800/month and 900ms of load time is usually worth consolidating.

Rules going forward

Install on a duplicate theme first. Measure before and after. Never install directly on live.

Set a review date. Every app gets a calendar entry six months out: is this still earning its place?

Prefer theme app extensions. The modern integration model. They render inside your theme, respect your styles, and are far cleaner to remove than injected script tags.

Cap the count. A soft limit of eight to ten apps forces the question every time a new one is proposed.

What to expect

A typical first audit on a mature store finds two or three uninstalled leftovers, two apps nobody is using, and three or four that could be theme sections. Acting on all of it commonly takes 30-50% off third-party JavaScript.

That shows up in LCP, in INP, and — with a lag — in mobile conversion rate.