Technical SEO
Preload
Preload is a resource hint telling the browser to fetch a specific resource early, at high priority, because it will be needed for the initial render.
What is preload?
Preload is a resource hint telling the browser to fetch a specific resource early, at high priority, because it will be needed for the initial render. It is declared with a link element.
Why anybody cares
Used on the Largest Contentful Paint image or the hero font it removes a discovery delay that no other optimisation can.
How it is actually done
Applied sparingly to the one or two resources that genuinely gate the first paint, with the correct as attribute so the priority is right.
A frequent error
Preloading many resources removes the benefit, because everything becomes high priority and the browser’s own prioritisation is overridden for no gain.
The definition is simple; the implementation is where the arguments happen.
Where this comes up in the work
It is part of Google Ads Management, and more specifically of Account audit and restructure. Across the rest of the work it shows up in:
- Marketplace Marketing, since deciding which SKUs belong on a marketplace at all is only as good as this is
- Content and Editorial: it is the reason naming a reviewer per page, publicly, so accountability is visible is scoped the way it is
- Lifecycle and Email, because retiring the addresses that are dragging everybody else towards spam depends on it
- Analytics and Measurement, where it quietly limits how far deleting the metrics that have never changed a decision can go
What to check
Two questions that establish whether this is actually in order on a given site:
- Whether anyone has checked it since the last platform or plugin update
- Whether the alert that should catch it reaches a person who can act
Common questions
Who owns preload in a business?
Whoever is accountable for deep linking from an assistant answer to the exact variant rather than a category. Problems with this tend to persist because nobody is.
How much work is preload?
The diagnosis is cheap. The fix ranges from an afternoon to a project depending on how deep it sits in the build, and we scope the second after doing the first.
Should preload come before other work?
High if it is actually broken, low if it is merely imperfect. The check tells you which.
How do you prove preload is worth fixing?
By measuring it rather than by argument. Applied sparingly to the one or two resources that genuinely gate the first paint, with the correct as attribute so the priority is right. The adjacent reading is Home and trade services, and Legal and professional services for the version of this question that comes up later.
Is preload just another name for something?
Preloading many resources removes the benefit, because everything becomes high priority and the browser’s own prioritisation is overridden for no gain. Worth clarifying before agreeing to work on it. App Store Optimization is the page to read before the kickoff call; Brand and Creative is the one to read after it.
Will fixing preload move rankings?
Not on its own, and claims that it does are usually overselling. Used on the Largest Contentful Paint image or the hero font it removes a discovery delay that no other optimisation can. The cheapest version of this is in Server-side rendering or Client-side rendering. The one that lasts is in Subdirectory or Subdomain.
Have the awkward questions answered first
Share the site and the target. We will say what we would check first and what we would leave alone.