Optimize third-party script loading
SkillMediathird-party-scripts is a skill that guides an AI agent through diagnosing whether third-party scripts are slowing down web pages. It covers auditing slow page loads, heavy assets, and rendering delays related to optimizing third-party script loading. The skill emphasizes verifying the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Use Optimize third-party script loading in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Optimize third-party script loading and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Optimize third-party script loading skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Have access to the web pages and performance data you want to audit, such as DevTools, Lighthouse, or field data.
What your AI can do with it
- Audit slow page loads, heavy assets, and rendering delays tied to third-party scripts
- Verify the actual bottleneck using DevTools, Lighthouse, or field data
- Diagnose whether third-party scripts are causing slowdowns before recommending changes
- Guide analysis of rendering delays related to third-party script loading
Getting started
- Have access to the web pages and performance data you want to audit, such as DevTools, Lighthouse, or field data.
- Add the third-party-scripts skill to your agent's available skills.
- Ask the agent to audit a page for slow loads, heavy assets, or rendering delays.
- The agent will verify the actual bottleneck before recommending any changes.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/third-party-scripts/SKILL.md and read by ahel’s review.
Third-party scripts are the #1 cause of slow websites—unoptimized loading can add 2-5 seconds to your page load time.
Quick Reference
- Use async for independent scripts (analytics, ads)
- Use defer for DOM-dependent scripts (chat widgets, social)
- Lazy-load non-critical scripts after page load
- Consider self-hosting critical third-party scripts
Check
Analyze third-party scripts on this page to ensure they use async/defer and don't block rendering.
Fix
Add async or defer attributes to third-party scripts and consider lazy loading non-critical scripts.
Explain
Explain the performance impact of third-party scripts and strategies to minimize their blocking effect.
Code Review
Review the routes, assets, and loading behavior that affect Optimize third-party script loading. Flag exact files, requests, or rendering steps that add unnecessary network, CPU, or layout cost, and describe the measurement method used to confirm the issue.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/performance/third-party-scripts
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Oct 2026
Questions
- When should this skill be used?
- Use it when auditing slow page loads, heavy assets, or rendering delays related to optimizing third-party script loading.
- Does it recommend changes right away?
- No. It verifies the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
- What tools does it use for diagnosis?
- DevTools, Lighthouse, or field data.
Advanced
- Item type
- skill
- Key
third-party-scripts- Source
- github.com/thedaviddias/front-end-checklist
github.com/thedaviddias/front-end-checklist