A global variable another script reads
How you'll know: Removing an "unused" file breaks a page that never loaded it directly.
Fix: Search every file, template and tag container for the name before deleting anything. Then wrap the code in a module so it stops leaking globals.
Scripts that only work in the order they load
How you'll know: A plugin or theme update moves jQuery to the footer, or defers it, and half the page stops responding.
Fix: Make each script declare what it needs, ideally through a small build step, so load order stops being a hidden rule.
Code stored in the CMS, not in the files
How you'll know: A behavior exists on one page, but nobody can find the code for it anywhere in the repository.
Fix: Check content blocks, page builder widgets and custom HTML fields for inline scripts and onclick handlers, and list them with the rest.
A form that only checks itself in the browser
How you'll know: Spam or half-empty entries reach the CRM, even though the form has validation.
Fix: Browser checks are a convenience, not protection. Repeat the validation on a small server endpoint, which is also where the CRM call and its key should live.
A Node job running on one machine
How you'll know: Orders stop syncing the week a laptop is replaced or an old server is switched off.
Fix: Move it to proper hosting with a schedule, a log, retries on failure, and an alert when a run doesn't finish.