SiteTraceKit Glossary
What are third-party scripts?
Third-party scripts are common on modern websites. They can add useful functionality, but they also create dependencies that deserve visibility.
Short definition
A third-party script is JavaScript loaded from a domain that is not the website's own domain or subdomain.
Simple example
Examples include analytics tags, payment widgets, chat tools, video embeds and consent platforms.
Why it matters for website checks
External scripts can influence loading speed, privacy documentation, consent flows, reliability and vendor governance.
Limits
A script URL alone does not prove what data is processed. Static HTML checks can also miss scripts loaded later by JavaScript.
What does this mean for website owners?
Use the signal as a starting point for manual review. The website’s purpose, technical environment and actual configuration provide the necessary context.
Matching checker
Third-Party Services Checker - Map visible external resource domains into categories such as analytics, ads, CDN, fonts, payments and chat.
FAQ
Are third-party scripts always a problem?
No. Many sites need them. The useful question is whether they are understood, documented and intentionally loaded.
Can SiteTraceKit see scripts loaded after page interaction?
No. It does not run a browser or execute third-party JavaScript.
Why group external domains by category?
Categories make the review easier for non-technical stakeholders than a raw list of resource URLs.