▲ | jameslk 5 days ago | |||||||
If server resources and scalability are a concern, speculative fetching will add more load to those resources, which may or may not be used. Same deal on the end user’s device. That’s the trade off. Also, this is basically a Blink-only feature so far The article provides a script that tries to replicate pre-rendering that speculation rules do for Safari and Firefox, but this is only pre-fetching. It doesn’t do the full pre-render. Rendering is often half the battle when it comes to web performance Another limitation is that if the page is at all dynamic, such as a shopping cart, speculation rules will have the same struggles as caching does: you may serve a stale response | ||||||||
▲ | pyman 5 days ago | parent | next [-] | |||||||
I've seen some sites, like Amazon, calculate the probability of a user clicking a link and preload the page. This is called predictive preloading (similar to speculative fetching). It means they load or prepare certain pages or assets before you actually click, based on what you're most likely to do next. What I like about this is that it's not a guess like the browser does, it's based on probability and real user behaviour. The downside is the implementation cost. Just wondering if this is something you do too. | ||||||||
| ||||||||
▲ | duxup 5 days ago | parent | prev [-] | |||||||
Definitely a balancing act where you consider how much work you might trigger. But I can think of a few places I would use this for quality of life type enhancements that are for specific clients and etc. |