Gatsby's page-fetching is a feature I consider a double-edged sword (though I'll admit I also don't fully understand it 😅). On the one hand, I'm all for anything that decreases load time between pages on a site. On the other, pre-caching a bunch of content that the user may never need feels like an extremely wasteful practice. InstantPage takes a slightly different approach, instead triggering the page request when a link is hovered (or touched on mobile). In their estimation that can reduce latency by 100s of milliseconds, so we're not talking huge wins here, but a minor UX bump. Assuming the page weight added from the client-side JS doesn't offset it, of course...
- Source
- Link to Original 🔗
- Published
- Categories
- Frontend, JavaScript, User Experience
- Tags
- JavaScript, tool, preload, link, hover, UX, client-side
Explore Other Notes
⬅ Newer
Adding Lighthouse scores to my site's footer
Using a combination of Speedlify and Google Lighthouse tool, Zach is able to display web performance scores in his footer, bespoke for each page. He seems to be doing so client-side, though I don't …
Older ➡
Sneak peek at Sunlit 3.0
A new product aiming to be an "Instagram replacement" and photo-blogging tool from the creator of Micro.blog‽ Colour me intrigued! 🤔 Sunlit looks very nice, will be interested to see how it …
- <p>Gatsby's page-fetching is a feature I consider a double-edged sword (though I'll admit I also don't fully understand it 😅). On the one hand, I'm all for anything that decreases load time between …</p>
- Murray Champernowne
