How to fight back against Google AMP as a web user and a web developer
401–410 of 570 posts
Re: How to fight back against Google AMP as a web user and a web developer
#402Re: How to fight back against Google AMP as a web user and a web developer
#403Earlier quoted context omitted.
Of course AMP has other motives than simply making the web faster for mobile, but it also does make the web faster for mobile. I guarantee the AMP version of that paper's mobile website provided a significantly better user experience than the normal version. That is why AMP has been successful, and it's why I will continue to click on AMP links whenever available. Is giving Google that much control ideal? Of course n…
> it also does make the web faster this is true > That is why AMP has been successful This is not. If google removes ranking incentive, people will forget about AMP the next day
>This is not. If google removes ranking incentive, people will forget about AMP the next day
Google giving ranking incentive to sites that are faster seems like the exact sort of thing they should be doing.
Re: How to fight back against Google AMP as a web user and a web developer
#404I know that can be overridden in Chrome's accessibility settings, but it's a shitty practice that something like AMP shouldn't be promoting.
Re: How to fight back against Google AMP as a web user and a web developer
#405Earlier quoted context omitted.
> they will look how to load it with ads and tracking, which very conveniently is supported on amp, just as they do in their regular sites. Yes OP did.
He put words in OPs mouth about sync loaded JS.
Whether or not that claim is true is beyond both my expertise and my interest.
Re: How to fight back against Google AMP as a web user and a web developer
#406Probably highly unpopular opinion, but as a user I've never had anything but positive experiences with AMP-enabled sites. They load massively faster than normal sites, especially on poor mobile connections where main sites sometimes hang indefinitely trying to load javascript, ads, etc. While content publishers are continuing to overload their sites with further trackers, ads, javascript, remotely loading assets whic…
> They load massively faster than normal sites, especially on poor mobile connections where main sites sometimes hang indefinitely trying to load javascript, ads, etc. Have you tried the normal mobile websites with an adblocker?
Re: How to fight back against Google AMP as a web user and a web developer
#407It's funny that, if it was a net neutrality issue, e.g. Comcast pushing a new video format and prioritizing video for their own streaming service, the internet would be a warzone by now. But we all love google. And google used to be all fuzzy and unevil. But now they 're evil
Re: How to fight back against Google AMP as a web user and a web developer
#408Re: How to fight back against Google AMP as a web user and a web developer
#409Earlier quoted context omitted.
> it also does make the web faster this is true > That is why AMP has been successful This is not. If google removes ranking incentive, people will forget about AMP the next day
>> That is why AMP has been successful >This is not. If google removes ranking incentive, people will forget about AMP the next day Google giving ranking incentive to sites that are faster seems like the exact sort of thing they should be doing.
Yes. It should give ranking incentive based on actual speed, not AMP support.
Re: How to fight back against Google AMP as a web user and a web developer
#410I worked on amp for a leading newspaper, and everyone who says that amp is about "making the web faster on mobile" is either very naive or doing marketing for google. For publishers, amp is about trying to top the results on google search and capture traffic, it's their only motivation to publish their content using amp, and the only metric they look in order to evaluate the results. Once they have their amp content,…
Of course AMP has other motives than simply making the web faster for mobile, but it also does make the web faster for mobile. I guarantee the AMP version of that paper's mobile website provided a significantly better user experience than the normal version. That is why AMP has been successful, and it's why I will continue to click on AMP links whenever available. Is giving Google that much control ideal? Of course n…