When a Third-Party Tool Isn’t Loading

Purpose

Help diagnose when a third party tool is not loading after Speed Layer installation.

Step 1: Confirm the issue is real and repeatable

• Test in an incognito window.
• Test on mobile and desktop if possible.
• Note which pages are affected.

Step 2: Check whether the tool is blocked by consent settings

Some tools are intentionally gated by consent or regional rules.

Step 3: Check the browser console for errors

Console errors often point to:

• A missing dependency script
• A script conflict
• A blocked network request

Public reference:

• Google: Chrome DevTools console overview https://developer.chrome.com/docs/devtools/console/

Step 4: Check network requests

Look for the vendor domain in the Network tab.

• If requests are missing, the script may not be inserted.
• If requests fail, it may be blocked by CSP, ad blockers, or network issues.

Public reference:

• Google: Chrome DevTools network overview https://developer.chrome.com/docs/devtools/network/

Step 5: Validate script placement and installation

If Speed Layer is installed incorrectly, script coordination can be unreliable.

See: Speed Layer Basic Installation.

Step 6: Escalate

If the tool is critical and still not working, capture:

• Page URL
• Tool name
• Steps to reproduce
• Console errors and screenshots

Then contact support.

Related pages

• How to Identify Script Conflicts
• When to Contact Support
• Basic Troubleshooting Checklist