{"id":7717,"date":"2022-02-18T17:30:06","date_gmt":"2022-02-18T16:30:06","guid":{"rendered":"https:\/\/f.technology\/blog\/wordpress-en\/preloading-in-wp-rocket\/"},"modified":"2022-02-18T17:30:06","modified_gmt":"2022-02-18T16:30:06","slug":"preloading-in-wp-rocket","status":"publish","type":"post","link":"https:\/\/f.technology\/en\/blog\/performance-en\/preloading-in-wp-rocket\/","title":{"rendered":"Preloading in WP Rocket"},"content":{"rendered":"

The Preloading<\/strong> section of WP Rocket<\/strong><\/a>, as the name suggests, is about pre-generation<\/strong> of different entities.
\nIt is divided into 3 parts: <\/p>\n

\n
Preloading cache<\/em><\/strong>,<\/li>\n
Preloading link<\/em><\/strong>,<\/li>\n
Preloading DNS requests<\/em><\/strong>.<\/li>\n<\/ul>\n For complete documentation, please refer to the official page<\/a>.
\nAs always, we recommend that you inquire about the integration between WP Rockete<\/strong>your server<\/strong>!<\/em> For example, in the case of Kinsta<\/a>, even if WP Rocket is fully compatible, some features such as cache preloading or file minification (should the Kinsta server-side one also be enabled) are not recommended<\/a>. <\/p>\n
Cache preloading<\/h2>\n
Page<\/strong>cache preloading (cache preload<\/em>) involves the page<\/strong> cache <\/em><\/strong> being generated<\/strong> independently by WP Rocket, regardless of user interactions.
\nAs seen in the previous article<\/a>, this is arecommended and default setting<\/strong> of WP Rocket.
\nIf preloading is turned off, each page will require at least one visit to be cached<\/em>.
\nTherefore, the first user will always view it slower. $\"preloading$ If enabled without additional options, WP Rocket will generate the cache starting from the home page and continuing independently based on all detected links<\/em>.
\nBy activating the “Enable cache preloading based on sitemap”<\/strong> option, the sitemap<\/strong> is automatically detected and preloaded.
\nSometimes it is also possible to confirm the detected sitemap<\/em>.
\nThis is the case with Yoast SEO<\/strong>: $\"wp$ Cache preloading occurs globally: <\/p>\n
\n
When the cache<\/em> expires<\/strong>,<\/li>\n
With each save of<\/strong> WP Rocket settings<\/strong>,<\/li>\n
Upon clicking the appropriate“Preload cache<\/strong>” command,<\/li>\n
Uponactivation of the plugin<\/em><\/strong>,<\/li>\n
On clearing the cache<\/em><\/strong>.<\/li>\n
In additional cases determined by specific servers<\/em> or plugins<\/em> such as Varnish HTTP Purge<\/em>.<\/li>\n<\/ul>\n Individually, it occurs when publishing\/updating content<\/strong>.
\nIf mobile version cache<\/em> separation<\/strong> is enabled, the mobile version cache<\/strong> is also preloaded along with the desktop<\/em> part: $\"user$ If WebP compatibility<\/strong> is enabled, WP Rocket will preload that cache instead of the non-WebP cache for the files involved.
\nTo verify that the cache preloading is working properly<\/strong>, access via FTP to the \/wp-content\/cache\/wp-rocket\/name\/ folder.
\nInside will be all the cache files created.
\nBy clicking on “Preload cache,” the contents of the folder will be updated. $\"\"$ Through plugins such as WP-Cron Status Checker<\/a> or WP Crontrol<\/a>, it is also possible to check the scheduling of preload actions.
\nNot to be underestimated, the chesty site health panel viewable in Settings –> Site Health.<\/strong>
\nFrom here we can verify that planned events have not failed.
\nIf an error 28 related to cURLs appears, this normally indicates a slow response from the server.
\nIn such a case, the suggestion is to contact the service provider. <\/p>\n
More information about cache<\/em> preloading<\/h3>\n
Cache<\/em> preloading never consumes more than 90% of<\/strong> the available PHP memory.
\nCPU utilization problems should never occur.
\n Sitemap-based<\/em> preloading requires that on<\/strong> server<\/strong><\/em>SimpleXML PHP<\/a> extension is enabled.
\nThe default interval for crawling between URLs is 500ms.
\nIt is possible to change it using an extension.
\nIt is possible to schedule cache<\/em> preloading by creating an appropriate cron.<\/em> <\/p>\n
Preloading of links<\/h2>\n
Only on Chrome<\/strong> and Chromium<\/strong> browsers<\/em>! Link<\/em> preloading<\/strong> improves the perceived interaction time of the user browsing the site.
\nIf the user scrolls over a link<\/em> for more than 100 ms, the HTML content of the linked page will be preloaded in the background.
\nThe option does not result in improvements<\/strong> in PageSpeed scores, Pingdom, GT Metrix, etc.
\nThey are automatically excluded: <\/p>\n
\n
Miscellaneous administration URLs;<\/li>\n
URLs excluded from WP Rocket cache<\/em>;<\/li>\n
Images;<\/li>\n
Links<\/em> with search strings and anchors;<\/li>\n
External URLs.<\/li>\n<\/ul>\n It is also possible to manually exclude<\/strong> specific URLs, by function. Warning.
\nFiles (including .docx) are not excluded from link preloading. <\/strong> This can cause errors mainly due to the automatically queued “\/” slash.<\/em>
\nTo avoid this, rules can be created using the WP Rocket | Regex Exclusions<\/a> extension.<\/em><\/p>\n
Preloading DNS Requests<\/h2>\n
Preloading<\/strong>DNS<\/em> requests<\/strong>(DNS prefetch<\/em>) comes in particularly handy if there is third-party content on the page.
\nIt causes DNS resolution<\/strong> to occur before the user’s interaction<\/strong> with the external content.
\nTechnically, it is addedrel=\"dns-prefetch\"<\/code> to the header. \nFor example, CDN, Google fonts, Pixel, Analytics, Tag Manager are handled in this case: <\/p>\n
<link rel=\"dns-prefetch<\/span>\" href=\"https:\/\/cdn.domain.com<\/span>\">\n<link rel=\"dns-prefetch<\/span>\" href=\"https:\/\/fonts.gstatic.com<\/span>\">\n<link rel=\"dns-prefetch<\/span>\" href=\"https:\/\/connect.facebook.net<\/span>\">\n<link rel=\"dns-prefetch<\/span>\" href=\"https:\/\/www.google-analytics.com<\/span>\">\n<link rel=\"dns-prefetch<\/span>\" href=\"https:\/\/www.googletagservices.com<\/span>\"><\/pre>\n The improvement is not easily evaluated, but it is a recommended practice<\/strong>. GT Metrix<\/strong> may suggest reducing DNSlookups (Reduce DNS Lookups<\/em>). \nDNS preloading does not result in the elimination of the suggestion<\/strong>: it does not eliminate requests, but anticipates them. \nThe only permanent solution remains the removal of third-party content<\/strong>. <\/p>\n Preload fonts<\/em><\/h2>\n Preloading fonts<\/em> within the element<head><\/code>, these will be downloaded before being identified<\/strong> within the CSS. \nIf the fonts<\/em> are located on the domain or CDN<\/strong>, it is recommended to enable the option.<\/strong> \nYou cannot take advantage of the feature when they are located externally. If the “Remove Unused CSS” option is enabled within “File Optimization,” pre-loaded fonts will also be removed.<\/em><\/p>\n Which fonts<\/em> to preload?<\/h3>\nGoogle PageSpeed<\/strong> provides a “Preload Key Requests” entry. \nIt is useful to start the test by bypassing WP Rocket with parameter \/?nowprocket<\/strong>. \nAlso, the URL must match the one provided by PageSpeed. \n Only fonts<\/em> that slow down page loading or perceived performance<\/strong> should be preloaded. \nPreloading can be counterproductive if it involves too many fonts<\/em><\/strong>. Do not preload multiple formats! \nNormally .woff2<\/strong> is sufficient. <\/em><\/p>\n Notice of PageSpeed<\/h3>\nWarnings: Lighthouse was unable to automatically check the `font-display` value for the origin<\/p><\/blockquote>\n It is usually caused by preloading unused fonts. \nIn such cases Chrome also shows a similar warning. <\/p>\n Preloading of external fonts<\/h3>\n It is not possible to implement this with WP Rocket. \nHowever, an appropriate HTML line can be added in the <head><\/code> section. <\/p>\n <link rel=\"preload\" href=\"https:\/\/ESEMPIO.COM\/FONT.woff2\" as=\"font\" type=\"font\/woff2\" crossorigin><\/code><\/pre>\n The correct URL must be entered. \nThe type<\/em> attribute should identify the correct format. \nOnce the code is entered, clear the WP Rocket cache. <\/p>\n","protected":false},"excerpt":{"rendered":" The Preloading section of WP Rocket, as the name suggests, is about pre-generation of different entities. It is divided into 3 parts: Preloading cache, Preloading link, Preloading DNS requests. For complete documentation, please refer to the official page. As always, we recommend that you inquire about the integration between WP Rocketeyour server! For example, in […]<\/p>\n","protected":false},"author":2,"featured_media":3452,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[75],"tags":[],"class_list":["post-7717","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-performance-en"],"acf":[],"_links":{"self":[{"href":"https:\/\/f.technology\/en\/wp-json\/wp\/v2\/posts\/7717","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/f.technology\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/f.technology\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/f.technology\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/f.technology\/en\/wp-json\/wp\/v2\/comments?post=7717"}],"version-history":[{"count":0,"href":"https:\/\/f.technology\/en\/wp-json\/wp\/v2\/posts\/7717\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/f.technology\/en\/wp-json\/wp\/v2\/media\/3452"}],"wp:attachment":[{"href":"https:\/\/f.technology\/en\/wp-json\/wp\/v2\/media?parent=7717"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/f.technology\/en\/wp-json\/wp\/v2\/categories?post=7717"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/f.technology\/en\/wp-json\/wp\/v2\/tags?post=7717"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}