You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the only enhancement that is made on the final bundle is instant.page. But there's no reason more couldn't be done, like Clayton suggests: "offline support, code splitting, smart preloading." These would probably all be options on the developer side, and include other things like: optimize images, append .html to relative links (for a static site), minify bundle, etc.
The text was updated successfully, but these errors were encountered:
I really like the idea of Instant.pages, but I think all stuff like this should be optional. I want to decide on my own what extra features are included on my website. Personally, I would use flying pages + turbolinks for preloading. Because since it is a static website I don't really care about server load. https://wpspeedmatters.com/quicklink-vs-instant-page-vs-flying-pages/
Source
At the moment, the only enhancement that is made on the final bundle is instant.page. But there's no reason more couldn't be done, like Clayton suggests: "offline support, code splitting, smart preloading." These would probably all be options on the developer side, and include other things like: optimize images, append
.html
to relative links (for a static site), minify bundle, etc.The text was updated successfully, but these errors were encountered: