5 ms·
It's true that Google doesn't explicitly boost AMP pages. But it does boost all of the attributes that AMP enforces on a page (reduced page size, loading speed,
by have_faith 9y ago
It's true that Google doesn't explicitly boost AMP pages. But it does boost all of the attributes that AMP enforces on a page (reduced page size, loading speed, etc). So it's an implicit signal boost rather than explicit. You may think that that's fine and there's nothing wrong with that, but no doubt Google see this as a way keeping users within the Google system as much as possible while they browse.
I'm personally on the fence regarding the whole situation. On one hand, I like less bloat, on the other I don't want a 3rd party involved more than is required in delivering a news article to me.
- ucaetano 9y ago"It's true that Google doesn't explicitly boost AMP pages. But it does boost all of the attributes that AMP enforces on a page (reduced page size, loading speed, etc)." So Google is guilty of making things that users want? "Google see this as a way keeping users within the Google system as much as possible while they browse." Well, isn't giving users what they want a way to keep them inside your system? I don't see the point in your comment, are you saying that Google should not be optimizing for what users want?
- coldtea 9y ago>So Google is guilty of making things that users want? Well, I'm a user and I don't want this. I want Google to not invent a new format for web pages, and instead help make the actual web faster.
- ucaetano 9y ago"Well, I'm a user and I don't want this." You (and myself, and anyone reading HN) are not the target user for this, nor are you representative of the typical internet user. Remember, India has more internet users than the US has people. And you can just not click on AMP sites if you don't want them.
- pmlnr 9y agoIndian users are the worst example for this, given the regular 2G connections. Hundreds of KB of JS is not helping this, especially not on low-end mobile devices.
- monokh 9y agoIt is helping this when you consider all the JS is cached because they've visited an AMP page before.
- pmlnr 9y agoNo, they are not, that's a misconception. Many low end devices simply lack the capacity to efficiently cache this many things, so they are going to re-download it once it's purged. For the downvoters: https://danluu.com/web-bloat/ https://danluu.com/web-bloat/
- endorphone 9y agoMany low end devices simply lack the capacity to efficiently cache this many things Very low-end devices still have an outrageous amount of memory and storage compared to the scopes we're talking about. In the actual anecdotes of people in India expressing their good user experience with AMP, actual results seem to differ. But as a North American with a GS8 and a very fast LTE connection, I still love getting AMP results. Just confining to best practices is alone worth it.
- monokh 9y agoOh I see. So low end devices in india which are predominantly android smart phones do not have the capacity to cache 500kb of frequently used JS? Reducing the overall page size of a given page doesn't help Optimizing rendering for content first and images loaded as required doesn't help Serving pages from a super fast global CDN doesn't help And prefetching content behind the scenes also doesn't help I think you should take these to Google because it seems like they've totally goofed this AMP thing!