This is the checklist we work through when auditing a funnel or website, whether it is a brand-new build before launch or an existing site that "just feels off". It is organized in the order we actually check things: assets, scripts, links, errors, functionality and finally browsers and devices.
Tick items off as you go. Your progress is saved in this browser only, so you can come back to it later; nothing is sent anywhere.
Open the browser's Developer Tools (F12, or right-click and Inspect) and keep the Console and Network tabs visible throughout. Most of the problems in this checklist show up there first.
1. External static assets
Every file loaded from a server you do not control is a dependency that can slow your page down, disappear or change without warning. On paid traffic, that is a risk you do not need.
2. Tracking & analytics scripts
Funnels accumulate scripts over time: old pixels, abandoned analytics tools, tags added for a test that ended months ago. Each one slows the page and can leak data or fire conversions you do not want.
3. Broken links & missing resources
A broken link on a compliance page can fail a bank review; a missing script can silently break checkout. These issues are easy to fix but only if someone looks.
4. HTTP errors (4xx / 5xx)
Client errors (4xx) usually point to wrong paths or permissions; server errors (5xx) point to something failing on the backend, which is far more serious on a checkout or API endpoint.
5. JavaScript errors
One JavaScript error can stop every script after it from running, including the one that submits the order or fires the pixel.
Documenting third-party errors
You often cannot fix an error inside a vendor's script, but you can make it easy for someone else to. A useful report includes the page URL, the exact error message and stack trace, the library and version, the browser and device, the steps to reproduce it, and whether it affects anything visible such as checkout or tracking. Check for a newer version of the library before reporting; many errors are already fixed upstream.
6. Functional testing
Click everything a customer could click, in the order they would click it. Do it with the console open, and confirm no errors appear during any interaction.
7. Cross-browser & responsive testing
Most paid social traffic arrives on phones, often inside in-app browsers. A funnel that looks perfect in desktop Chrome can still break where most of your buyers are.
Run this checklist again after every significant change, not just before launch. Most of the issues we find on live funnels were introduced by a small edit weeks after the original QA.
Key takeaways
- Serve assets locally or from trusted CDNs, and remove every script you do not need.
- Use the Console and Network tabs to find missing resources, HTTP errors and JavaScript errors.
- Fix custom-code errors; document and report third-party ones with enough detail to reproduce.
- Test the full purchase path, including upsells, CRM records and conversion events.
- Test on real mobile devices, in-app browsers and private mode, not just desktop Chrome.
