What exactly are "leads" in this context?
Google AMP case study: leads dropped by 59%
31–40 of 163 posts
Re: Google AMP case study: leads dropped by 59%
#32Earlier quoted context omitted.
I abhor it on mobile. I can't navigate away from it easily, it's hard to copy paste annurl to share with others, etc. I wish Chrome had the option to disable it, but of course they don't.
> I can't navigate away from it easily eh? You can't hit 'back'?
They might also mean "go to the non-AMP version", which is my main issue with AMP.
I'd like to get the non-AMP page to e.g. see user comments (if any) which are often omitted from the AMP version, or for posting the non-AMP URL to friends or social media.
Sometimes there is an easy way to go to non-AMP page, depending on how you got there, but most of the time for me there is not. For example, this article just appeared on my Google feed on my phone, with no way to open the non-AMP version: https://www.vice.com/amp/en_uk/article/wda7jm/where-does-he-...
My preferred option would be to have AMP permanently disabled on my phone.
Re: Google AMP case study: leads dropped by 59%
#33Earlier quoted context omitted.
Definitely. I can’t understand why the hell anyone would want to use it anyway. The experience is terrible.
It isn't though, really. Page load really is nearly instantaneous. I'm no fan of AMP, but I see the reasons why users like it.
You're right about that, but AMP'ed pages not coming from Google's cache are already really fast. Actually they're only preloading those pages while you're on the results page, which is something they could do as a reward for all pages that have a reduced page weight.
Re: Google AMP case study: leads dropped by 59%
#34Hopefully 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.
It only takes a couple business to start using it and always winding up at the top of search before everyone else feels they have to like it or not.
Re: Google AMP case study: leads dropped by 59%
#35A company trying to hijack the web is not a good idea.
Re: Google AMP case study: leads dropped by 59%
#36As a user I like AMP because it's guaranteed to be very fast. There, I said it.
As user I dislike AMP because it adds a JavaScript requirement to read articles that don't have any JavaScript. There, I said it.
Re: Google AMP case study: leads dropped by 59%
#37Front 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.
The obsession with data structures and algos is getting out of control, cargo culting this idea around is going to lead to requiring an L5 to change a button color.
Re: Google AMP case study: leads dropped by 59%
#38> Could we have done more conversion rate optimization to our AMP install? Probably yes. There are ways to add CTAs, newsletter signups, etc
If I'm reading this correctly they switched from regular pages with CTAs to AMP pages without CTAs. Seemingly this test was designed to fail.
Re: Google AMP case study: leads dropped by 59%
#39Earlier quoted context omitted.
Well sure, Google isn't dumb. Adding in enough benefits (speed, carousel placement) to your Trojan horse ensures there are plausible reasons to bring it into the fort. 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.
"Perceived" benefit is the key. It used to be the "World Wide Web" but now it is the "Google Platform" and we just live in it. After Google established that useful web search was possible the realized that the #1 competitor for their ads was organic rankings, and if you could really get a #1 ranking by investing in the best content then why would you spend money on ads? So since then it is has been about deliberately…
Last time I checked the url bar still works
Re: Google AMP case study: leads dropped by 59%
#40As a user I like AMP because it's guaranteed to be very fast. There, I said it.
no, you can't assert how fast the cache gets updated
it becomes indeterminate to the user, and when the harvester decides it