Over-prefetching section for home page #148
Conversation
| {% markdownConvert %} | ||
| ```js | ||
| quicklink.listen({ | ||
| el: document.getElementById('carousel') |
There was a problem hiding this comment.
Wdyt about us using an example like document.getElementById('article') or document.getElementById('content')?
There was a problem hiding this comment.
Changed it to 'content', thank you!
|
I think these changes strike the right balance of conveying how our latest features for limiting and controlling throttling help avoid the over-prefetching problem well. I like that we started off with sharing how to limit prefetching to specific elements. Something I may try doing if there's time is creating a nice SVG that shows how this works. But overall I think this will help. Going ahead and landing the change 👍 |
|
Great! Thanks @addyosmani. I tested both option parameters on the demo site (limit and throttling), and could visualize clearly in the network tab how in one case requests are limited to a certain number and, in the other, how they are sent sequentially instead of simultaneously. With that said, if at some point think we would need a demo to complement this explanation, it can be easily done as well. 👍 |
[docs] Over-prefetching section for home page (GoogleChromeLabs#148)
[docs] Over-prefetching section for home page (GoogleChromeLabs#148) * Home section around over-prefetching. * Over-prefetching partial. * Changing carousel by content. Quicklink Chrome extension section for home page.
Section covering techniques to avoid over-prefetching with Quicklink.