The average Shopify merchant running more than $1M in annual revenue is paying for 23 apps. According to internal data shared by Shopify agency Underscore Talent at the 2026 Merchant Operations Summit in Austin, fewer than 40% of those apps are actively contributing to revenue or retention. The rest are legacy installs, redundant tools, and abandoned experiments — each one adding JavaScript weight, API call overhead, and monthly SaaS spend that compounds quietly in the background.
This isn’t a theoretical problem. Storefronts carrying 20+ active apps routinely score below 40 on Google’s Core Web Vitals PageSpeed index, and a 2025 Portent study found that conversion rates drop roughly 4.4% for every additional second of load time. For a store doing $3M a year, a two-second lag could represent $260,000 in lost revenue annually.
The good news: auditing and rebuilding your app stack is a weekend-sized project if you run it with a clear framework. Here’s how to do it in six steps.
Step 1: How Do You Get a Complete Picture of Every App You’re Paying For?
Before you can cut anything, you need a full inventory. Pull this from three sources simultaneously:
- Shopify Admin → Apps: Shows all installed apps, but not uninstalled apps that may still be injecting code via theme files or ScriptTags.
- Your billing dashboard: Cross-reference app charges in Shopify’s billing section against your credit card or bank statement. Orphaned charges for uninstalled apps are common.
- Google Tag Manager or your theme’s
theme.liquidfile: Use Chrome DevTools (Network tab, filter by JS) to surface third-party scripts that aren’t visible in the admin panel.
Build a simple spreadsheet with columns for: app name, monthly cost, primary function, last active use date, owner/stakeholder, and a performance impact score (you’ll fill that last one in Step 3).
“Most merchants haven’t opened their app list in 18 months. When we do this audit with new clients, we find an average of four apps they’re paying for that do the same thing — usually review tools, loyalty programs, or upsell widgets that were installed and then replaced without removing the old one.” — Jamie Kwong, Head of Platform Strategy, Fuel Made
Step 2: How Do You Categorize Apps by Function and Redundancy?
Once you have your full list, group apps into functional categories. Common clusters where redundancy hides:
- Reviews and UGC: Okendo, Yotpo, Judge.me, Stamped — merchants frequently have two running simultaneously after a migration
- Loyalty and retention: Smile.io, LoyaltyLion, Yotpo Loyalty (yes, separate from Yotpo Reviews)
- Upsell and cross-sell: ReConvert, Aftersell, Zipify OCU, CartHook
- Email/SMS capture: Klaviyo pop-ups, Privy, Justuno, Omnisend forms — often stacked accidentally
- Inventory sync: Stocky (now deprecated), Linnworks, Skubana/Extensiv, native Shopify inventory
For each category, identify the single source of truth you actually want. Everything else in that category is a candidate for removal.
Step 3: How Do You Measure the Real Performance Cost of Each App?
This step requires a tool. Use one of the following to get app-level performance data:
- Shopify’s built-in App Impact report (Admin → Apps → App performance): Released in late 2025, this dashboard shows per-app JavaScript size, render-blocking impact, and estimated effect on Largest Contentful Paint (LCP). It’s the most authoritative source available for Shopify merchants.
- SpeedScore by Nostra AI: Gives a per-app speed penalty score and estimated revenue impact based on your store’s traffic volume and conversion rate.
- WebPageTest.org with filmstrip view: Run your store URL with and without specific apps (by temporarily disabling them in a staging environment) to see raw load time delta.
Assign each app a score from 1–5 on performance impact (5 being highest drag). Apps scoring 4 or 5 need either replacement with a lighter alternative or justification based on revenue contribution that clearly outweighs the cost.
“We had a client in the apparel space — $8M a year — who was running Yotpo Reviews, Okendo, and Stamped simultaneously because three different agencies had installed them over four years. Removing two of them and cleaning the leftover ScriptTags knocked 1.8 seconds off their mobile LCP overnight.” — Rachel Moreau, Technical Lead, Ethercycle
Step 4: How Do You Decide What to Cut, Keep, or Replace?
Run each app through a simple three-question decision framework:
- Is it actively used? If no one on your team can name the last time they logged into it or reviewed its output, it’s a cut candidate regardless of cost.
- Does it have a measurable revenue or retention contribution? Pull 90-day data. For review apps, check review volume and their attributed conversion lift. For loyalty programs, check redemption rates. If you can’t attribute anything to it, the burden of proof is on the app.
- Can Shopify native features or a single consolidated tool replace it? Shopify’s 2025-2026 platform releases have closed the gap significantly: native bundles, native B2B, improved Flow 3.0, and Shopify Subscriptions now handle use cases that previously required paid apps. Audit what you’re paying for that Shopify now does free.
Apps that pass all three questions stay. Apps that fail question one are immediate cuts. Apps that fail questions two or three go on a 30-day probation — track them explicitly and make a final call at the end of the month.
Step 5: How Do You Safely Remove Apps Without Breaking Your Store?
This is where merchants cause the most self-inflicted damage. Uninstalling an app from the Shopify admin does not automatically remove the code it injected. Follow this removal checklist:
- Before uninstalling, check the app’s documentation for a “clean uninstall” guide — most reputable vendors (Okendo, ReConvert, Gorgias) publish one.
- After uninstalling, search your
theme.liquid,product.liquid,cart.liquid, and any section files for leftover{% render %}tags,{% include %}calls, or hardcoded<script src="">references tied to the removed app. - Check your Content Security Policy and any custom pixel configurations in Shopify’s Customer Events section (Admin → Settings → Customer events) for orphaned app pixels.
- Run a full regression test on your checkout funnel after each removal — not just homepage load, but add-to-cart, checkout step one through confirmation, and any post-purchase flows.
Use a staging environment if your plan supports it (Shopify Plus includes development stores; non-Plus merchants can use a duplicated theme). Never remove more than two or three apps in a single session without testing in between.
Step 6: How Do You Build a Leaner Stack Going Forward?
Once you’ve pruned, establish governance so the bloat doesn’t return within six months. Three practices that work at the operator level:
- Single app owner per category: One person on your team owns the reviews tool. One person owns the loyalty program. No app installs without that owner’s sign-off and a documented use case tied to a specific KPI.
- Quarterly app reviews on the calendar: Thirty minutes every quarter to re-run the App Impact report and check for new Shopify native features that may have made a paid app redundant. Put it on the ops calendar the same way you’d schedule a financial review.
- A preferred vendor shortlist: For each functional category, define your preferred tool and one fallback. For review collection, that might be Okendo (primary) and Judge.me (fallback for smaller SKU counts). Having a shortlist prevents the instinct to test every new entrant that appears in the app store.
“The merchants who keep clean stacks aren’t the ones who are most disciplined about removing apps — they’re the ones who set a high bar for installing them in the first place. If you can’t write a three-sentence business case for a new app before you install it, you probably don’t need it.” — Drew Sanocki, co-founder of Nerd Marketing and former CMO of Teamwork Commerce
What Does a Lean High-Performance App Stack Actually Look Like?
For a DTC brand doing $2M–$10M annually in 2026, a well-governed app stack typically runs 10–14 apps total. A representative example from a skincare merchant audited by Ethercycle in Q1 2026 post-cleanup:
- Reviews: Okendo ($299/mo)
- Loyalty: Smile.io ($199/mo)
- Subscriptions: Shopify Subscriptions (native, free)
- Email/SMS: Klaviyo ($400/mo, combined)
- Helpdesk: Gorgias ($300/mo)
- Post-purchase upsell: Aftersell ($99/mo)
- Bundles: Shopify Bundles (native, free)
- Inventory management: Extensiv ($500/mo, replaces three legacy tools)
- Analytics: Triple Whale ($299/mo)
- Returns: Loop Returns ($195/mo)
Total monthly app spend: approximately $2,291. Down from $4,800/month pre-audit. Page load time on mobile: 2.1 seconds LCP, up from 4.7 seconds. The merchant reported a 7% lift in mobile conversion rate within 60 days of completing the cleanup.
The math is not subtle. A bloated app stack is a performance tax, a financial leak, and an operational liability rolled into one. Running a structured audit twice a year — and building the governance to keep your stack lean between audits — is one of the highest-ROI infrastructure investments an ecommerce operator can make.
