Hopefully this one-sided, web damaging framework will die a death like IE finally did, with its awful standards.
Definitely. I can’t understand why the hell anyone would want to use it anyway. The experience is terrible.
Google AMP case study: leads dropped by 59%
11–20 of 163 posts
Re: Google AMP case study: leads dropped by 59%
#12Earlier quoted context omitted.
Definitely. I can’t understand why the hell anyone would want to use it anyway. The experience is terrible.
It's wonderful when browsing. Pages load in less than half a minute, unlike nearly the entire rest of the internet. Hacker News doesn't need it, but they're nearly unique in having written a good website.
Re: Google AMP case study: leads dropped by 59%
#13Front end engineers are not selected for their skills in understanding algorithms and data structures. It's quite easy to speed up a web site if you understand how CPU works on a low level and how Javascript is compiled to machine code, but it requires a lot of knowledge.
Very little knowledge is needed to know how to speed up a website (or keep it from becoming slow). Almost every front-ender I've met, including those who never got beyond inserting jQuery snippets, knows enough.
Re: Google AMP case study: leads dropped by 59%
#14Front end engineers are not selected for their skills in understanding algorithms and data structures. It's quite easy to speed up a web site if you understand how CPU works on a low level and how Javascript is compiled to machine code, but it requires a lot of knowledge.
Very little knowledge is needed to know how to speed up a website (or keep it from becoming slow). Almost every front-ender I've met, including those who never got beyond inserting jQuery snippets, knows enough.
Re: Google AMP case study: leads dropped by 59%
#15Re: Google AMP case study: leads dropped by 59%
#16Hopefully this one-sided, web damaging framework will die a death like IE finally did, with its awful standards.
Definitely. I can’t understand why the hell anyone would want to use it anyway. The experience is terrible.
Re: Google AMP case study: leads dropped by 59%
#17As a user I like AMP because it's guaranteed to be very fast. There, I said it.
Re: Google AMP case study: leads dropped by 59%
#18wait until they are kicked out from the google cache (see your trusted google search console, best the useable old one).
then remove the references to the AMP page from the non-AMP pages. then delete the AMPs.
usually takes 2 to 3 days for a few thousand pages.
Re: Google AMP case study: leads dropped by 59%
#19As a user I like AMP because it's guaranteed to be very fast. There, I said it.
Publishers certainly wouldn't give up the most important bits of their page (the top), and cede left/right swipe hijacking (on carousel loaded pages) if there weren't some perceived benefit.
Re: Google AMP case study: leads dropped by 59%
#20Earlier quoted context omitted.
Definitely. I can’t understand why the hell anyone would want to use it anyway. The experience is terrible.
Purely to keep the SEO positioning everyone enjoyed before it came into being.
They take it away from you and then you will bend over and kiss Matt's Butt.