Gijo Varghese

<p>Flying Pages preload pages before the user click on it, making them load instantly</p>
<h3>How it Works?</h3>
<p>Flying Pages injects a tiny JavaScript code (1KB gzipped), waits until the browser becomes idle. Then it detects pages in the viewport and on mouse hover and preloads them.</p>
<p>Flying Pages is intelligent to make sure preloading doesn’t crash your server or make it slow.</p>
<ul>
<li>
<p><strong>Preload pages in the viewport</strong> – Detect links within the viewport (current viewing area) using ‘Intersection Observer’ and tells the browser to preload them using ‘prefetch’, switch to xhr if not available (similar to <a href="https://github.com/GoogleChromeLabs/quicklink" rel="nofollow ugc">Quicklink</a>).</p>
</li>
<li>
<p><strong>Preload pages on mouse hover</strong> – On hovering links, if it’s not preloaded yet using above ‘viewport’, then Flying Pages will prefetch them instantly (similar to <a href="https://instant.page/" rel="nofollow ugc">Instant.page</a>).</p>
</li>
<li>
<p><strong>Limits the number of preloads per second</strong> – If your page has too many links, prefetching all at the same time will cause the server to crash or slow down the website to visitors. Flying Pages limits the number of preloads per second (3 req/sec by default) using an in-built queue. For example, if you’ve 10 links in the viewport, preloading all these are span into 4 seconds.</p>
</li>
<li>
<p><strong>Stops preloading if the server is busy</strong> – In case the server starts to respond slowly or return errors, preloading will be stopped to reduce the server load.</p>
</li>
<li>
<p><strong>Understands user’s connection and preferences</strong> – Checks if the user is on a slow connection like 2G or has enabled data-saver. Flying Pages won’t preload anything in this case.</p>
</li>
</ul>
<h3>Support</h3>
<ul>
<li><a href="https://wordpress.org/support/plugin/flying-pages/" rel="ugc">Official Support Forum</a></li>
<li><a href="https://www.facebook.com/groups/wpspeedmatters" rel="nofollow ugc">Facebook Group</a></li>
</ul>
<h3>Our premium products</h3>
<ul>
<li><a href="https://flyingpress.com" rel="nofollow ugc">FlyingPress</a></li>
<li><a href="https://flyingcdn.com" rel="nofollow ugc">FlyingCDN</a></li>
</ul>
<h3>Our free plugins</h3>
<ul>
<li><a href="https://wordpress.org/plugins/flying-pages/" rel="ugc">Flying Pages</a></li>
<li><a href="https://wordpress.org/plugins/nazy-load/" rel="ugc">Flying Images</a></li>
<li><a href="https://wordpress.org/plugins/flying-scripts/" rel="ugc">Flying Scripts</a></li>
<li><a href="https://wordpress.org/plugins/flying-analytics/" rel="ugc">Flying Analytics</a></li>
<li><a href="https://wordpress.org/plugins/flying-fonts/" rel="ugc">Flying Fonts</a></li>
</ul>


Flying Pages: Preload Pages for Faster Navigation & Improved User Experience

Preload pages intelligently to boost site speed and enhance user experience by loading pages before users click, ensuring instant page transitions.

Dana Ross

<p>HTTP/2 is the new generation of the venerable HTTP protocol that powers the web. Among its most powerful features is <em>server push</em>, a way for web servers to send resources to the browser before it even realizes it needs them. This avoids the usual HTTP request/response cycle which happened for every script or stylesheet on a page.</p>
<p>This plugin enables WordPress to send a <code>Link:<...> rel="prefetch"</code> header for every enqueued script and style as WordPress outputs them into the page source. Unfortunately, it can’t help plugins and themes that output their scripts directly into the page itself, but these will continue to work as they always have.</p>
<p>Requires a web server that supports HTTP/2.</p>
<h3>WordPress 4.6 and above</h3>
<p>WordPress 4.6 introduced <a href="https://make.wordpress.org/core/2016/07/06/resource-hints-in-4-6/" rel="nofollow ugc">native support for resource hints</a>.<br />
By default, this plugin defers to WordPress 4.6 and theme/plugin developers to responsibly prefetch the right assets. Sites running<br />
on older versions of WordPress will continue to get the previous behavior where all JavaScript and stylesheets had resource hints<br />
printed for them.</p>
<p>I’ve added a filter To restore the old behavior (hint everything) on WordPress 4.6 and above. To use it, add this line to<br />
your theme’s functions.php file or a custom plugin:</p>
<pre><code>`add_filter('http2_render_resource_hints', '__return_true');```
</code></pre>


HTTP/2 Server Push

This plugin helped speed up my website by 33%!

Works as advertised

This plugin does just what it says it'll do, HTTP/2 pushes everything!  

That generally will speed things up unless you have a ridiculous number of assets.  

While it now respects resource hinting for themes and plugins that provide that info, I do wish it had a UI for older themes/plugins to control what assets were going to be pushed instead of pushing them all. This plugin is so great without that though it still gets 5 stars

Speeds things up

Works perfectly in conjunction with Cloudflare to deliver excellent performance

Works perfectly

Enables HTTP/2 server push for local JavaScript and CSS resources.

Flying Pages: Preload Pages for Faster Navigation & Improved User Experience vs HTTP/2 Server Push