When the app stack is the problem: auditing installed apps

Most Shopify stores grow by installing apps, and that is the platform working as intended. The trouble comes later: an app installed for one campaign still loads a script on every page, two apps do the same job, and the monthly bill includes tools nobody opens. None of this shows up as one broken thing. It shows up as a slower store and a larger invoice.

An app audit is not about getting to a small number. It is about knowing what each app does, what it costs, and whether that is still worth it.

What an app actually costs

• Speed. Apps that add storefront features usually load scripts, styles or requests. web.dev lists what third-party code does to a page: too many network requests to other servers, JavaScript that keeps the main thread busy, and scripts that block content until they finish.
• Fees. Each subscription looks small alone. Across 20 apps it is a real line item, and some apps bill outside Shopify, which is easy to miss.
• Leftover code. Shopify’s Help Center warns that some apps add code to the theme that isn’t removed automatically when the app is uninstalled.
• Overlap. Two apps changing the same part of the page can conflict, and a bug is harder to trace when several apps touch the same area.

Step 1: make the inventory

Start with a table, one row per installed app, from Settings > Apps in the Shopify admin:

Admin-only apps and background syncs don’t load anything on the storefront, so they matter for cost and data, not speed. The storefront column is where the performance work is.

Step 2: measure with real data first

Shopify’s web performance reports show the three Core Web Vitals: Largest Contentful Paint for loading speed, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift for visual stability. The summary on the Themes page rates the store on real user data from the past 30 days, and the reports show the 75th percentile of visits by default. The full reports are under Analytics > Reports.

The most useful feature for an app audit is on the “over time” reports: numbered vertical lines mark events that could affect performance, including app installations, theme updates and new code. If a metric got worse after a particular install, the chart shows it. Two caveats: data can be delayed by up to 36 hours, and it covers only the last 90 days, so older installs have to be tested directly.

For INP, web.dev’s thresholds are: at or below 200 milliseconds is good, above 200 up to 500 needs improvement, and above 500 is poor. Scripts that keep the main thread busy tend to show up here first, because every tap has to wait for them.

Step 3: isolate each app’s impact

Real-user data tells you whether there is a problem. To find which app causes it, test one at a time:

1. Open a product page and a collection page in Chrome with DevTools, and list the scripts and requests that come from each app’s domain in the Network panel.
2. Use DevTools’ request blocking, which web.dev recommends for this, to block one app’s scripts and reload. The difference is roughly what that app costs on that page.
3. Run Lighthouse with and without the app’s scripts. This mirrors how Shopify measures an app’s storefront impact: it compares Lighthouse scores before and after an app is installed, weighting product pages 40%, collection pages 43% and the home page 17%.
4. Note which pages the app actually needs to run on. A review widget belongs on product pages; if it loads on every page, that is waste.

Step 4: remove, reconfigure or consolidate

• Remove apps with no owner and no recent use. web.dev’s advice for third-party scripts is blunt: if a script doesn’t add clear value, remove it.
• Reconfigure apps that are needed but load everywhere. Shopify recommends that app developers use app embed blocks, which can load scripts only on specific pages; check the theme editor for per-page or per-template settings before replacing the app.
• Replace apps that edit theme code by hand with ones built on theme app extensions, which Shopify describes as extending themes in a way that protects theme code integrity.
• Consolidate when several apps each cover part of one workflow. Sometimes one App Store app covers all of it; sometimes a single custom app built around the workflow is cheaper to run than three subscriptions.

Patterns to look for in the inventory

Once the table is filled in, a few patterns tend to stand out. None of them is a rule; each is a question for the app’s owner.

• Campaign leftovers. Apps installed for a launch, a sale or a test that ended. If no one can name the last time it was needed, it is a removal candidate.
• Two apps, one job. Two popup apps, two review apps, two apps that both add badges to product cards. Keep the one the team actually configures.
• Storefront apps with admin-only value. An app whose useful part is a report in the admin, but which also loads a script on every page for a feature nobody turned on. Check its settings before removing it.
• Apps billed outside Shopify. These don’t show on the Shopify bill, so they are easy to forget. Match them against card statements.
• Apps from a previous theme. Code added by hand to an old theme may have been copied into the current one, even if the app’s features aren’t used there.

Uninstalling cleanly

1. Export data first. Shopify’s Help Center notes that apps may store data that can’t be recovered after uninstalling.
2. Check for extra steps. Read the app’s App Store listing or ask its developer whether theme code has to be removed by hand, then remove it from a duplicate of the theme and check it before publishing.
3. Check billing. Uninstalling a paid app stops future charges, but you might still be billed for the current cycle. Apps that charge outside Shopify have to be cancelled with the developer separately.
4. Measure again. Compare the web performance report after the change, remembering the delay of up to 36 hours.

Where Lintel fits

Lintel’s performance and technical SEO work includes this kind of audit: an inventory, per-app measurements on your own pages, and a list of what to remove, reconfigure or replace, with leftover theme code cleaned up. When the audit shows several apps doing one workflow badly, a custom Shopify app is one of the options, priced against the subscriptions it would replace. Often the answer is simply fewer apps.