2 ms·
Comparing cold loading doesn't seem appropriate - one of the points of AMP is requiring you to hotlink to their specific resources, so as to benefit fully from
by icebraining 10y ago
Comparing cold loading doesn't seem appropriate - one of the points of AMP is requiring you to hotlink to their specific resources, so as to benefit fully from cache, as more website get AMP'ed.
- velcro 10y agoSure it does - even if you totally ignore the fact that the same AMP page is loading quite a bit of JS, that its almost double the size and double the number of requests - you're assuming that all requests are cached and thats not correct. For the Youtube AMP component alone some of those requests are "no-cache" cookie/ads/other types + if nothing else, its also loading the video cover image i.e. effectively starting the video iframe in the background. Which is as mentioned not ideal since the video is in a hidden inline popup thats used only by 40% of the visitors. Our main page loads and executes all of this on click/user-interaction first so ideally I'd like to be able to set how this behaves in an AMP component too. If that loads from cache afterwards - even better. But it shouldn't upfront and I can't influence it easily. BTW fun fact - all popups/galleries/sliders/menus/animations on the page are done without JavaScript - none whatsoever (excluding pre-loading large images). They use clever new CSS techniques instead. Just for fun - we tried to go completely JS-free, but Youtube/iframe was the only problem because it was preloading everything on start (and we tried various hacks from various nested display:none; stuff to switching iframes for objects, etc.). Plus/minus Google Analytics of course. So its quite a contrast - on one hand going JS-free, but then on another loading an insane amount of JS for the AMPed version :)