What installed apps add to your storefront’s load

Apps are how most Shopify stores get reviews, bundles, upsells, loyalty and chat. Each one with a storefront feature also adds work to every page it runs on. None of that is a reason to avoid apps. It is a reason to know what each one costs, so the decision to keep it is a real decision.

How apps get onto your storefront

There are two routes, and they behave very differently when you change your mind:

Shopify pushes app developers toward the first route: apps in its Built for Shopify programme must use theme app extensions for storefront elements, and may not modify theme files through the Asset API except for narrow cases such as page builders and backup tools. Older apps, and apps outside the programme, may still use the second.

What an app costs a page

• Requests to more servers. Each third-party origin needs its own connection before anything downloads.
• Main-thread JavaScript. Scripts must be parsed, compiled and run on the same thread that answers taps and clicks. That is where apps hurt INP, often on the product page where visitors interact most.
• Render-blocking code. A script loaded without defer or async in the page head holds up rendering, which delays LCP.
• Everywhere, not only where it’s used. A script loaded site-wide runs on pages that never show the feature. App embed blocks let developers load scripts only on specific pages; not every app does.

How much a given app costs depends on the app, the theme and the page. There is no reliable per-app figure to look up, which is why the next section matters. For what each metric is made of, see Core Web Vitals and INP on Shopify.

Shopify’s own yardstick

Shopify asks app developers to measure impact as the difference in Lighthouse performance score before and after the app is installed and configured, weighted across three page types: home 17%, product 40%, collection 43%, averaged over several runs. For Built for Shopify status, an app must not reduce the storefront score by more than ten points. That is a useful bar for your own store too: an app that costs more than that on your theme deserves a hard look.

The weighting is worth noticing. Product and collection pages together carry 83% of the score in Shopify’s method, the home page only 17%. That matches where apps tend to live, and where visitors decide to buy: reviews, size guides, badges, bundles and upsells cluster on product pages. An app that looks harmless on the home page can still be the most expensive thing on the page that sells.

Measuring your store, app by app

1. List every app with a storefront presence, and for each, the pages where its feature actually appears.
2. Search the theme for leftovers. Look in the layout file and snippets for code from apps you no longer have. Before uninstalling anything else, ask the app’s developer whether extra removal steps are needed.
3. Check the history. Shopify’s web performance reports mark app installs and theme changes on the chart. A step change in LCP or INP next to an install is your first suspect.
4. Test without it. In Chrome DevTools, block the app’s script URLs and run Lighthouse again on the home, product and collection templates. Average several runs and weight them the way Shopify does. The difference is the app’s lab cost on your theme.
5. Decide with both numbers. Put the cost next to what the app earns. Shopify’s own advice is to check that each app creates enough value to offset its performance cost.

The DevTools part, step by step

• Find the scripts. In the Network panel, filter by the app’s domain or file names. Lighthouse’s JavaScript boot-up time audit shows which scripts cost the most to parse, compile and run.
• Block and compare. Right-click a request and choose “Block request URL”, then reload and rerun Lighthouse. It simulates the store without that app, without touching the live theme.
• Read the waterfall. Scripts that start early and hold up the page are the ones to fix first. Scripts that load late and run little can usually stay.
• For apps you keep, check that their scripts load with async or defer unless the page needs them to render, and consider preconnect for a third-party origin on the critical path.

Questions to ask an app vendor

• Does the app use theme app extensions, or does it write into theme files?
• Can its script load only on the pages where its feature appears?
• Are its assets served from Shopify’s CDN or from its own servers?
• What stays in the theme after uninstalling, and how is it removed?
• Has it been measured against Shopify’s ten-point Lighthouse bar?

A note on page builders and theme-editing apps

Page builders are one of the few kinds of app Shopify still allows to modify theme files for Built for Shopify status, because editing the theme is their job. That makes them different from a reviews widget: removing one can mean rebuilding the pages it created, not just deleting a script. Measure them like any other app, but plan their removal as a small theme project rather than an uninstall.

Keep, fix, replace or rebuild

• Keep apps whose cost is small or whose value clearly covers it.
• Fix the loading: ask the vendor for page-specific loading, or move a widget below the fold and load it on interaction.
• Replace apps whose feature a modern theme now does natively, or that still inject code into theme files.
• Rebuild the feature in the theme or as a small custom app when you use one narrow part of a heavy app, so the storefront carries only what you need.
• Clean up code from uninstalled apps. It is the one change that has no trade-off at all.

How Lintel handles it

An app audit is the first step of our performance work: we list what each app loads and where, measure it with the method above, and give you the cost of each one in numbers you can check. Keeping, replacing or rebuilding stays your decision, and theme-side fixes fall under Shopify theme development.