How Shopify Apps Quietly Kill Your Store's Speed (And How to Audit Yours)

Apps are the number-one reason Shopify stores are slow. Not your theme. Not Shopify itself. The stack of apps you have installed over time, each adding their own JavaScript and CSS to every page they touch, whether your customer is on a page that uses them or not.

The good news is that diagnosing which apps are hurting you is something you can do yourself in about thirty minutes, with free tools and no code. The harder part comes after, but at least you will know exactly what you are dealing with. This is a practical guide to running that diagnosis.

Why apps slow stores so much

A short explanation, because it shapes how you audit them.

When you install a Shopify app, most of them inject scripts into your theme that load on every page visit, not just the pages where the feature actually appears. A review widget loads on your homepage even if it only shows on product pages. A popup script loads on your cart page even if the popup only fires on entry. A live-chat widget loads everywhere. Multiply that across the fifteen to twenty apps a typical store runs, and you can easily be shipping a megabyte or more of third-party JavaScript that the browser has to download and process before it can show your customer anything.

There is a second, less obvious problem: uninstalling an app often does not fully remove its code. Many apps inject snippets into your theme files during installation and leave them behind on uninstall, sometimes for years. So even your previous cleanups may be leaving orphaned scripts loading on every page, doing nothing but slowing you down.

This is what you are auditing for.

The thirty-minute audit

Here is the practical walkthrough. Do it on a desktop computer with Chrome, on a quiet browsing window so other tabs are not competing.

Step one: get your baseline. Run your homepage and one product page through Google PageSpeed Insights at pagespeed.web.dev, separately. Write down the mobile score and the three Core Web Vitals (LCP, CLS, INP) for each. This is the number you will compare against. Without a baseline, you cannot tell what an app is actually costing you.

Step two: see every script your store is loading. Open Chrome, go to your store, press F12 to open DevTools, click the Network tab, then reload the page. In the filter row, click "JS" to show only JavaScript files. Now sort by the Transfer column to see the largest files first. Anything loading from a domain that is not your own store domain or cdn.shopify.com is almost certainly an app or third-party script. Make a quick list of what you see and roughly how heavy each one is. You are looking for the big ones.

Step three: check for ghost code from removed apps. With DevTools still open, click the Console tab and reload the page. Look for red errors, especially anything saying a JavaScript or CSS file returned a 404. Those are ghost scripts: code your theme is still trying to load from an app that no longer exists. Each one is a wasted request adding latency for no benefit. Note them down.

Step four: identify your worst offenders by category. Some app categories are consistently the heaviest. Review widgets, live chat, popups and email-capture tools, page builders, social proof and recently-viewed notifications, and product recommendation engines tend to ship the most JavaScript. Cross-reference what you found in DevTools against these categories. The pattern usually becomes obvious quickly.

Step five: isolate each suspect. This is the part that gives you the actual numbers. For each heavy app you found, temporarily disable it (in Shopify admin, Apps, three dots, uninstall, or for app embeds: Online Store, Themes, Customize, App embeds, toggle off). Then re-run PageSpeed Insights on the same page you tested in step one. The score change tells you what that app is genuinely costing. If disabling an app gains you ten points, you know exactly what it is worth. Re-enable apps as you finish testing each one.

Step six: decide what to do with what you found. For each app on your list, ask three questions. Is this app generating measurable value: revenue, conversions, customer satisfaction you can point to? If no, remove it permanently. If yes, is there a lighter alternative that does the same job? If yes, consider switching. If no, can its script be deferred so it loads after the main page is visible? That last question is where the audit hits its ceiling.

Where the DIY audit ends

Here is the honest part. The audit above will identify your problems, and it will let you remove the apps that are clearly not earning their keep, which alone often recovers ten to twenty PageSpeed points. That is real and worth doing.

But the deeper work, safely deferring scripts you need to keep, removing ghost code embedded across multiple theme files, and getting your remaining apps to load in a way that does not block your page from showing, is structural engineering, not housekeeping. Deferring the wrong script breaks your cart, your reviews, your chat. Editing Liquid files to clean orphaned snippets without breaking anything else takes real care. This is where the diagnostic guide ends and where the specialist work begins.

If your audit turned up a long list, or you found apps you cannot remove without losing revenue and need them to stop blocking your page, that is exactly the work our page speed optimization services handle. We take the messy app stack as-is, defer what can be deferred, remove the orphan code your previous cleanups left behind, and validate the result against real-world performance, not just a lab score. And because the audit you just ran will need to be repeated every few months as you add new apps, ongoing maintenance keeps the result from quietly decaying.

If you want help interpreting what your audit found, or simply do not have the time to run it yourself, a quick call is the fastest way to know exactly where your store stands.