Preconnect added for third-party origins
Why it matters
Every third-party origin requires a separate TCP connection and TLS handshake before the browser can send its first byte. On a typical network, that overhead is 100–300ms per origin (ISO-25010 time-behaviour). A page loading from fonts.googleapis.com, fonts.gstatic.com, and a CDN without preconnect directives pays that cost three times over — sequentially, if the browser has not yet opened those connections. The most visible symptom is delayed web font rendering, which blocks text display and contributes to layout shift.
Severity rationale
Info because each missing preconnect adds 100–300ms of connection overhead per third-party origin, but the impact is bounded and depends on the number of distinct origins used.
Remediation
Add <link rel="preconnect"> in <head> for the 3–4 origins used in the first 5 seconds of page load. Use dns-prefetch for lower-priority origins to avoid wasting TCP connections:
<!-- Google Fonts requires two origins -->
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<!-- Analytics: preconnect if loaded early -->
<link rel="preconnect" href="https://www.google-analytics.com">
<!-- Lower-priority third party: DNS only, no TCP socket held open -->
<link rel="dns-prefetch" href="https://cdn.example.com">
Limit total preconnect directives to 4. Each one holds a TCP socket open; exceeding that for rarely-used origins wastes browser connection budget.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Performance Core Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- iso-25010:2011 · performance-efficiency.time-behaviour — Time Behaviour
Taxons
History
- 2026-04-18·v1.0.0·Initial import from performance-core·automated