Re:The meaning of AMP
by jordanlev on Monday October 30, 2017 @11:03AM
(#15585453)
If Google just flat-out said they would penalize sites in rankings for poor performance, then management would very much prioritize it.
Same thing happened with responsive design a year or two ago and now https this year -- my clients never cared about doing either of these when presented with the choice (since it would cost more money), but the second they received and email from Google about it affecting their search rankings (or showing the site as "insecure" in chrome, as per the recent push for https), they were asking us to do this for them.
[ Parent
| on HN ]
Re:The meaning of AMP
by seanwilson on Monday October 30, 2017 @11:09AM
(#15585506)
I'm curious about this as well. How easy would it be to game performance measurements? For example, when you can lazily load content it becomes much more difficult to measure. The advantage of the AMP restrictions for them is that they know for sure certain performance metrics will be met but this is much more difficult for arbitrary webpages.
Run a WebPageTest on an AMP link and tell me it fits within the 1 second promise AMP keeps making.
Without prefetch, on a lot of the pages I've cross-checked manually, it doesn't. So there's already gaming from the other side of the aisle in a sense.