fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-10 00:12:09 +00:00
Code Issues Projects Releases Wiki Activity

New note: speculative preloading

Browse source
This commit is contained in:
Rohan Kumar 2023-05-05 00:00:04 -07:00
parent 59ea763cee
commit ecaf0a7aa5
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 14 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
content/notes/speculative-preloading.md Normal file
View file

@ -0,0 +1,14 @@
---
title: "Approaches to speculative preloading"
date: 2023-05-05T00:00:04-07:00
replyURI: "https://social.treehouse.systems/@felipe/110185148285133305"
replyTitle: "there must be a whole research area for “speculative human interaction”"
replyType: "SocialMediaPosting"
replyAuthor: "Felipe Tavares"
replyAuthorURI: "https://felipetavares.com/"
---
instant.page (mentioned in another response) is popular, but it's not the only game in town. Google Chrome Labs made an alternative called [quicklink](https://github.com/GoogleChromeLabs/quicklink) which also attempts to optimize CPU time by preloading in-viewport pages during idle time. instant.page generally expects you to be using a mouse; results on touchscreens are pretty minimal and probably not worth the extra JS.
[Speculation rules](https://wicg.github.io/nav-speculation/speculation-rules.html) are being standardized for a JavaScript-free alternative. Figuring out which pages to preload will be the hard part. I like this because it'll be easy to globally disable the behavior if I need to save data (or if it helps reduce fingerprinting).
If your backend isn't too slow and your payload is small, simpler optimizations are probably better.