External resources are loaded without preconnect or dns-prefetch hints, causing additional latency for critical scripts and stylesheets.
By Seoxpert Editorial · Published · Updated
Without preconnect hints, browsers delay loading external resources due to extra DNS and connection setup steps. This increases page load times and can negatively affect Core Web Vitals metrics like Largest Contentful Paint (LCP), impacting both user experience and SEO rankings.
Leaving this unresolved can slow down critical resource loading, harming page speed and SEO performance.
Automated crawlers scan for external scripts or stylesheets and check if corresponding <link rel="preconnect"> or <link rel="dns-prefetch"> tags exist in the <head>.
Problem: No preconnect for external CDN
<!-- Loads stylesheet from external CDN, but no preconnect -->
<link rel="stylesheet" href="https://cdn.example.com/styles.css">Fix: Add preconnect for external CDN
<!-- Preconnect hint added for external CDN -->
<link rel="preconnect" href="https://cdn.example.com">
<link rel="stylesheet" href="https://cdn.example.com/styles.css">Add preconnect hints for critical origins that affect above-the-fold content or LCP. Use dns-prefetch for less critical resources.
Yes, preconnect can reduce connection setup time, improving metrics like LCP and TTFB.
dns-prefetch only resolves DNS. Preconnect also establishes TCP and TLS, offering greater performance benefits for critical resources.
Place <link rel="preconnect"> tags as early as possible in the <head> section.
Run a scan to see if External Resource Origins Without Preconnect Hints affects your pages.
Scan my website →