Flying Pages Plugin
Load inner pages instantly, intelligently!
Flying Pages preload pages before the user click on it, making them load instantly
How it Works?
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.
Flying Pages is intelligent to make sure preloading doesn’t crash your server or make it slow.
Preload pages in the viewport – 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 Quicklink).
Preload pages on mouse hover – On hovering links, if it’s not preloaded yet using above ‘viewport’, then Flying Pages will prefetch them instantly (similar to Instant.page).
Limits the number of preloads per second – 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.
Stops preloading if the server is busy – In case the server starts to respond slowly or return errors, preloading will be stopped to reduce the server load.
Understands user’s connection and preferences – 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.
Support
Our premium products
Our free plugins
Installation
From within WordPress
- Visit ‘Plugins > Add New’
- Search for ‘Flying Pages’
- Activate Flying Pages for WordPress from your Plugins page.
- Visit ‘Settings -> Flying Pages’ to configure
Manually
- Upload the
flying-pagesfolder to the/wp-content/plugins/directory - Activate the Flying Pages plugin through the ‘Plugins’ menu in WordPress
- Visit ‘Settings -> Flying Pages’ to configure
Screenshots
Flying Pages Settings
FAQ
Flying Pages starts preloading when all other resources have completed downloading and browser has become idle. It will not affect the TTFB or First Contentful Paint or Time to Interactive. If you’re worried about the fully loaded time in GTmetrix, set the “Delay to start preloading” to a higher number in settings or set it to preload only on mouse hover.
See the video and you’ll find ‘prefetch cache’ (test it from an incognito window if you’ve enabled ‘Disable for logged in admins’)
Flying Pages preload links after the website is loaded and only improves the speed on clicking links. It doesn’t help you to speed up the initial load.
Every time a page/link is preloaded, it executes some PHP code and MySQL queries which is resource-intensive. So it’s highly recommended to use a cache plugin like FlyingPress.
Flying Pages only downloads the HTML content. It doesn’t execute any code inside it. So it will not affect Google Analytics or similar scripts.
It’s mostly videos and images that consume 80% of the bandwidth. Flying Pages only preloads HTML pages (which is usually <30KB) and doesn’t download any resources inside it (like images, css, js). Installing Flying Pages won’t increase your bandwidth usage not even by 5%.
In short, yes. But you can configure Flying Pages to limit the number of preloads per second or preload only on mouse hover which reduces the server load. Also, make sure to use a good cache plugin like FlyingPress. This will reduce server load dramatically.
Please create a support request in the official support forum. You can also get help from WP Speed Matters’ Facebook group.
Changelog
2.4.6
- Updated FAQ
2.4.5
- Fix: Missing Compatibility error
2.4.4
- Updated shortcuts link
2.4.3
- Updated “Optimize More” tab
2.4.2
- [UPDATE] Added ‘/checkout’ and ‘.webp” to ignore keywords
- [UPDATE] Minor update in JS file
- [FIX] Cross-Site Scripting in admin settings form
2.4.1
- [BUGFIX] Warnings and errors in Compatibility tab
2.4.0
- [NEW] Compatibility tab
2.3.0
- [BUGFIX] Stopped preloading when ignore list is empty
- [NEW] FAQ
- [NEW] Optimize more
2.2.2
- Bug fix for Fast Velocity Minify plugin
2.2.1
- Addtional options to mouse hover delay (0ms) and max rps (2s)
- Disable for logged in admins by default
2.2.0
- Moved option’s config object to window
- Separate option for ‘preload only on mouse hover’
- Start flyingPages() without waiting for DOMContentLoaded
- Improved babel setup
- Removed arrow functions for IE compatibility
2.1.2
- Removed XMLHttpRequest and improved minification of JS file (reduce size by ~300bytes)
- Added option ‘2 secs’ to delay to start preloading
2.1.1
- Changing JavaScript scope to prevent conflicts with other plugins using same variables
2.1.0
- Option to disable preloading when logged in as administrator
2.0.9
- Disable on Internet Explorer
- Renamed observer object to prevent conflicts with other plugins
2.0.8
- Ignore query strings by default
2.0.7
- Allow 1 second in delay
2.0.6
- Better compatibility for WooCommerce
- Prefetching on mobile using ‘touchstart’
2.0.5
- Bug fix – Start queue only after calling main function, causing errors in browser console
2.0.4
- Bug fix – Issues with Swift Performance cache plugin when ‘Merge Scripts’ is enabled
2.0.3
- Bug fix – Prevent max rps from resetting to default value on plugin update
2.0.2
- Support WordPress 4.5+
- Copy fixes
2.0.1
- Bug fix – Set default config on plugin update/activation
2.0.0
MAJOR UPDATE!
* Configure ignore keywords
* Configure delay for prefetching from viewport
* Configure to prefetch on mouse hover only
* Configure maximum requests per second
* Configure mouse hover delay
1.0.5
- Bug fix – Prevent wp-admin links from preloading
1.0.4
- Bug fix for Safari/iOS Safari
1.0.3
- Prevent logout links from preloading
1.0.2
- Prevent external links from preloading on hover
1.0.1
- Support for Microsoft Edge browser
- Prevents current page from preloading
1.0.0
- Initial release