Weston Ruter

Google

Hendrik Luehrsen

WP Munich

Quicklink for WordPress attempts to make navigation to subsequent pages load faster. Embedded with the plugin is a javascript library, which detects links in the viewport, waits until the browser is idle and prefetches the URLs for these links. The library also tries to detect, if the user is on a slow connection or on a data plan.
This plugin builds heavily on the amazing work done by <a href="https://github.com/GoogleChromeLabs/quicklink" rel="nofollow ugc">Google Chrome Labs</a>.
More information about <a href="https://getquick.link" rel="nofollow ugc">Quicklink on the official Website</a>.
<h4>How it works</h4>
<ul>
<li>Detects links within the viewport (using <a href="https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API" rel="nofollow ugc">Intersection Observer</a>)</li>
<li>Waits until the browser is idle (using <a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/requestIdleCallback" rel="nofollow ugc">requestIdleCallback</a>)</li>
<li>Checks if the user isn’t on a slow connection (using <code>navigator.connection.effectiveType</code>) or has data-saver enabled (using <code>navigator.connection.saveData</code>)</li>
<li>Prefetches URLs to the links (using <a href="https://www.w3.org/TR/resource-hints/#prefetch" rel="nofollow ugc"><code><link rel=prefetch></code></a> or XHR). Provides some control over the request priority (can switch to <code>fetch()</code> if supported).</li>
</ul>
If you are a developer, we encourage you to follow along or <a href="https://github.com/luehrsenheinrich/wp-quicklink" rel="nofollow ugc">contribute</a> to the development of this plugin <a href="https://github.com/luehrsenheinrich/wp-quicklink" rel="nofollow ugc">on GitHub</a>.

Quicklink for WordPress

Thanks for publishing this. Works really well. Would be nice to see option to loading Quicklink from a CDN.

Great plugin

⚡️ Faster subsequent page-loads by prefetching in-viewport links during idle time.

andrewmoof

DNS resolution time can lead to a significant amount of user perceived latency. The time that DNS resolution takes is highly variable. Latency delays range from around 1ms (locally cached results) to commonly reported times of several seconds.
DNS prefetching is an attempt to resolve domain names before a user tries to follow a link. This is done using the computer’s normal DNS resolution mechanism. Once a domain name has been resolved, if the user does navigate to that domain, there will be no effective delay due to DNS resolution time. When we encounter hyperlinks in pages, we extract the domain name from each one and resolving each domain to an IP address. All this work is done in parallel with the user’s reading of the page, using minimal CPU and network resources. When a user clicks on any of these pre-resolved names, they will on average save about 200 milliseconds in their navigation (assuming the user hadn’t already visited the domain recently). More importantly than the average savings, users won’t tend to experience the “worst case” delays for DNS resolution, which are regularly over 1 second.

Simple DNS Prefetch

Adds (or removes) DNS prefetching meta tags to your site and speeds up your page load speed.

Quicklink for WordPress vs Simple DNS Prefetch