Google AMP case study: leads dropped by 59%
1–10 of 163 posts
Re: Google AMP case study: leads dropped by 59%
#2Hopefully this one-sided, web damaging framework will die a death like IE finally did, with its awful standards.
Re: Google AMP case study: leads dropped by 59%
#3Hopefully 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%
#4Hopefully 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'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%
#5Front 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.
Re: Google AMP case study: leads dropped by 59%
#6Front 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.
Err you don't need to know how Js is compiled.
You need to understand how html css and js work and not cut and paste megabytes of cruft.
Re: Google AMP case study: leads dropped by 59%
#7Earlier 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.
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.
Re: Google AMP case study: leads dropped by 59%
#8Hopefully 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.
Purely to keep the SEO positioning everyone enjoyed before it came into being.
Re: Google AMP case study: leads dropped by 59%
#9Front 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%
#10Front 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.
Haha what? You absolutely do not need to understand how a CPU works to make a fast site. 90% of the job is getting rid of shitty third party ad and tracking code, something most front engineers don't control. Beyond that most is just sensible practices.
In depth knowledge of the DOM would serve you a lot better than knowing about CPUs. What triggers a repaint, how you can avoid it, and so on.