3 ms·
I think it's largely a user experience thing. Because the "portal" has already been loaded and rendered, you don't need to add the delay of loading the new page
by neilalexander 7y ago
I think it's largely a user experience thing. Because the "portal" has already been loaded and rendered, you don't need to add the delay of loading the new page at the point of navigation.
- rst 7y agoBut if performance boosts from preloading are all you want, you could just add a 'preload' attribute to the usual <a> tag. The stated rationale of supporting spiffy transitions seems a bit more sensible, though, given how many hooks this has into browser UI, I'd be interested in seeing the limits on what, say, a malicious ad network could do with it. (Besides, if a page has several dozen links, exactly how many of them can you afford to preload before that activity starts bogging things down? The ZDnet article talks about this behavior replacing all links, which doesn't make a whole lot of sense to me...)