# Third Party Scripts > Audit and optimize third-party scripts — analytics, tag managers, chat widgets, embeds — with the right loading strategy, performance budget, facades, and CSP/consent controls. Use when adding a script, when TBT/INP regress, when a GDPR/CCPA consent requirement arises, or before shipping. Not for first-party bundle size (use bundle-optimization) or broad Core Web Vitals diagnosis (use rendering-performance). - Skill: `jaykim88/third-party-scripts` (Agent Skill) - Install (CLI): `npx skillmds@latest add jaykim88/third-party-scripts` - Raw SKILL.md: https://api.skillmd.com/api/skills/jaykim88/third-party-scripts/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - License: MIT - Author: JayKim88 (https://skillmd.com/u/jaykim88) - Updated: 2026-09-10 - Page: https://skillmd.com/skills/jaykim88/third-party-scripts --- # Third-Party Scripts ## Purpose Keep third-party scripts (analytics, tag managers, chat, A/B tools, embeds) from silently destroying performance and privacy. Each script earns its place: right loading strategy, measured cost, CSP-controlled, consent-gated where required. **Universal** — loading-strategy classification, performance budgeting, facade patterns, and CSP/consent controls apply to any site; only the script-injection helper differs by framework. ## Procedure 1. **Inventory every third-party script** - List all external scripts (analytics, tag managers, ads, chat, embeds, hosted fonts) - For each: purpose, owner, business-critical? — scripts with no owner or unclear purpose are removal candidates 2. **Assign a loading strategy per script** - **Critical & needed early** (consent manager, core analytics) → load high priority, but still async - **Important, not render-blocking** (most analytics) → load after hydration / when the main thread is idle - **On-interaction only** (chat widget, video embed) → lazy-load on click / scroll via a **facade** - Never inject a render-blocking synchronous `