Adding preconnect for every third-party domain is not a reliable WordPress speed fix. Keep a hint only when you can identify the critical request it helps and verify that the browser can reuse the connection. Old font providers, removed widgets and duplicate optimization plugins often leave hints that no longer have a useful job.
The web.dev resource-hints guide explains that preconnect opens an early connection to another origin. It recommends prioritizing critical origins and matching CORS behavior for resources such as font files. A hint prepares a connection; it does not prove that a file loads or that the page becomes faster.
Inventory the Hints Actually Served
Inspect the public page response and its Link headers, then check the hydrated document. Record each preconnect origin, its crossorigin setting and the theme or plugin that emits it. Look for duplicates added by a performance plugin, theme settings and custom header code.
Keep the origin distinct from a resource URL. A font stylesheet host and the host serving the actual font file can be different. Use the Network panel to find the final request destination rather than copying a domain from a years-old optimization checklist.
| Candidate |
Evidence needed |
| Critical font host |
A font used in the first visible content |
| Image CDN |
An important image actually served from that origin |
| Removed chat vendor |
No current request means no demonstrated benefit |
| Same-site asset host |
Confirm it is really a separate origin |
Do not interpret a missing font as a missing preconnect. A 404, blocked request or incorrect CSS declaration needs a functional repair first. Use the custom font loading guide when the typeface never appears.
Origin: Actual final resource host. Mode: Match font CORS behavior. Benefit: Repeat controlled comparisons. Privacy: Review early vendor contact. Explanatory checklist, not a customer test result.
Test One Candidate Against a Baseline
Use a representative landing page and repeat measurements under the same device, network and cache conditions. Compare several runs with and without one hint on staging. Record connection setup and the timing of the resource it was meant to help, alongside the page's largest visible content.
Do not accept a single faster run as proof. Network variability can overwhelm a small optimization. If the hint is discovered almost as late as the resource, or the connection was already available, its practical value may be small.
For a cross-origin font, inspect whether the connection mode matches the font request. An incorrectly configured hint can open a connection that is not reused. Treat preload as a different decision: it fetches a specific resource rather than merely preparing its origin.
Include Consent and Vendor Review
An early network connection still contacts a third-party server. Review proposed hints against your site's approved vendor and consent behavior, especially for optional tracking or embedded media. Do not add speculative connections to every marketing service simply because no script has executed yet.
This is an implementation check, not a legal determination. Your privacy owner should decide which external contacts are appropriate for each visitor state.
What Should the Final Change List Say?
Name the removed duplicate, the retained origin, the request it supports and the measured comparison. Keep the change only if its purpose remains clear after plugins or providers change. Request a focused performance review when competing optimization layers make the emitted hints difficult to trace.
References reviewed October 15, 2026. Examples are explanatory, not customer test results.