Free Shopify Tool

Shopify App Bloat Detector

Free browser tool that scans a Shopify page for installed third-party apps (Klaviyo, Yotpo, Loox, Recharge, Gorgias, GTM, Hotjar, Shogun, GemPages and more) and estimates the aggregate Total Blocking Time cost so you know which ones to kill first.

After 100+ Shopify CRO audits, the same finding kept landing on the audit doc: the store has too many apps. Every app installs a third-party script (or three), every script blocks the main thread, and the aggregate TBT collapses Core Web Vitals.

This tool detects which apps you have installed and estimates the aggregate cost. It does not tell you to uninstall anything; it tells you which apps are the heaviest, which ones can be replaced with native Liquid snippets, and where to start.

FAQ

Frequently Asked Questions

How does the detector know which apps are installed?

It scans the page HTML for known Shopify-app DOM signatures: third-party script src URLs (static-tracking.klaviyo.com, staticw2.yotpo.com, loox.io/widget, config.gorgias.chat, etc.), iframe sources, link tags, custom data attributes, preconnect/preload hints, inline-script substrings, and global JS object names (window.klaviyo, OptanonWrapper, TriplePixel, fbq, ttq, etc.). Each app has 2 to 7 distinct signatures so a single match is enough. The library covers 192 of the most-installed Shopify apps across 18 categories: Email & SMS, Reviews, Subscriptions, Page Builders, Chat, Analytics, Cart & Upsell, Search, Loyalty & Rewards, Logistics, Currency, Social, Consent & Privacy, Performance Proxy, Personalization, Marketing, Inventory, and BNPL. It also detects Theme App Extensions installed via cdn.shopify.com/extensions/ (with numeric suffix stripped so handles like judgeme-494 resolve correctly).

How accurate is the Total Blocking Time estimate?

It is a directional estimate, not a measurement. Each app's TBT contribution is a typical figure I have collected from real-store audits and public benchmarks (Klaviyo onsite ~120ms, Yotpo widgets ~250ms, Shogun page builder ~300ms). Actual TBT depends on theme, app configuration, network, and device. Run Lighthouse for the real number; use this tool to know which apps are the heaviest before you start cutting.

What does the grade mean?

A: less than 100ms aggregate app TBT (lean stack, well-optimized). B: 100 to 200ms (typical small store). C: 200 to 400ms (mid-size store, some bloat). D: 400 to 700ms (heavy stack, will fail Core Web Vitals). F: 700ms+ (rebuild candidate, app sprawl is the primary CRO blocker).

Does it run on the URL or only pasted HTML?

Both. URL mode tries 5 public CORS proxies. Many production stores block shared proxies, so Paste HTML mode is the reliable path: open the page, View Source, copy, paste into the textarea. Detection runs locally in your browser, nothing is sent to any server.

Why does the tool flag Google Tag Manager? Is GTM bad?

GTM itself is fine. The tool flags it because GTM containers can hide dozens of pixels (Meta, TikTok, Pinterest, Snapchat, Reddit, LinkedIn) plus heavy scripts (Hotjar, Clarity, custom HTML tags), and those compound. A bare GTM container costs ~30ms TBT; a typical DTC GTM container costs 200ms+. The tool reports the conservative figure and recommends auditing the container.

Need a developer to actually fix what this tool finds?

I rebuild Shopify Markets currency setups, eliminate hardcoded prices, and ship clean Liquid that converts across every region. Book a free 30-minute strategy call or read the Everly case study that inspired this tool.