In this guide, we’ll walk you through how to use Preload Requests effectively for optimizing your website’s performance. Let’s dive into the details and get started.<\/p>\r\n

\r\n

<\/div>\r\n

\r\n

Speed Up Your WordPress Website.<\/strong><\/p>\r\n

Unlock the ability to Preload Requests by upgrading to W3TC Pro.<\/p>\r\n<\/div>\r\n

\r\n
View Plans<\/a><\/p>\r\n<\/div>\r\n<\/div>\r\n<\/div>\r\n<\/div>\r\n
Step 1: Enable Preload Requests<\/h2>\r\n
To enable preloading in W3 Total Cache:<\/p>\r\n
\r\n
Login to WordPress<\/li>\r\n
Go to Performance > General Settings<\/strong><\/li>\r\n
Click on User Experience<\/strong> in the top sub-nav<\/li>\r\n
Check the box to enable <\/span>Preload Requests <\/b>and then click on <\/span>Save Settings<\/b><\/li>\r\n<\/ol>\r\n\r\n
$\"Preload$ <\/figure>\r\n
<\/p>\r\n
<\/p>\r\n
<\/p>\r\n
<\/p>\r\n
Step 2: Configure Preload Requests<\/h2>\r\n
The next step is to configure the feature by navigating to <\/span>Performance > User Experience<\/b>. There will be a new section titled <\/span>Preload Requests<\/b> towards the bottom of the page.<\/span><\/p>\r\n
DNS Prefetch Domains<\/b><\/h3>\r\n
This<\/span> <\/b>textarea <\/span>allows users to input a list of domains that browsers will use to resolve domain names to IP addresses in advance. It resolves DNS queries before they are needed, anticipating the need for future requests to specific domains. This helps in reducing DNS resolution time when actual requests are made, improving the perceived website load time.<\/p>\r\n
<\/p>\r\n
$\"DNS$ <\/figure>\r\n
<\/p>\r\n
<\/p>\r\n
<\/p>\r\n
Preconnect Domains<\/b><\/h3>\r\n
This<\/span> textarea allows users to input a list of domains that should be preconnected by the browser. Preconnect goes beyond DNS prefetching. It not only resolves the DNS but also initiates a connection to the server and performs the necessary handshake (e.g., TCP handshake, TLS negotiation). It establishes a complete network connection to the specified domain, enabling the browser to fetch resources more quickly when requested, as it has already set up the necessary network infrastructure.
<\/span><\/p>\r\n
<\/p>\r\n
$\"\"$ <\/figure>\r\n
<\/p>\r\n
Note: <\/strong>Preconnecting to an excessive number of domains can overwhelm browsers and actually hinder overall performance, as each connection consumes resources. It’s crucial for web developers to analyze and prioritize which third-party domains should be preconnected in order to maximize efficiency of website loading.<\/div>\r\n
Preload<\/b><\/h3>\r\n
These <\/b>textareas allow users to specify various file URLs that should be preloaded in the browser’s cache before the page is rendered, thereby improving the page’s load performance and rendering speed for subsequent requests. There are separate textareas for CSS, JavaScript, fonts, images, videos, audio, and documents.<\/p>\r\n\r\n
$\"Preload$ <\/figure>\r\n\r\n\r\n\r\n
$\"Preload$ <\/figure>\r\n\r\n\r\n\r\n
$\"Preload$ <\/figure>\r\n\r\n\r\n\r\n
$\"Preload$ <\/figure>\r\n\r\n\r\n\r\n
$\"Preload$ <\/figure>\r\n\r\n\r\n\r\n
$\"Preload$ <\/figure>\r\n\r\n\r\n\r\n
$\"Preload$ <\/figure>\r\n\r\n
How to Confirm DNS Prefetch is Active<\/h2>\r\n
Detecting whether DNS prefetching is working involves checking the browser’s behavior and inspecting network requests. Here is how to determine if DNS prefetching is functioning using the browser development tools:<\/p>\r\n
\r\n
Chrome: Open Chrome DevTools (right-click on the page, select “Inspect”, and go to the “Network” tab). Select the URL of your site on the left, then click Response on the right. Use the search box at the bottom to find “DNS”. These entries indicate that DNS prefetching is taking place.<\/li>\r\n
Firefox: Similarly, open Firefox Developer Tools and go to the “Network” tab. Look for entries labeled “DNS” or “Prefetch.”<\/li>\r\n<\/ul>\r\n
$\"DNS$ <\/a><\/p>\r\n
How to Confirm Preload is Active<\/h2>\r\n
In this example we’re going to see how an image loads higher in priority after being added to preload settings, using the browser’s developer tools. Start these steps before adding your URL to the preload settings. <\/p>\r\n
\r\n
Right click the page, click Inspect<\/strong> and then the Network<\/strong> tab.<\/li>\r\n
Reload the page, and you will see how the elements load by default. In this example, the image ten.jpg<\/em> loads last on the page.
$\"Before$ <\/a><\/li>\r\n
Navigate to Performance > User Experience > Preload <\/b>and add your URL to the appropriate section.<\/li>\r\n
Return to the page.<\/li>\r\n
Right click the page, click Inspect and<\/strong> then the Network<\/strong> tab again.<\/li>\r\n
Reload the page, and you will see your element load higher in priority. In this example, ten.jpg<\/em> now loads before some other images. The images in the immediate viewport will always load first.
$\"After$ <\/a><\/li>\r\n<\/ol>\r\n
Learn More about Preloading Requests<\/h2>\r\n
Want to learn more about what these techniques are in-depth? We’ve got you covered!<\/p>\r\n
DNS Prefetching<\/h3>\r\n
DNS prefetching is a technique used by web browsers to improve the performance of web page loading. The Domain Name System (DNS) is responsible for translating human-readable domain names (like www.example.com) into IP addresses that computers use to locate and connect to each other on the Internet.<\/p>\r\n
When you visit a website, your browser needs to resolve the domain name to an IP address before it can fetch the web page. DNS prefetching anticipates the need for these translations and resolves the domain names in advance, before they are actually requested by the user. By doing so, the browser can reduce the latency associated with DNS resolution and make the web page load faster.<\/p>\r\n
Here’s how DNS prefetching typically works:<\/p>\r\n
\r\n
\r\n
Parsing HTML<\/strong>: When parsing the HTML of a web page, the browser identifies domain names embedded in links, scripts, or other resources.<\/p>\r\n<\/li>\r\n
\r\n
Prefetching DNS<\/strong>: The browser then proactively performs DNS resolution for these domain names in the background, even before the user clicks on a link or requests the resource.<\/p>\r\n<\/li>\r\n
\r\n
Caching<\/strong>: The resolved DNS information is cached by the browser so that subsequent requests for the same domain can be served more quickly without needing to perform another DNS lookup.<\/p>\r\n<\/li>\r\n<\/ol>\r\n
By prefetching DNS information, the browser can reduce the time it takes to establish connections and retrieve resources, thus improving the overall perceived speed and responsiveness of the web page.<\/p>\r\n
Preconnecting<\/h3>\r\n
Preconnecting is a technique used by web browsers to establish network connections in advance, before they are actually needed to load a particular resource. This is done to reduce latency and improve the overall performance of web pages. Preconnecting is particularly useful for resources hosted on different domains, such as external scripts, stylesheets, or images.<\/p>\r\n
Here’s how preconnecting typically works:<\/p>\r\n
\r\n
\r\n
Identifying Resources<\/strong>: As the browser parses the HTML of a web page, it identifies external resources (like scripts, stylesheets, or images) that will be required to render the page.<\/p>\r\n<\/li>\r\n
\r\n
Initiating Connections in Advance<\/strong>: Instead of waiting until the browser encounters a link or resource that needs to be fetched, the browser proactively initiates network connections (TCP connections) to the servers hosting these resources. This is done in the background, before the user explicitly requests the resource.<\/p>\r\n<\/li>\r\n
\r\n
Reducing Latency<\/strong>: By establishing connections in advance, when the user eventually clicks on a link or requests a resource, the connection is already established or in the process of being established. This can significantly reduce the time it takes to establish a network connection and retrieve the resource, resulting in a faster page load time.<\/p>\r\n<\/li>\r\n<\/ol>\r\n
Preconnecting can be done using specific HTML tags, such as <link><\/code> with the rel=\"preconnect\"<\/code> attribute, or programmatically through JavaScript. The specific implementation details may vary between browsers.<\/p>\r\n
It’s worth noting that while preconnecting can improve performance, it should be used judiciously to avoid unnecessary network overhead.<\/p>\r\n
Preloading<\/h3>\r\nPreloading is a technique used in web development to initiate the early loading of certain resources, such as images, scripts, stylesheets, or fonts, before they are explicitly requested by the user or the web page. The goal is to optimize the performance of a website by reducing latency and improving the overall user experience.<\/p>\r\n Here’s how preloading typically works:<\/p>\r\n \r\n\r\nIdentifying Critical Resources<\/strong>: Web developers analyze their web pages to identify critical resources that are essential for rendering or functionality. These can include images, scripts, stylesheets, or other assets.<\/p>\r\n<\/li>\r\n \r\nAdding Preload Tags<\/strong>: Developers include preload tags in the HTML of the web page to instruct the browser to start fetching these critical resources as early as possible. The <link><\/code> tag is commonly used for this purpose, and it may have attributes like rel=\"preload\"<\/code> to indicate the resource type and as<\/code> to specify the type of the resource.<\/p>\r\n<\/li>\r\n \r\nFetching in the Background<\/strong>: When the browser encounters these preload tags, it initiates the fetching of the specified resources in the background, parallel to other page loading tasks.<\/p>\r\n<\/li>\r\n \r\nCaching<\/strong>: Once fetched, the resources are cached by the browser. When the same resource is later requested during the normal course of page rendering, it can be retrieved more quickly from the cache, reducing the overall page load time.<\/p>\r\n Preloading is especially beneficial for large or critical resources that can introduce latency if fetched only when they are explicitly needed. However, it should be used judiciously to avoid unnecessary network overhead. Over-preloading can lead to increased resource consumption and might not be suitable for all types of content.<\/p>\r\n<\/li>\r\n<\/ol>\r\n\r\n <\/p>\r\n<\/body><\/html>\n","protected":false},"excerpt":{"rendered":" Welcome to the W3 Total Cache Pro Preload Requests feature guide. This feature helps improve your website’s performance by adding browser “hint” link tags to the HTML head for dns-prefetch, preconnect, and preload. Below is a brief explanation of each, and at the end of this article is an in-depth explanation for those who want […]<\/p>\n","protected":false},"author":1307,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"bgseo_title":"","bgseo_description":"","bgseo_robots_index":"index","bgseo_robots_follow":"follow","footnotes":""},"categories":[747,692],"tags":[],"class_list":["post-108458","post","type-post","status-publish","format-standard","hentry","category-user-experience","category-w3-total-cache"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts\/108458","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/users\/1307"}],"replies":[{"embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/comments?post=108458"}],"version-history":[{"count":30,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts\/108458\/revisions"}],"predecessor-version":[{"id":126638,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts\/108458\/revisions\/126638"}],"wp:attachment":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/media?parent=108458"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/categories?post=108458"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/tags?post=108458"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Step 1: Enable Preload Requests<\/h2>\r\nTo enable preloading in W3 Total Cache:<\/p>\r\n\r\nLogin to WordPress<\/li>\r\nGo to Performance > General Settings<\/strong><\/li>\r\nClick on User Experience<\/strong> in the top sub-nav<\/li>\r\n

Step 2: Configure Preload Requests<\/h2>\r\nThe next step is to configure the feature by navigating to <\/span>Performance > User Experience<\/b>. There will be a new section titled <\/span>Preload Requests<\/b> towards the bottom of the page.<\/span><\/p>\r\n

Learn More about Preloading Requests<\/h2>\r\nWant to learn more about what these techniques are in-depth? We’ve got you covered!<\/p>\r\n

Step 2: Configure Preload Requests<\/h2>\r\n
The next step is to configure the feature by navigating to <\/span>Performance > User Experience<\/b>. There will be a new section titled <\/span>Preload Requests<\/b> towards the bottom of the page.<\/span><\/p>\r\n

Learn More about Preloading Requests<\/h2>\r\n
Want to learn more about what these techniques are in-depth? We’ve got you covered!<\/p>\r\n