Preconnect configured is an important SEO check in the Technical Foundation category. This is a lower-priority optimization. Address it after handling more critical issues.
What this check is really about
Preconnect is a small performance hint you put in your page’s <head> that tells the browser: “you are about to need this other server — start the handshake now.” When your page loads a web font, an analytics script, or images from a CDN, the browser normally waits until it hits that resource before doing the slow part: DNS lookup, TCP connection, and the TLS negotiation. A <link rel="preconnect"> lets that setup happen in parallel, up front, so the resource is ready the moment the page actually asks for it. It shaves real milliseconds off render time on exactly the third-party origins that tend to sit on your critical path.
It is lower-priority because it is an optimisation on top of a working site, and the gains are measured in tenths of a second, not whole seconds. But those tenths land on Largest Contentful Paint and the other Core Web Vitals that Google does weigh, and this is a genuinely low-effort change. It is the kind of polish worth doing once your bigger performance problems are already solved.
Preconnect the origins that matter, and only those
The temptation is to preconnect to everything. Resist it — this is a case where more is worse. Each preconnect opens and holds a connection, and browsers cap how many they will keep warm; spray them at a dozen origins and you crowd out the ones that actually matter, or you waste connections on origins the page barely touches. The discipline is to preconnect only to the handful of third-party origins that are both on the critical rendering path and known in advance: your font provider, your primary CDN, maybe your analytics endpoint.
There is also a lighter-weight cousin worth knowing. Where you know you will eventually need an origin but not urgently, dns-prefetch resolves just the DNS at almost no cost, which is the right tool for lower-priority third parties. Reach for preconnect on the few origins that block your first paint, and dns-prefetch for the rest. Using the heavier hint everywhere is the classic over-optimisation that makes a site slower while feeling faster to configure.
How to Fix This in WordPress
Difficulty Level: EASY – This fix is straightforward and can typically be completed by anyone with basic WordPress knowledge.
Estimated Time: 15 min
A tight, low-risk pass:
- Identify your critical third-party origins. Run the site through a tool like PageSpeed Insights or WebPageTest and look at the network waterfall for the external origins that load early and block rendering — typically fonts, a CDN, and analytics.
- Add preconnect for those, with a crossorigin flag where needed. A font origin loaded with CORS needs
<link rel="preconnect" href="https://fonts.example.com" crossorigin>. Getting thecrossoriginattribute wrong on fonts is the usual reason a preconnect silently does nothing. - Let a plugin manage it if you would rather not touch the head. Most performance and caching plugins have a “preconnect / resource hints” setting where you list the origins. That is the safe route on a client site you do not want to hand-edit.
- Downgrade the non-critical ones to dns-prefetch. Anything that is not on the first-paint path gets the cheaper hint instead of a full preconnect.
Re-run the performance test before and after so you can confirm the connection setup actually moved earlier in the waterfall. If the numbers do not budge, you preconnected to an origin that was not on the critical path — remove it rather than leaving a connection held for nothing.
Recommended Tools & Plugins
These tools can help you fix and prevent this issue:
- Yoast SEO – Comprehensive SEO plugin with built-in checks
- Rank Math – Feature-rich SEO plugin with detailed analysis
- Google Search Console – Free tool to monitor your site’s search presence
- SEO Roadmap – Complete SEO audit and action plan tool
The mistakes I see most often
- Preconnecting to too many origins, which exhausts the browser’s connection budget and slows the ones that matter.
- Omitting the
crossoriginattribute on font preconnects, so the hint is quietly ignored. - Using
preconnectwheredns-prefetchwas the right, cheaper tool. - Adding hints and never re-testing to confirm they actually improved anything.
Need More Help?
If a preconnect is not helping, check the waterfall to confirm the origin is genuinely on the critical path and that the crossorigin flag matches how the resource is fetched. Consult a performance-focused developer for a deeper Core Web Vitals pass, review your caching plugin’s resource-hints documentation, and run a complete site audit with SEO Roadmap for a prioritized action plan.
This guide is part of the SEO Roadmap knowledge base – your complete resource for WordPress SEO optimization.
Last modified: August 2, 2026
United States / English 
Slovensko / Slovenčina 
Canada / Français 
Türkiye / Türkçe