Preconnect Hints
Checks for <link rel="preconnect"> to critical third-party origins.
What this check measures
We look for preconnect hints to origins used for fonts, analytics, CDN assets. Preconnect saves 100-300ms per origin on first connection.
Why it matters
Without preconnect, the browser only connects to third-party origins when it encounters the first asset reference — late, costing 100-300ms per origin. Preconnect hints start the handshake early.
How our audit detects it
Parse <link rel="preconnect"> tags. Compare against third-party origins used elsewhere on the page.
Typical findings
- error_outlineGoogle Fonts used without preconnect to fonts.googleapis.com and fonts.gstatic.com.
- error_outlineCDN used but no preconnect for the CDN origin.
How to fix
Add preconnect for every third-party origin that serves critical path assets. Include `crossorigin` for font hosts.
Frequently asked questions
How many preconnects is too many?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
SSR / Pre-rendering
Checks if the page is server-rendered or statically pre-rendered.
TechnicalHTTP Status Codes
Checks that pages return proper status codes — 200 for live, 404 for missing, 301 for moved.
TechnicalNo Client-Side Redirects
Checks that redirects happen server-side, not via JavaScript.
TechnicalViewport Meta Tag
Checks for <meta name="viewport" content="width=device-width, initial-scale=1">.