Summary

  1. Most apps load their JavaScript on every page, before your content is ready. In our data from 273 stores, average mobile PageSpeed falls from 53.2 to 38.3 as app count rises.

  2. Start with the free fixes. Confirm apps are the cause, remove unused apps and leftover code, and limit apps to the pages that need them.

  3. Defer the apps you keep. Defer their scripts, limit them to the pages that need them, then re-test both your scores and your key shopping flows.

Apps slow your store because their scripts load before your content

Your Shopify store got slower after installing apps because most apps load their JavaScript on every page, for every visitor, while the browser is still building the page. In our analysis of 273 Shopify stores, average mobile PageSpeed fell from 53.2 for stores with 1 or 2 apps to 38.3 for stores with 16 or more.

Picture a store that launched in spring with a clean theme and two apps. By October, the team has added reviews, an email popup, live chat, and an upsell widget for Black Friday. Each app solved a real problem, and nobody touched the theme. That store is an example, but the pattern behind it is not.

The fix isn't deleting the apps you rely on. It's controlling when and where each one loads, so your page renders first and your apps load when shoppers need them.

What 273 Shopify stores show about app count and speed

We matched app counts to mobile PageSpeed scores for 273 live Shopify stores. Scores dropped at every step as app count rose. Full results are in our study of how many apps the average Shopify store has.

Table 1. Average mobile PageSpeed score by number of apps installed
Apps installed Average PageSpeed score (mobile, out of 100)
1 to 2 53.2
3 to 5 49.8
6 to 10 45.2
11 to 15 38.8
16 or more 38.3

The typical store is already in the poor range

The median store in our study runs 4 apps. Stores with 3 to 5 apps averaged 49.8, and Lighthouse rates any score from 0 to 49 as poor. A store doesn't need a long app list to have a speed problem. An ordinary one is enough.

The decline also builds as stores grow. The largest single step, 6.4 points, comes between stores with 6 to 10 apps and stores with 11 to 15.

Correlation, not a controlled test

These numbers show that stores with more apps tend to score lower. They don't prove apps caused every point of the drop, since stores with more apps may also differ in theme, images, and custom code. What they do show is a consistent pattern across hundreds of real stores, which matches how browsers handle extra JavaScript.

How app scripts slow loading and interaction

The slowdown happens in your shopper's browser, not on Shopify's servers. Our audit of 1,166 Shopify stores found that the bottleneck was the browser's workload: JavaScript, apps, and other assets that block rendering. The browser has to download and run every app script, and that costs you twice: once while the page loads, and again when a shopper tries to use it.

Loading: scripts compete with your content

When a script is loaded without async or defer, the browser stops building the page until that script has run. Google's guidance is to use async or defer for third-party scripts unless they're needed to render the page.

Even well-behaved scripts need the browser's main thread to run. That's why Total Blocking Time carries the largest weight in the Lighthouse performance score, at 30%. It measures how long the page is too busy to respond.

Interaction: busy scripts delay taps and clicks

Interaction to Next Paint (INP) measures how quickly a page responds when someone taps, clicks, or types. Google rates INP of 200ms or less as good and anything above 500ms as poor. If an app is running a long task when a shopper taps "Add to cart", the tap waits.

One app rarely means one script

The 2025 Web Almanac found the median chain of third-party inclusions is 3 deep: a script loads another script, which loads another. The real cost of an app is often larger than the one file you can see.

Shopify's script tag change won't fix this for you

Shopify is retiring script tags, the older way apps add JavaScript to a storefront. Since October 1, 2026, apps can't create or update script tags, and Shopify will stop running existing ones on March 1, 2027. Apps are moving to app embed blocks, and to web pixels for analytics.

That's a good change: app embeds are visible in your theme editor, so you can see what's running and switch it off. But it doesn't change how much JavaScript an app loads or when it runs. An embed that's switched on can still load on every page unless the app limits it.

How to fix a slow Shopify store without removing your apps

Start with the free steps. They clear out dead weight, so you can see which apps are actually costing you speed.

Step 1: Confirm apps are the cause (free)

  1. Look for a pattern in Shopify's data. The Web Performance report shows LCP, INP, and CLS from real visitors, and marks events like app installs on its chart. If a metric worsened right after an install, you have your first suspect. The report can lag by up to 36 hours.
  2. Test the pages Shopify uses to grade apps. Shopify measures an app's impact as a weighted Lighthouse average of home (17%), product (40%), and collection (43%) pages. Run PageSpeed Insights on one of each and note the scores.
  3. List what loads. In your Shopify admin, go to Online Store > Themes > Customize, then open App embeds and note every embed that's switched on. In PageSpeed Insights, check which third-party scripts kept the main thread busy and match them to your apps.
  4. Note mismatches. Flag apps loading on pages where they do nothing, such as a reviews app on your homepage.

Step 2: Remove unused apps and leftover code (free)

Uninstall apps you no longer use, and any that duplicate each other. Two apps that both run popups double the cost for one job. Chat apps are a common case.

Then check for leftovers. Shopify notes that uninstalling an app doesn't automatically remove its code from your theme. To check safely:

  1. Duplicate your theme and work on the copy.
  2. Search theme.liquid and your snippets for the names or domains of apps you've removed.
  3. Remove the references, then test your home, product, cart, and checkout pages before publishing.

If you're unsure what a piece of code does, ask the app's developer before deleting it.

Step 3: Limit where apps load (free, where the app allows it)

If an app offers both an app embed and an app block, use the block and place it only on the templates that need it. A reviews block on product pages is lighter than a store-wide embed. Shopify's own guidance for app developers is to load scripts only on the pages that need them.

Many apps don't offer this choice, so this step usually helps only a few of them.

Step 4: Defer the scripts you keep (manual or automatic)

Deferring tells the browser to render your page first and run app scripts afterward. This is the step that lets you keep your apps and still get speed back. There are two useful moments to load an app:

  • After the main content loads. Good for widgets shoppers see but don't need instantly.
  • On first interaction. The script waits until the visitor scrolls, taps, or moves the mouse. Good for features nobody uses in the first second, like chat.

The right timing depends on the app and the page.

Table 2. When to load common app types
App type Where it's needed Suggested timing What to watch
Product reviews Product pages After main content Star ratings near the title appearing late and shifting the layout
Live chat Pages where shoppers ask questions On first interaction The chat button not responding on the very first tap
Popups and email capture Home and collection pages On first interaction Timed popups firing later than configured
Upsell and cart add-ons Product and cart pages After main content The cart drawer being ready before a shopper adds to cart
Loyalty and rewards Account pages and the rewards launcher On first interaction The launcher icon appearing late
Analytics and ad pixels All pages Usually leave as is Missed sessions from visitors who leave before interacting

Manual option: add the defer attribute to script tags you control in your theme, or use a tag manager to fire non-critical scripts after the first interaction. This needs a developer, can break apps that expect to run early, and doesn't reach scripts that apps inject through app embeds. Theme code edits can also conflict with future theme updates and need to be copied over by hand.

Automatic option: a script deferral app sets the timing for you, without editing theme code.

Whichever you choose, know what can break:

  • Analytics can undercount. If a tracking script waits for interaction, visitors who leave without interacting may never be recorded.
  • Visible widgets can shift the layout. Anything near the top of the page that appears late can push content down and hurt your Cumulative Layout Shift (CLS) score.
  • First clicks can wait. A feature that loads on interaction may need a moment to respond to the very first tap.

Step 5: Re-test scores and flows (free)

Run the same pages through PageSpeed Insights and compare Largest Contentful Paint (LCP), Total Blocking Time, and INP. Then click through your key flows (add to cart, reviews, popups, chat) to confirm every app still works.

Some speed apps make the next page feel instant by preloading it when a shopper hovers over a link. That helps the second page, not the first. The page a shopper lands on from Google or an ad still loads every app script before your content, and PageSpeed Insights tests that single page from a cold start.

If your store got slow after installing apps, you need those scripts deferred, not the next page preloaded.

How Hyperspeed's JS app deferral works

Hyperspeed's JS app deferral handles Steps 3 and 4 without code:

  • Two timings. App scripts load once critical content has loaded, or when the shopper starts interacting with the page.
  • Per app and per page. App optimization can be customized per app and per page. For third-party app scripts, you choose each script's load method (default, async, or defer) and which pages it loads on.
  • A store-wide deferral list. Scripts you add to the Smart JS deferral list wait until the page has loaded or the shopper interacts, on every page.
  • Two modes. Smart deferral defers safe app and Shopify scripts and keeps analytics loading normally. Aggressive deferral also defers analytics for maximum speed, which may affect tracking.
  • Built-in compatibility with popular apps, including Klaviyo, Judge.me, Privy, Yotpo, Loox, and Stamped.io.

Preview any change on a copy of your theme before publishing it. One limit to know: some apps may not work in preview mode but work normally once published, so recheck those after going live.

Table 3. Ways to fix an app slowdown, compared
Approach Keeps your apps Skill needed Speeds up the first page load Page-specific loading Upkeep
Remove apps No None Yes Not applicable Low, but you lose the features
App blocks on select templates Yes Low Partly Only for apps that offer blocks Low
Manual defer in theme code Yes Developer Partly; can't reach app embed scripts Only with custom code High; edits can conflict with theme updates
Tag manager triggers Yes Developer Yes, for tags it manages Yes Medium; adds its own script
Link preloading apps Yes None No; speeds up the next page No Low
Other script deferral apps Yes None Yes Varies by app Low
Hyperspeed JS app deferral Yes None Yes Yes, per app and per page Low; compatibility maintained for popular apps

Keep the apps that earn their place

Deferral is the right fix for apps that earn their place. It isn't a reason to keep apps you don't use. If an app hasn't driven a sale, a signup, or a support conversation in months, remove it. Zero code always loads faster than deferred code.

Where the data comes from

  • Sample: More than 400 active Shopify stores, compiled from public web sources and verified as Shopify, with at least one detectable app. Of these, 273 were matched to PageSpeed scores; all scores in this post come from those 273.
  • Collection dates: Not stated in the source study, which was published on June 11, 2026.
  • Method: We detected apps by fingerprinting public page source (CDN URLs, JavaScript globals, CSS class names, and DOM attributes) on each store's home, collection, and product pages, using a database of 100+ apps across 20 categories. Scores came from the Google PageSpeed Insights API using the mobile strategy.
  • Limitations: We could only detect apps visible in public page source, so back-office apps aren't counted. The results show correlation between app count and score, not a controlled before-and-after test.
  • Source data: Full findings in how many Shopify apps does the average store have?

What to do next

Work in order: confirm apps are the cause, remove what you don't use, limit where apps load, then defer the rest one app at a time. Re-test your home, product, and collection pages after each change, and click through checkout before you call it done.

Keep your apps. Just stop letting them load before your store does.

Is your Shopify store
fast enough?

Find out what’s slowing your storefront down and where to start improving it.

Preparing your demo

  1. Checking your store
  2. Opening your homepage, a collection and a product
  3. Extracting the styles your first screen needs
  4. Getting your demo ready

This usually takes 10 to 30 seconds.

FAQ

How many Shopify apps is too many?

There is no fixed number. In our study of 273 stores, average mobile PageSpeed dropped with each step up in app count, and stores with 3 to 5 apps already averaged below 50. What matters more than the count is how much JavaScript each app loads, and on which pages.

Does uninstalling a Shopify app remove its code?

Not always. Shopify says uninstalling an app doesn't automatically remove its code from your theme. Apps that edited theme files directly can leave scripts and snippets behind, so check your theme code after uninstalling, on a duplicate theme first.

Can I speed up my Shopify store without removing apps?

Yes. You can defer an app's scripts so they load after the main content or on the visitor's first interaction, and only on the pages where the app is used. The app still works; it just stops competing with the content shoppers see first.

Will Shopify's script tag deprecation make my store faster?

Not on its own. Apps are moving from script tags to app embed blocks, which makes them easier to see and switch off in your theme editor. It doesn't change how much JavaScript an app loads or when it runs.

Will deferring app scripts break my apps or analytics?

It can if the timing is wrong for the app. Deferred analytics may miss visitors who leave quickly, widgets near the top of the page can appear late and shift the layout, and chat may not be ready on the first click. Defer one app at a time and test each change.