5 ms·
I recently setup a simple Jekyll blog that conforms to amp[1]. I used Amplify[2], a repo that was on Show HN[3] a few months ago. There are still a few issues
by ryanmaynard 10y ago
I recently setup a simple Jekyll blog that conforms to amp[1]. I used Amplify[2], a repo that was on Show HN[3] a few months ago.
There are still a few issues with their docs at this point, but its basically just inline css/js.
[1] http://ryanmaynard.co/ http://ryanmaynard.co/
[2] https://github.com/ageitgey/amplify https://github.com/ageitgey/amplify
[3] https://news.ycombinator.com/item?id=11287540 https://news.ycombinator.com/item?id=11287540
- rikkus 10y agoI loaded this on a 4g connection and it took 14 seconds from click to progress bar disappearing. AMP talks about sub second load times on mobile. What might be in the way of that being realised?
- 6DM 10y agoI just opened the site in chrome and did a hard refresh on the Good 2G setting of the chrome tools, only took 3 seconds. Maybe you're cell phone dropped the connection or something.
- kuschku 10y agoIt takes about 12 seconds on a 64k connection (the default if you used up your data cap). In contrast, HN loads in half a second on that connection. Obvious result: AMP is bloated.
- ryanmaynard 10y agoI don't think its AMP. I think its my fault. Out of the box, you can't place analytics on the page. There is a special tag for any analytics. It seems I'm getting an error, and so Google has not cached it. Thank you for telling me. I need to debug that. That being said, I just received 239 ms with Pingdom.[1] [1] http://i.imgur.com/qeEyKqL.png http://i.imgur.com/qeEyKqL.png
- kuschku 10y agoWell, cache doesn’t matter when the page is almost a quarter megabyte, but you have only a 64kib connection. The majority of time spent will be on getting the 170kiB AMP lib.
- ryanmaynard 10y agoThank you for this. Google attempts to validate the AMP rules. If not validated, they won't cache it. Error on my part (misuse of their amp-analytics tag).
- mark_l_watson 10y agoYour site did load very quickly for me. Basically, Google is also your CDN with AMP?
- ryanmaynard 10y agoYes. There are limits to what you can place in an AMP site. Basically, its all static assets, so the entire AMP version is supposed to be cached by Google.
- gorhill 10y ago> the entire AMP version is supposed to be cached by Google Does this means there is no way to opt out of connecting to a Google-controlled server in order for any AMP-based page to display properly?
- ryanmaynard 10y agoIts the Google Amp Cache[1] > What gets cached? > If an AMP page is valid and is requested (so the Google AMP Cache is aware of it), it will get cached. Any resources in AMP pages, including AMP images, also get cached. > Can I stop content from being cached? > No. By using the AMP format, content producers are making the content in AMP files available to be cached by third parties. For example, Google products use the Google AMP Cache to serve AMP content as fast as possible. > Can the cache be crawled? > No. The Google AMP Cache is roboted to crawlers. We recommend that search engines process cache links according to the guidelines for crawling Google AMP Cache URLs. For more information, see robots.txt." [1] https://developers.google.com/amp/cache/faq https://developers.google.com/amp/cache/faq
- deleted 10y ago[deleted]