SEO

Preload and Preconnect

Also called resource hints, rel preload, rel preconnect

Hints that tell the browser to fetch a critical file, or open a connection, earlier than it otherwise would.

Quick facts: Preload and Preconnect

Category
SEO
Also called
resource hints, rel preload, rel preconnect
Level
Advanced
Affects
Largest Contentful Paint, font loading, when rendering starts
Where to see it
Chrome DevTools Network and Performance panels, PageSpeed Insights, Lighthouse
In this article4
  1. How preload and preconnect work
  2. Why preload and preconnect matter
  3. Common mistakes with preload and preconnect
  4. How to act on it

How preload and preconnect work

A browser builds a page by reading the HTML from the top down and fetching whatever it meets along the way. That order is frequently wrong. The hero image may be referenced inside a stylesheet and the web font inside another file, so the browser only discovers them after it has already spent time on things the visitor cannot see yet.

Resource hints correct the order. Preload tells the browser to fetch one named file straight away because the page will certainly need it — normally the font or the main image on the first screen. Preconnect is lighter: it fetches nothing, it simply opens the connection to another domain in advance, so the handshake is already done by the time a real request arrives.

Why preload and preconnect matter

Both attack waiting rather than weight. Nothing becomes smaller; the delays simply overlap instead of stacking up. On a page whose biggest visible element is a hero image or a heading in a custom font, that overlap is often the difference between a page that feels immediate and one that flashes blank first, and it shows directly in Largest Contentful Paint.

They matter most where connections are slow to set up. On mobile data the handshake with a new domain costs real time, so a page pulling fonts from one host, analytics from another and a chat widget from a third pays that cost three times over before it has drawn anything.

Common mistakes with preload and preconnect

Overuse is the standard failure. Priority only exists in relation to something else, so if you preload everything you have prioritised nothing, and the genuinely urgent file now queues behind files that were never urgent. A page that preloads a whole font family, several images and a script is usually slower than the same page preloading nothing at all.

The second mistake is hinting at files the browser already finds immediately. An image referenced high in the HTML needs no help; the hint just adds a line to maintain. The third is preconnecting to domains the page contacts late, or no longer contacts at all, which holds connections open for nothing.

How to act on it

Start from a measurement rather than a checklist. Load the page with the browser’s network panel open, find what the largest visible element is waiting for, and hint at that one thing. Add a preconnect only for a host that is contacted early and belongs to something the visitor actually sees.

Then measure again and keep the hint only if it changed the result. Hints are cheap to add and easy to forget, so they accumulate quietly; review them whenever the design or the font stack changes. Treat them as a final refinement rather than a cure — if the first screen is heavy, or held up by render-blocking files, reordering the queue only rearranges the same wait. That deeper work is what a page speed engagement deals with first.

Do and do not

Do

  • Preload only the font or image the first screen needs
  • Preconnect to domains the page contacts immediately
  • Measure before and after, and remove hints that change nothing

Do not

  • Preload files the browser already discovers early
  • Preconnect to a long list of domains
  • Use hints to disguise a page that is simply too heavy

Questions people ask about this

What is the difference between preload and preconnect?

Preload fetches one specific file early because you already know the page needs it. Preconnect fetches nothing; it opens the connection to another domain ahead of time so the handshake is finished when a request finally arrives. Preload is for files you can name. Preconnect is for hosts you will certainly use but whose files you cannot list in advance.

Can preloading actually make a page slower?

Yes. Bandwidth is finite, so anything you preload takes capacity from something else. Preload a font, a few images and a script together and the browser must juggle them all before it can settle, which delays the very element you were trying to speed up. Preload sparingly, and only what the first screen genuinely needs to appear.

Do resource hints affect search rankings?

Only through the experience they change. Google does not look for the tags themselves and gives no credit for having them. If a hint makes the main content appear sooner for real visitors, that improvement can show up in the page experience signals Google does use. If the page was already quick, adding hints changes nothing worth measuring.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.