I love that this solution specifically addresses challenges other options struggle with (QuickLink, Instant.page, etc.).
It's worth calling out, though, that preloading is not the same as prefetching. A true preload would fully render the page in a background tab, and can only handle one page at a time. Prefetching simply fetches the document, but doesn't parse any of its contents, including any CSS or JS called by that fetched page. Therefore, it's much less resource-intensive than preloading. They both serve important performance-related purposes, but are still very different. I wrote about this in more depth here:
I love that this solution specifically addresses challenges other options struggle with (QuickLink, Instant.page, etc.).
It's worth calling out, though, that preloading is not the same as prefetching. A true preload would fully render the page in a background tab, and can only handle one page at a time. Prefetching simply fetches the document, but doesn't parse any of its contents, including any CSS or JS called by that fetched page. Therefore, it's much less resource-intensive than preloading. They both serve important performance-related purposes, but are still very different. I wrote about this in more depth here:
macarthur.me/posts/best-ish-practi...
Yes, Flying Pages use
prefetch. Theprerenderwill consume too much bandwidth and cause issues in reporting tools like Google Analytics