3 ms·
I 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
by rikkus 10y ago
I 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).