Live data from Hacker News

Google AMP case study: leads dropped by 59%

kinsta.com

131–140 of 163 posts

Re: Google AMP case study: leads dropped by 59%

#131

Earlier quoted context omitted.

Google AMP on iOS is also much worse than Safari + adBlocker. AMP also leaves out relevant content.

My beef is that it used to jack the scrolling. I don't know if it still does.

This has been partially fixed. AMP no longer scrolls at a different rate than other websites, but it still doesn't collapse the URL bar when scrolling.

Re: Google AMP case study: leads dropped by 59%

#132
post #122
post #79

Earlier quoted context omitted.

A huge pet peeve of mine was that I'd google for something I once saw on Reddit, or maybe I just wanted to see a certain discussion. Google would identify the correct post, but then I'd either get it in AMP or new-redesign format, both of which present a terrible loss in readability (for the most part). With AMP in particular, there was no obvious link back towards Reddit itself. And with the redesign, the actual dis…

Heh I uninstalled reddit is fun a while ago to limit my procrastination. Worked well. But I reinstalled after about a week because I search for things on Reddit via Google regularly. Reddit has some disturbing dark patterns going on. You can't view a page on their site without being nudged to use their app. And you're asked every single page view. Like take a damn hint please. I'd be ok with the asking but they use d…

It was these dark patterns that prompted me to really step back and re-evaluate what I wanted to get out of Reddit.

I set a hard timer on the app and focused on surfing Hacker News instead (since I wanted to keep abreast of tech news). I still browse /r/politics for popcorn purposes, but otherwise no other subreddits. To my surprise today I realised I hadn't opened Reddit and didn't even miss it at all.

Re: Google AMP case study: leads dropped by 59%

#133

Hopefully this one-sided, web damaging framework will die a death like IE finally did, with its awful standards.

There are two sides with AMP:

- A set of enforced good practices that make sites faster and generally more user friendly

- A way for Google to get more control by introducing a semi-proprietary framework

The disturbing thing is that webmasters usually criticize the first aspect. Basically they want to bloat their sites and AMP doesn't let them do it. They don't really care about the second part. They are already using Google analytics, Google ads and optimize for Google search anyways. It means that the ones who can do something want AMP to die for all the wrong reasons.

For that reason, I think that AMP is good (or less bad). Even better would be to do what AMP does but without the Google framework. That would make it even faster than AMP because there won't be any Google bloat.

Re: Google AMP case study: leads dropped by 59%

#134
post #33
post #11

Earlier quoted context omitted.

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.

> something they could do as a reward for all pages that have a reduced page weight

This would leak information to sites that came up in your search results but you didn't visit. Webpackages should make it be possible to safely prerender sites without AMP though: https://wicg.github.io/webpackage/draft-yasskin-webpackage-u...

(Disclosure: I work at Google, on making ads AMP so they don't get to run arbitrary JS anymore)

Re: Google AMP case study: leads dropped by 59%

#135
post #85
post #79

Earlier quoted context omitted.

A huge pet peeve of mine was that I'd google for something I once saw on Reddit, or maybe I just wanted to see a certain discussion. Google would identify the correct post, but then I'd either get it in AMP or new-redesign format, both of which present a terrible loss in readability (for the most part). With AMP in particular, there was no obvious link back towards Reddit itself. And with the redesign, the actual dis…

I think the trick is to go to google.com with Desktop Mode (iOS: share page from Mobile Safari then scroll bottom icons left, I think). That: (A) gets Google to return desktop links (rather than cruddy mobile links) (B) gets the site to show the desktop version rather than the cruddy mobile site. It is more obvious how to do it on Android (google.com in Desktop Mode), but I do it on the iPad at work when needed.

(iOS, tap and hold on reload button to request Desktop Site)

Re: Google AMP case study: leads dropped by 59%

#136

Earlier quoted context omitted.

If one thinks all they need to do is remove javascript to speed things up substantially, then they fit into my category of people who only know jQuery snippets only think they know enough. There are a multitude of issues that can be tweaked to speed things up more so than javascript elimination. You can switch to HTTP/2, implement server push, image compression, header compression, compressing HTML/CSS/Javascript dow…

And none of the things you mention will amount to anything if the site is still pulling dozens of trackers and ad scripts. The average JS dev (like average anything dev) may not write performant code, but the functional parts of the website are not where the main problem lies.

That is a business and design problem not a programming problem. And if one thinks the functional part of a web site cannot be tuned to substantially increase the speed of a web site then one is part of that jQuery plugin crowd who does not know or understand the pipeline from browser to network to server and back.

Re: Google AMP case study: leads dropped by 59%

#137

Earlier quoted context omitted.

AMP is a fork of HTML that pressures limited developer resources to maintain a version for Google's visitors while only being fast because of arbitrary framework limitations. You can get a far better outcome by having search results consider site speed as a factor in rankings, which would make all publishers improve their sites overnight. The reason Google doesn't do this is because they also run the biggest ad netwo…

https://searchengineland.com/google-speed-update-page-speed-...

The open secret in adtech and media is that this isn't used to any real effect, if at all. Google's own sites fail these performance reports.

Re: Google AMP case study: leads dropped by 59%

#138
post #122

Earlier quoted context omitted.

Heh I uninstalled reddit is fun a while ago to limit my procrastination. Worked well. But I reinstalled after about a week because I search for things on Reddit via Google regularly. Reddit has some disturbing dark patterns going on. You can't view a page on their site without being nudged to use their app. And you're asked every single page view. Like take a damn hint please. I'd be ok with the asking but they use d…

It was these dark patterns that prompted me to really step back and re-evaluate what I wanted to get out of Reddit. I set a hard timer on the app and focused on surfing Hacker News instead (since I wanted to keep abreast of tech news). I still browse /r/politics for popcorn purposes, but otherwise no other subreddits. To my surprise today I realised I hadn't opened Reddit and didn't even miss it at all.

Thanks. You have just convinced me to never browse reddit again, and I've been on it since 2007.

Re: Google AMP case study: leads dropped by 59%

#139
post #44

I think that AMP made Google's search results feel like they were essentially just Google's own pages. Because that's exactly what the user sees in his address bar, when he visits an accelerated mobile page : google.com/amp/ . And that encourages him to hit "Back" as soon as he is done with it, instead of checking out the newly discovered website. Because he never felt like he had discovered anything. He never felt t…

Users don't see google.com, they see shittypopups.com delivered by Google

Re: Google AMP case study: leads dropped by 59%

#140

Earlier quoted context omitted.

> No reason to have any proprietary formats like AMP or others. Unless you want pages to load instantly, which is what AMP and its non-web competitors provide.

HackerNews loads instantly, as do many other sites. HTML works fine. The problem is the stuff on the page, like ads delivered by Google AdX. Removing or optimizing those will make any page faster. No AMP necessary. Slow sites are not a technical problem, they are a business and marketing problem.

> HackerNews loads instantly, as do many other sites. HTML works fine.

They load quickly, not instantly. That's the fundamental mistake you have in understanding why people prefer AMP, Facebook instant articles, and Apple News.

Post reply on HN