Google AMP Cache, AMP Lite, and the Need for Speed
developers.googleblog.com
Google AMP Cache, AMP Lite, and the Need for Speed
1–10 of 247 posts
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#2I've been critical of AMP in some previous posts, but an AMP like infrastructure has the impressive advantage of trying out such optimizations and solutions, without a large affect on the users.
I'd still like to push for an open, standards based approach to tackling the issue of content delivery under resource constraints.
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#3I've been critical of AMP in some previous posts, but an AMP like infrastructure has the impressive advantage of trying out such optimizations and solutions, without a large affect on the users. I'd still like to push for an open, standards based approach to tackling the issue of content delivery under resource constraints.
Cloudflare just launched its own AMP viewer and cache: https://blog.cloudflare.com/accelerated-mobile/
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#4"We remove image data that is invisible to users, such as thumbnail and geolocation metadata. For JPEG images, we also reduce quality and color samples if they are higher than necessary."
Great. Except that that information might be deliberately a part of the image.
These things should be opt-in.
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#5[deleted]
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#6I've been critical of AMP in some previous posts, but an AMP like infrastructure has the impressive advantage of trying out such optimizations and solutions, without a large affect on the users. I'd still like to push for an open, standards based approach to tackling the issue of content delivery under resource constraints.
Cloudflare just launched its own AMP viewer and cache: https://blog.cloudflare.com/accelerated-mobile/
It didn't launch its own AMP. They are now supporting Google's AMP by replacing all links on CloudFlare powered webpage into AMP ones with that little thunderbolt.
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#7[deleted]
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#8Earlier quoted context omitted.
Cloudflare just launched its own AMP viewer and cache: https://blog.cloudflare.com/accelerated-mobile/
It didn't launch its own AMP. They are now supporting Google's AMP by replacing all links on CloudFlare powered webpage into AMP ones with that little thunderbolt.
It's the same standard but it's Cloudflare's own viewer, cache and the AMP URLs are managed by Cloudflare and not Google.
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#9"We remove image data that is invisible to users, such as thumbnail and geolocation metadata. For JPEG images, we also reduce quality and color samples if they are higher than necessary." Great. Except that that information might be deliberately a part of the image. These things should be opt-in.
I would love it if all AMP sites were opt-in. I understand the target audience and I agree that making the web a faster place is important. However, there are tradeoffs that come with AMP, and I personally have an amazingly fast and unlimited LTE connection. I don't need AMP, so all I get is the downsides with none of the positives.
The mobile Internet has become a far more frustrating place for me since Google introduced AMP. I just want to be able to turn it off.
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#10There is zero reason for AMP to be hijacking URLs or embedding any additional elements into a page that are detectable by the average user.
Beyond that, universal opt-out should be possible and stats on the percentage of users opting out should be published real-time.
As such, until this is addressed, I am against AMP.