WordPress connection and preload hints and the Core Web Vitals
10.2% of audited sites (6,426) combine preconnect and preload hints (68% good LCP, 2.0s median), while 34.9% rely solely on legacy dns-prefetch hints (68% good LCP, 2.0s median).
23.5% of WordPress sites use no resource hints connection and preload hints, and 74% of those sites have a good LCP, against 70% of all WordPress sites.
LCP pass rate
Sites with no resource hints connection and preload hints have a good LCP most often: 74%, against 70% of all WordPress sites. Sites with preconnect hints without preload connection hints have it least often, at 65%.
Connection and preload hints usage
Only dns-prefetch hints is the most used: 34.9% of WordPress sites. No resource hints is 23.5% of WordPress sites.
The four LCP phases
Across the four LCP sub-parts in Chrome's field data, the largest gap between no resource hints and preconnect hints without preload sits in time to first byte (TTFB): 1057 ms median for no resource hints against 1213 ms for preconnect hints without preload. Overall median field LCP is 1.8s for no resource hints (TTFB 1057 ms, load delay 338 ms, load duration 186 ms, render delay 214 ms) versus 2.1s for preconnect hints without preload.
Connection and preload hints per framework
On jQuery, 36% of sites use only dns-prefetch hints connection and preload hints, and 69% of jQuery sites have a good LCP, against 70% of all sites. On Vue, 32% of sites use no resource hints, and 67% of Vue sites have a good LCP.
Connection and preload hints or the framework
Does the framework explain the connection and preload hints difference?
On jQuery, 73% of sites with no resource hints connection and preload hints have a good LCP, against 67% of jQuery sites with only dns-prefetch hints. Within jQuery, sites with no resource hints have a good LCP more often. On Vue, 65% of sites with no resource hints connection and preload hints have a good LCP, against 63% of Vue sites with only dns-prefetch hints. Within Vue, sites with no resource hints and only dns-prefetch hints have a good LCP about equally often.
Why targeted preload and preconnect beat legacy dns-prefetch
dns-prefetch only resolves the domain name, leaving TCP and TLS handshakes on the critical path. Pairing preconnect on critical asset CDNs with preload on the LCP image eliminates both connection and discovery delay. Across 6,426 sites (10.2%) pairing preconnect and preload, 68% pass field LCP (2.0s median), compared with 68% (2.0s median) on the 34.9% using dns-prefetch alone.
Understanding connection and preload hints
Replace legacy wp_resource_hints dns-prefetch entries with targeted <link rel="preload"> for the LCP image and <link rel="preconnect"> for external font or CDN origins. On WordPress, 34.9% of sites emit only dns-prefetch (68% good LCP) while 15.7% use preload (72% good LCP).
By Arjen Karel · 63,295 crawled WordPress sites (36,524 with phone Chrome field data, October 2026). How we measured.