This specification defines the preconnect relationship and extends the preload relationship of the HTML Link Element (``). These primitives enable the developer, and the server generating or delivering the resources, to assist the user agent in the decision process of which origins it should connect to, and which resources it should fetch to improve page performance.
Modern browsers leverage a wide variety of speculative optimization techniques to anticipate user input and intent, which allows them to hide some of the networking, processing, and rendering latencies: preconnects, early fetching of resources, and preloading and processing of resources for subsequent navigation.
The decision to initiate one or more of the above optimizations is typically based on heuristic rules based on document markup and structure, navigation history, and context of the user - e.g., type of device, available compute and memory resources, network connectivity, user preferences, and so on. These techniques have proven to be successful, but can be further improved by leveraging the knowledge a developer has about the front-end and back-end generation and delivery of the resources of a web application.
For example, the application may provide the following resource hints to the user agent:
Many web applications already leverage a variety of prefetching techniques. This includes, but is not limited to, using `XMLHttpRequest` to fetch and cache assets before they are needed. However, these implementations are application specific, are not interoperable, and do not provide the same level of performance as the browser-provided primitives. Worse, these implementations sometimes conflict with the browser logic and result in delayed or unnecessary resource fetches that degrade overall page performance.
This specification defines the preconnect relationship and extends the preload relationship of the HTML Link Element (``). These primitives enable the developer, and the server generating or delivering the resources, to assist the user agent in the decision process of which origins it should connect to, and which resources it should fetch to improve page performance.
The preconnect relation is used to indicate an origin that will be used to fetch required resources. Initiating an early connection, which includes the DNS lookup, TCP handshake, and optional TLS negotiation, allows the user agent to mask the high latency costs of establishing a connection.
<link rel="preconnect" href="//example.com">
<link rel="preconnect" href="//cdn.example.com">
The optimal number of connections per origin is dependent on the negotiated protocol, users current connectivity profile, available device resources, and other context specific variables. As a result, this decision is deferred to the user agent, which is in the best position to determine the optimal number of connections per origin.
The user agent SHOULD initiate the handshake as early as possible and perform the full connection handshake (DNS+TCP for HTTP, and DNS+TCP+TLS for HTTPS origins) whenever possible, but is allowed to elect to perform a partial handshake (DNS only for HTTP, and DNS or DNS+TCP for HTTPS origins), or skip it entirely, due to resource constraints or other reasons.
The preload relationship is used to declare a resource and its fetch properties. This specification extends its functionality with additional processing policies that enable efficient fetching of resources that may be required by the next navigation, such that the user agent can deliver a faster response once the resource is requested.
<!-- fetch and preprocess for next navigation -->
<link rel="preload" href="//example.com/next-page.html" as="html" loadpolicy="next">
<!-- fetch and do not preprocess for next navigation -->
<link rel="preload" href="//example.com/next-component.html" as="html" loadpolicy="next inert">
This specification extends the loadpolicy of preload relation, which consists of a space-separated set of the keywords that determine the load and processing policy of the specified resource:
<link rel="preload" href="/assets/font.woff" as="font" loadpolicy="next">
<link rel="preload" href="/assets/logo.webp" as="image" loadpolicy="next inert">
Resource fetches that may be required for the next navigation can negatively impact the performance of the current navigation context due to additional contention for the CPU, GPU, memory, and network resources. To address this, the user agent MUST implement logic to reduce and eliminate such contention:
Speculative preload hints may be combined with other preload policies:
The above processing strategies are not an exhaustive list. The user agent MAY implement other and additional strategies.
To ensure compatibility and improve the success rate of prerendering requests the target page should use the [[PAGE-VISIBILITY]] to determine the visibility state of the page as it is being rendered and implement appropriate logic to avoid actions that may cause the preload to be abandoned (e.g. non-idempotent requests), or unwanted side-effects from being triggered (e.g. analytics beacons firing prior to the page being displayed).
In addition to specifying the hint type, its fetch parameters, and the resource URL, the developer can communicate the expected probability that the specified resource hint will be used.
<link rel="preconnect" href="//cdn.example.com" pr="0.42">
<link rel="preload" href="//example.com/next-page.html" pr="0.75" loadpolicy="next">
<link rel="preload" href="//example.com/thankyou.html" pr="0.25" loadpolicy="next">
The pr attribute is a float value in the [0.0-1.0] range that MAY be used in the following cases:
preconnect relation to indicate probability of initiating a fetch against the specified origin, either within the current navigation context, or within the next navigation context.speculative preload relation to indicate probability of using the specified resource within the next navigation context.
If the pr attribute is omitted for above cases, the user agent MAY assign a default probability value based on own heuristics, past navigation data, and so on.
A hint probability of 1.0 does not guarantee that the hint will be executed by the user agent. Resource hints MAY be processed on a best effort basis by the user agent, and decision to process the hint MAY be based on the runtime context of the user agent — availability of CPU, GPU, memory, and networking resources — developer specified probability indicating the likelihood of that resource being used, specified user preferences, and other variables. The user agent MAY decide to:
preconnect MAY fallback to a partial handshake (DNS only, or DNS+TCP for HTTPS origins).speculative preload MAY fallback to preconnect for specified origin, or apply a custom preprocessing strategy for the target resource, and if applicable, its sub-resources: preconnect only; fetch the target resource but defer fetch of sub-resources; fetch sub-resources but delay their processing, and so on.To optimize the overall user experience the user agent should account for local context and specified probability of a speculative hint. For example, on a resource constrained device the user agent may decide to only execute high probability hints. Alternatively, it may decide to perform partial processing of the hint, such as downgrading speculative preload to a preconnect, performing partial preprocessing, and so on. Performing a partial optimization allows the user agent to improve performance even if a full optimization cannot be performed. Conversely, on a device with sufficient resources, the user agent may execute all of the specified hints as far as possible.
The user agent MUST NOT delay the `load` event of the document due to outstanding preconnect or speculative preload initiated requests.
The decision on whether a resource hint is executed, and if so, whether full or partial processing is applied is deferred to the user agent. As a result, element-level `load` and `error` JavaScripts events are not guaranteed to fire, and if they do, do not guarantee that full processing was applied. However, the user agent SHOULD fire the appropriate `load` and `error` events when possible, to allow the application to track which hints were executed and when.
In addition to the hints specified in the document markup, the application may dynamically insert and remove additional resource hints based on user context or other signals. The user agent SHOULD process dynamically inserted resource hints in addition to, and in the same way as, markup-declared hints.
// insert new preload hint
var hint = document.createElement("link");
hint.rel = "preload";
hint.loadpolicy = "next";
hint.href = "/article/part3.html";
document.head.appendChild(hint);
// remove preload hint (UA may cancel request)
document.head.removeChild(hint);
The application can use dynamic scheduling to react and adapt to user initiated actions - e.g. initiate a speculative resource fetch in response to recent user activity, cancel previous speculative fetch, and so on.
The decision to cancel a preconnect or speculative preload request is deferred to the user agent, which MAY use local context and other signals to determine if and when the optimization should be aborted. For example, the removal of the hint element from the document MAY be used as a signal that the requested optimization is no longer necessary and should be aborted - see .
The user agent SHOULD allow the optimization to continue across navigations. However, the user agent MAY cancel these requests once it determines that they are not required by the new destination - see .
A user agent that supports [[!RFC5988]] SHOULD process resource hints specified via the Link HTTP header. The application can provide one or more preload relations via multiple HTTP headers or via a comma separated list.
Link: <https://example.com>; rel=preconnect
Link: <https://example.com/next-page.html>; rel=preload; as=html; loadpolicy=next inert;
Link: <https://example.com/logo-hires.jpg>; rel=preload; as=image; media=min-resolution:2dppx; loadpolicy=next
The full resource URL may not be known until the page is being constructed by the user agent - e.g. conditional loading logic, UA adaptation, etc. However, the origin from which one or more of these resources will be fetched is often known ahead of time by the developer or the server generating the response. In such cases, a preconnect hint can be used to initiate an early connection handshake such that when the resource URL is determined, the user agent can dispatch the request without first blocking on connection negotiation.
Many sites rely on redirect services for analytics, malware protection, and to anonymize the referrer before sending the user to the final destination. Because the destination is known ahead of time, a preconnect hint can be used to initiate the connection handshake with the destination origin (without revealing any private information) in parallel with the processing of the redirect - this masks the redirect latency and reduces navigation time to final destination.
The preload hint can be used to implement a prefetch strategy that leverages app-specific knowledge about the next navigation based on content, structure, analytics, or other signals - e.g. high-likelihood search results, paginated content or step-driven flows, aggregated analytics or per-user behavior, and so on.
For example, an image gallery may have knowledge about the likelihood of the next photo or page that may be requested by the user. To provide an improved experience the application can ask the user agent to begin fetching required resources (individual photos, critical resources, or the full page) before the next navigation is triggered.
To achieve the above behavior the application can specify one or more preload relations, set their loadpolicy to next to indicate that the resources are intended for next navigation, and optionally specify the probability (via pr attribute) of each resource being used.
The preload hint can be used to implement a "reactive prefetch strategy" that leverages the knowledge of where the user is heading next and enables the application to begin prefetching critical resources in parallel with the navigation request.
To achieve the above behavior the application can listen for click events and dynamically insert relevant speculative preload relations for critical resources required by the next navigation. In turn, the user agent can fetch the hinted resources in parallel with the navigation request, making the critical resources available sooner.
The enabling feature of this strategy is that requests initiated via speculative preload relation may be allowed to persist across navigations.
The preload hint can be used to prerender the destination page, enabling an instant navigation experience once the user triggers the navigation.
To deliver an instant navigation experience the application can specify one or more preload relations, each of which points to a destination page (an HTML resource), and set their loadpolicy to next to indicate that the resources are intended for the next navigation. In turn, the user agent may fetch and process the HTML document, fetch its subresources, and perform other work to deliver an instant navigation - i.e. prerender the page. Alternatively, if the application wants to only prefetch the HTML response, it can set the loadpolicy to `next inert`, to indicate that the response should not be prerendered.
Finally, because prerendering may require a lot of resources, the application can specify the probability (via pr attribute) of each target to help the user agent deliver the best user experience.
This document reuses text from the [[!HTML]] specification, edited by Ian Hickson, as permitted by the license of that specification.