Amazon and others chanced on that laying aside 100 milliseconds of latency improves sales by 1%. But latency on the procure is difficult to overcome.
rapid.online page uses upright-in-time preloading — it preloads a online page appropriate sooner than a user clicks on it.
Earlier than a user clicks on a link, they waft their mouse over that link. When a user has hovered for 65 ms there is one likelihood out of two that they’ll click on on that link, so rapid.online page starts preloading at this moment, leaving on average over 300 ms for the procure page to preload.
One more possibility is to load the pages when the user starts pressing their mouse with out preloading. This makes for zero unused requests whereas soundless improving online page hundreds by 80 ms on average.
You could doubtless also moreover preload on waft or as soon as a link is considered and keep of living off the click on when the user starts pressing their mouse, making your pages the quickest on this planet.
A user starts touching their indicate sooner than releasing it, leaving on average 90 ms for the procure page to preload.
One more possibility is to preload hyperlinks as soon as they’re considered.
Are trying it out
You could doubtless also moreover click on the menu to trip it.
Dishonest the mind
The human mind perceives actions taking lower than 100 ms as rapid. As a result, rapid.online page makes your pages in actual fact feel rapid even on 3G (assuming your pages are mercurial to render).
Straightforward to your server and your user’s files opinion
Pages are preloaded simplest when there’s a real likelihood that a user will focus on over with them, and simplest the HTML is preloaded, being respectful of your customers’ and servers’ bandwidth and CPU.
It uses passive match listeners and requestIdleCallback so that your pages defend gentle. It respects files saver mode. It’s 1 kB and hundreds after every little thing else. And it’s free and beginning source (MIT license).