Live data from Hacker News

Google AMP case study: leads dropped by 59%

kinsta.com

161–163 of 163 posts

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

#161

So another problem with AMP delivered via Google is it tends to utterly booger your analytics... first pageview (via the Google cache) is viewed as a different domain than your site. This can play havoc with optimization efforts. In terms of performance... this is a situation where the AVERAGE AMP site is much faster than the AVERAGE site not using AMP... but that's a rigged game given the volume of non-optimized Wor…

You can’t beat its load times. Google pre-renders the web page before the user clicks, which isn’t safe to do with pages created by your own elbow grease.

You can actually.... with very, very lean design....

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

#162

Earlier quoted context omitted.

You can’t beat its load times. Google pre-renders the web page before the user clicks, which isn’t safe to do with pages created by your own elbow grease.

You can actually.... with very, very lean design....

Nope. You can’t best the speed of light.

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

#163
post #147

Earlier quoted context omitted.

You can’t beat its load times. Google pre-renders the web page before the user clicks, which isn’t safe to do with pages created by your own elbow grease.

Load times ain’t everything, and it’s a terrible pitch for something that breaks basic rules of browsing.

This post was specifically saying you could beat AMP’s load times. That isn’t possible.
Post reply on HN