Use preconnect for critical third-party origins

SkillMedia

preconnect is a skill for AI agents that guides them through auditing slow page loads. It checks whether browsers preconnect to critical third-party origins and helps verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Available today. Use it from your connected AI after setup.

Have an AI agent that supports loading skills.

Then ask your AI: use the Use preconnect for critical third-party origins skill

What your AI can do with it

  • Audit slow page loads for preconnect-related issues
  • Check whether browsers preconnect to key third-party sites
  • Identify heavy assets and rendering delays tied to third-party origins
  • Verify the actual bottleneck in DevTools, Lighthouse, or field data
  • Recommend preconnect changes only after confirming the cause

Getting started

  1. Have an AI agent that supports loading skills.
  2. Add the preconnect skill to the agent's available skills.
  3. Prepare the page or field data you want audited.
  4. Ask the agent to audit the page load and check preconnect usage on critical third-party origins.

What this skill tells your AI

The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/preconnect/SKILL.md and read by ahel’s review.

Preconnecting to essential origins can shave hundreds of milliseconds off the critical path by handling connection overhead ahead of time.

Quick Reference

  • Establish early connections to important third-party domains (e.g., fonts, APIs)
  • Reduce latency by performing DNS lookup, TCP handshake, and TLS negotiation early
  • Avoid overusing preconnect; limit to 2-4 most critical origins

Check

Review the page's head for preconnect hints and identify any missing or unnecessary connections to third-party domains.

Fix

Add <link rel="preconnect"> for critical third-party origins and remove it for non-essential or underutilized domains.

Explain

Explain how preconnect helps reduce the time spent on connection overhead for third-party resources.

Code Review

Review the routes, assets, and loading behavior that affect Use preconnect for critical third-party origins. Flag exact files, requests, or rendering steps that add unnecessary network, CPU, or layout cost, and describe the measurement method used to confirm the issue.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/performance/preconnect

Signals

GitHub stars
74k
Forks
7k
Last commit
Aug 2026

Questions

When should this skill be used?
Use it when auditing slow page loads, heavy assets, or rendering delays related to preconnect for critical third-party origins.
Should changes be recommended right away?
No. The skill verifies the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Advanced
Item type
skill
Key
preconnect
Source
github.com/thedaviddias/front-end-checklist