# Non-critical third-party scripts defer-loaded or async
- **Pattern:** `ab-002011` (`performance-core.script-style-efficiency.third-party-async`)
- **Severity:** high
- **Lifecycle:** active
- **Last modified:** 2026-04-18
- **Canonical URL:** https://auditbuffet.com/patterns/ab-002011
- **License:** CC-BY-4.0 — attribute to AuditBuffet Pattern Catalog (https://auditbuffet.com/patterns/ab-002011)
## Why it matters
Synchronous third-party scripts in `` block HTML parsing from the moment the browser encounters them (ISO-25010 time-behaviour). A page with four analytics and marketing scripts loading synchronously — Google Analytics, Segment, Drift, Intercom — commonly adds 200–400ms of render-blocking time before any content displays. That delay is entirely external to your codebase: network latency, third-party CDN performance, and script execution time are all out of your control, yet they block your page from rendering.
## Severity rationale
High because synchronous third-party scripts block the entire HTML parsing pipeline, adding uncontrolled latency from external CDNs before any first-party content can render.
## Remediation
Move all non-critical third-party scripts to `async` or `defer` loading. Analytics, chat widgets, and pixel trackers are never critical for initial render:
```html
```
For the heaviest scripts (chat widgets, heatmap tools), delay loading until after the page is interactive:
```ts
// src/components/providers.tsx
if (typeof window !== 'undefined') {
window.addEventListener('load', () => {
const script = document.createElement('script')
script.src = 'https://js.intercomcdn.com/shim.latest.js'
document.body.appendChild(script)
})
}
```
With Next.js `
```
## External references
- iso-25010 performance-efficiency.time-behaviour
Taxons: performance
HTML version: https://auditbuffet.com/patterns/ab-002011