IIRC back in the day, google used a similar trick, where it would preload the first few search results to make them load from cache in the 90% of the cases when a user clicked on them
Show HN: Make your site’s pages faster than instant in one minute
51–59 of 59 posts
Re: Show HN: Make your site’s pages faster than instant in one minute
#52>it triggers the page load when the user starts pressing their mouse This breaks the standard GUI interaction model. Buttons are typically triggered on mouse-up events, not mouse-down, and there's probably good reasons for that. Any client-side hacks that attempt to improve the perceived page speed are somehow bound to break something. If there really is a simple way, it's already been implemented at the browser leve…
Re: Show HN: Make your site’s pages faster than instant in one minute
#53Re: Show HN: Make your site’s pages faster than instant in one minute
#54Earlier quoted context omitted.
It's extremely common. It is unclear to me if the mousedown event just kicks off preloading of the page, or actually forces you to navigate to the page. If it's the latter, you are breaking decades of mouse ux changing a click from a mousedown followed by mouseup.
It's the latter - it's in use on all links on their sidebar.
[Edit: I was using a blocker that was blocking it. Now I've used it and can tell it's working, and I still don't notice any problems using it in Safari.]
Re: Show HN: Make your site’s pages faster than instant in one minute
#55Re: Show HN: Make your site’s pages faster than instant in one minute
#56Earlier quoted context omitted.
It's the latter - it's in use on all links on their sidebar.
Dragging sidebar links worked fine for me all but once in Safari. Not sure how to tell whether it's actually being used, but I don't notice any problems. [Edit: I was using a blocker that was blocking it. Now I've used it and can tell it's working, and I still don't notice any problems using it in Safari.]
> Safari 13.0 has support for but it’s disabled by default. Hopefully it will be enabled in September 2020 in Safari 14.0.
Try enabling that setting or using another browser (I used Firefox) to see the effect it has.