How to fight back against Google AMP as a web user and a web developer

Post by reaperducer » Thu, Dec 05, 2019, 7:47 PM UTC

mrtksn wrote: post #131

buboard wrote: post #115

Earlier quoted context omitted.

from USERS PERSPECTIVE, amp is meh. yes it's faster, does it really matter if you re getting an article in 1 second when you -obviously- plan to spend 2 minutes reading it? i dont know anyone who thinks so, perhaps your USERS do > A strealined conent delivery platform prioritizing UX that the publishers failed to create what you re implying is, Google failed to improve their algorithms to bypass obvious SEOs, so they…

Actually, it's a pretty well-known fact that users leave websites if they are not loading fast. People don't go with reading plans to websites, the titles are optimized to bring you there and you don't know what's in the article. More often than not, the text on the website is not what the title made you believe it is. You can't plan ahead, you want to quickly find out what is this all about. The article themselves a…

Post by [deleted] » Thu, Dec 05, 2019, 7:52 PM UTC

joshuamorton wrote: post #306

wizzwizz4 wrote: post #278

Earlier quoted context omitted.

Source for your second paragraph: https://news.ycombinator.com/item?id=16730905 That's out of date now, though; despite still being part of the required boilerplate CSS for AMP pages, I can't find that delay in any of the https://amp.dev/ pages (the ampbyexample.com replacement demo site). This is really shady.

It's a little more complex than that: If you disable all js, there is no delay. If you specifically block amp js, there is a delay. There could certainly be a shady reason for this, but the justification makes sense: one of the goals of AMP is to have, basically, a single, correct, initial paint. That's why images are statically sized and amp sticks placeholders there until the real images load. The js delay exists t…

Post by privateSFacct » Thu, Dec 05, 2019, 7:53 PM UTC

soyyo wrote: post #30

I 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,…

Post by stephenr » Thu, Dec 05, 2019, 7:54 PM UTC

joshuamorton wrote: post #306

wizzwizz4 wrote: post #278

Earlier quoted context omitted.

Source for your second paragraph: https://news.ycombinator.com/item?id=16730905 That's out of date now, though; despite still being part of the required boilerplate CSS for AMP pages, I can't find that delay in any of the https://amp.dev/ pages (the ampbyexample.com replacement demo site). This is really shady.

It's a little more complex than that: If you disable all js, there is no delay. If you specifically block amp js, there is a delay. There could certainly be a shady reason for this, but the justification makes sense: one of the goals of AMP is to have, basically, a single, correct, initial paint. That's why images are statically sized and amp sticks placeholders there until the real images load. The js delay exists t…

Post by RonanTheGrey » Thu, Dec 05, 2019, 7:56 PM UTC

joshuamorton wrote: post #307

stephenr wrote: post #194

Earlier quoted context omitted.

Without their monopoly search position no one would be forced to adopt amp and further strengthen said monopoly position.

How does amp strengthen a monopoly position?