Is old app code still slowing your store?

Store health

Uninstalled Shopify apps routinely leave scripts behind that keep loading — or keep failing — on every page view. Scan your store and see every app script it carries, which ones are dead residue, and how much weight they add. Free, ~15 seconds.

Want the leftovers actually removed?

A fixed-scope theme cleanup — I find every injected snippet, remove it on a duplicated theme, test, and hand it back faster. I take that on as studio work, and I quote it from this exact scan.

Reads your public homepage only — nothing is installed, nothing is changed. 10 free scans a day.

External scripts on your homepage

—

From known Shopify apps

—

Measured script weight

—

SourceTypeStatusKB

Honest limits: this is a script-level scan of your homepage. Theme-embedded snippets and CSS that don't load an external file can't be seen from outside — a theme audit with code access covers those.

Straight answers.

Do uninstalled Shopify apps really leave code behind?

Very often, yes. Uninstalling revokes the app's access but doesn't clean your theme — script tags, snippets and CSS the app added can stay forever, loading (or failing) on every page view. It's one of the most complained-about problems in Shopify communities.

How does leftover code slow my store?

Every leftover script is another request on every page view. Live-but-unused scripts add download and execution time; dead ones stall the browser until the request fails — every visit. A store that's tried ten apps commonly carries hundreds of kilobytes it no longer needs, and page speed is a conversion input: slower pages sell less.

What can this scanner honestly see?

Everything your homepage loads from outside: each script, who it belongs to, whether the URL still answers, and its size where servers report it. What it can't see: theme-embedded snippets that don't load an external file — those need a theme audit with code access.

How do I remove what it finds?

For each dead or unwanted script: find the injection point — usually theme.liquid, a snippet named after the app, or Settings → Customer events — remove the reference on a duplicated theme, and test before publishing. Not comfortable in Liquid? That's a fixed-scope Studio job.

Will you keep watching my store after this?

Only if you ask. This scan is one look at one page. Bilby is the ongoing version — it visits your store every night and emails you when something breaks, from US$29/mo (US$24/mo billed yearly). Prices include GST.

A Bilby report: the step that failed, ringed, with what it costs
Bilby's report: the step that failed, and what it costs while it stays broken.

What this looks like in the app

A live status card: one service, three cities and the last 24 hours
Everything I publish is measured the same way: by trying the real thing.
The email Bilby sends before breakfast when something is broken
What it looks like when it happens to a real store: the email, at 06:58.

Start tonight.

Type your store. Bilby walks it now and shows you what it found. Free, no card.

Scan your store

About two minutes. Bilby stops at payment.

Walk my store