Medium or highSpeedMeasured

Leftover or broken code asks for missing files

Your pages ask for scripts, stylesheets or app addresses that no longer exist, often code a removed app left behind, so every shopper’s browser makes a wasted request and whatever the code was for doesn’t work.

Checked on: every page the audit scans except the cart · Zolvio’s check: “Leftover or broken code asks for missing files”

Why it costs you sales

Uninstalling an app doesn’t always remove what it added: a snippet pasted into the theme, an app embed, a script Shopify still loads for it, or a tag pointing at an account that was deleted. The page keeps asking for files that are gone.

Each missing file is a wasted request in every shopper’s browser, and a script in the page’s head without async or defer holds up the page until the error comes back. Whatever the code was for, such as a chat, reviews or tracking, doesn’t work, often without anyone noticing.

How Zolvio detects it

While each page loads on its own in a real browser, Zolvio notes the scripts and stylesheets that answer “not found” (404) or “gone” (410), the ones the browser refused to run because what came back wasn’t code, and the requests to an app’s address on your store (/apps/…) that answer “not found” or “gone”. Shopify’s own code, such as checkout, analytics and web pixels, isn’t judged. The audit’s browser doesn’t load other companies’ files, so their scripts and stylesheets are noted to be asked about separately.

Each one is then asked for once more. Up to 25 of your store’s own files and Shopify’s are asked for from a page of your store: one that still answers “not found” or “gone” counts, and an app’s address counts only when Shopify answers that no app is there any more. Up to 20 of other companies’ files are asked for from Zolvio’s server: one counts when its server answers “not found” or “gone”, or when the site’s name no longer exists. A refused request or a server error isn’t judged.

Each file is reported once, on the first page that asked for it; the cart isn’t checked. The finding lists up to ten, with what each answered, what it is (an app’s address, an app’s or the theme’s file, or another company’s), the app it belongs to when its address names one, where the page asks for it, and on how many pages.

Severity. Medium; high when a missing file is a script in the page’s head without async or defer, which holds up the page until the error comes back.

This is a direct measurement, so it’s reported on every plan, including Free and audits with AI turned off. With AI review on, the AI agent also checks it against the audit’s evidence before it reaches your issue list.

How to fix it

  1. Match each address in the finding to the app or tag it belongs to; the finding names the app when the address does.
  2. For a theme file or a script or stylesheet tag, duplicate your theme first, then in Online Store → Themes → Edit code search the theme for the file name and remove the line.
  3. For an app’s address (/apps/…) or an app’s file, turn off the app’s embed in the theme editor (App embeds), or reinstall the app and uninstall it again. A script in Shopify’s ScriptTag list is removed by the app that added it.
  4. For another company’s tag, such as a Google tag or a pixel, remove it where it was added (the theme, Google Tag Manager or Settings → Customer events), or replace its ID with a live one.

In Zolvio: on paid plans with AI turned on, the guided fix writes these steps for your own store and theme: where to click in Shopify admin or the theme editor, or which file to open, the line to find and the code to add. Each file opens in Shopify’s code editor. Zolvio never edits your theme: you make the change, then Verify fix checks your published theme for code changes (or you mark it fixed), and later audits confirm the problem is gone.

Common questions

Why does “Leftover or broken code asks for missing files” cost a Shopify store sales?

Uninstalling an app doesn’t always remove what it added: a snippet pasted into the theme, an app embed, a script Shopify still loads for it, or a tag pointing at an account that was deleted. The page keeps asking for files that are gone. Each missing file is a wasted request in every shopper’s browser, and a script in the page’s head without async or defer holds up the page until the error comes back. Whatever the code was for, such as a chat, reviews or tracking, doesn’t work, often without anyone noticing.

How does Zolvio detect “Leftover or broken code asks for missing files”?

While each page loads on its own in a real browser, Zolvio notes the scripts and stylesheets that answer “not found” (404) or “gone” (410), the ones the browser refused to run because what came back wasn’t code, and the requests to an app’s address on your store (/apps/…) that answer “not found” or “gone”. Shopify’s own code, such as checkout, analytics and web pixels, isn’t judged. The audit’s browser doesn’t load other companies’ files, so their scripts and stylesheets are noted to be asked about separately. Each one is then asked for once more. Up to 25 of your store’s own files and Shopify’s are asked for from a page of your store: one that still answers “not found” or “gone” counts, and an app’s address counts only when Shopify answers that no app is there any more. Up to 20 of other companies’ files are asked for from Zolvio’s server: one counts when its server answers “not found” or “gone”, or when the site’s name no longer exists. A refused request or a server error isn’t judged. Each file is reported once, on the first page that asked for it; the cart isn’t checked. The finding lists up to ten, with what each answered, what it is (an app’s address, an app’s or the theme’s file, or another company’s), the app it belongs to when its address names one, where the page asks for it, and on how many pages.

How do I fix “Leftover or broken code asks for missing files” on Shopify?

Match each address in the finding to the app or tag it belongs to; the finding names the app when the address does. For a theme file or a script or stylesheet tag, duplicate your theme first, then in Online Store → Themes → Edit code search the theme for the file name and remove the line. For an app’s address (/apps/…) or an app’s file, turn off the app’s embed in the theme editor (App embeds), or reinstall the app and uninstall it again. A script in Shopify’s ScriptTag list is removed by the app that added it. For another company’s tag, such as a Google tag or a pixel, remove it where it was added (the theme, Google Tag Manager or Settings → Customer events), or replace its ID with a live one.

Related

Documentation

  • How audits work — What an audit scans and how findings become issues.
  • Guided fixes — Step-by-step fixes written for your theme, with links into the code editor.
  • Workflows — Go from an issue to its heatmap and recordings before you change anything.