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

Update stance on speculative preloading

Browse source
This commit is contained in:
Rohan Kumar 2024-04-06 20:10:04 -04:00
parent 35894e3df5
commit 98b4b86156
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
2 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
content/posts/website-best-practices.gmi
View file

@ -305,6 +305,9 @@ Unfortunately, pages with lazy loading don't finish loading off-screen images in
### Against speculative pre-loading
Update 2024-04-06: I've updated my stance on this. If you use the Speculation Rules API, preloading will obey user preferences in a standard cross-site way.
=> https://wicg.github.io/nav-speculation/speculation-rules.html
A common objection to my case against lazy-loading is that users may be more likely to click a link than scroll to the end, so pages should prioritize pre-loading the link. Pre-loading a page's essential resources is fine. Speculatively pre-loading content on separate pages isn't.
Many users with poor connections also have capped data, and would prefer that pages don't decide to predictively load many pages ahead-of-time for them. The overlap between these two groups grows especially pronounced as data cap overages trigger throttling:

2
content/posts/website-best-practices.md
View file

@ -326,6 +326,8 @@ Unfortunately, pages with lazy loading don't finish loading off-screen images in
### Against speculative pre-loading
<ins itemprop="correction" itemscope="" itemtype="https://schema.org/CorrectionComment">Update <time itemprop="datePublished">2024-04-06</time>: I've updated my stance on this. If you use the [Speculation Rules API](https://wicg.github.io/nav-speculation/speculation-rules.html), preloading will obey user preferences in a standard cross-site way.</ins>
A common objection to my case against lazy-loading is that users may be more likely to click a link than scroll to the end, so pages should prioritize pre-loading the link. Pre-loading a page's essential resources is fine. Speculatively pre-loading content on separate pages isn't.
Many users with poor connections also have capped data, and would prefer that pages don't decide to predictively load many pages ahead-of-time for them. The overlap between these two groups grows especially pronounced as data cap overages trigger throttling; this is enough to trigger [a seasonal pattern in Japan](https://web.archive.org/web/20220402004738/https://nitter.pussthecat.org/yoavweiss/status/1195036487538003968).