predictive-fetching
Improve performance by predictively fetching pages a user is likely to need
by addyosmani
Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
42
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 1 discussion · Last activity 8y ago
See all on GitHub →
Speculative prefetching (after page load) Scrolling links into the viewport (Gatsby) On user-interaction (e.g hovering over links) Prefetching during idle time
Recent fixes
Hi Addy, And thanks for pushing the web forward as always! We as web developers started to focus on code-splitting (e.g. via Webpack) and you've already wrote about this powerful feature multiple articles. Prefetching next assets by using tiny neural network implementation would learn which asset you will likely grep (page -> js assets to be fetched pair). Notice also that many tend to even embed css-in-js that will take the benefit from this approach also. This thing is more related to dynamically fetching assets chunks more than fetching the data itself, which will save the latency time + parse + execution.
Structured data for AI agents
Repository: addyosmani/predictive-fetching. Description: Improve performance by predictively fetching pages a user is likely to need Stars: 239, Forks: 13. License: Apache-2.0. Open PRs: 0, open issues: 1. Last activity: 8y ago. Community health: 42%. Top contributors: addyosmani, aamirmukaram.