Neither PWA nor AMP are needed to make a website load fast • Hacker News Board

Re: Neither PWA nor AMP are needed to make a website load fast

#221

Post by lern_too_spel » Sat, Dec 08, 2018, 3:15 PM UTC

dmitriid wrote: post #220

lern_too_spel wrote: post #219

Earlier quoted context omitted.

You're the one who doesn't know the problem it solves, as many times as I've explained it. It loads pages instantly, not merely quickly. That's the whole point of the technology and the whole reason so many link aggregators use it. I showed you that your first link didn't understand this either. Your last link isn't even about the same technology. I didn't bother clicking the other because that would surely also be a…

> I didn't bother clicking the other because that would surely also be a waste of time. Yup. That sums up your attitude perfectly.

Fine. I clicked link two. That author made the same mistake as link 1, the author of this article, and you. Do you think that repeating something that is wrong will make it right?

Re: Neither PWA nor AMP are needed to make a website load fast

#222

Post by dmitriid » Sun, Dec 09, 2018, 6:30 PM UTC

lern_too_spel wrote: post #221

dmitriid wrote: post #220

Earlier quoted context omitted.

> I didn't bother clicking the other because that would surely also be a waste of time. Yup. That sums up your attitude perfectly.

Fine. I clicked link two. That author made the same mistake as link 1, the author of this article, and you. Do you think that repeating something that is wrong will make it right?

The author doesn't make "the same mistake", it just shows you reality, not faith.

Re: Neither PWA nor AMP are needed to make a website load fast

#223

Post by lern_too_spel » Mon, Dec 10, 2018, 6:43 PM UTC

dmitriid wrote: post #222

lern_too_spel wrote: post #221

Earlier quoted context omitted.

Fine. I clicked link two. That author made the same mistake as link 1, the author of this article, and you. Do you think that repeating something that is wrong will make it right?

The author doesn't make "the same mistake", it just shows you reality, not faith.

"Reality" is to ignore what AMP was designed to do and suggest alternatives that don't solve the same problem? I don't follow.

Re: Neither PWA nor AMP are needed to make a website load fast

#224

Post by privateSFacct » Tue, Dec 11, 2018, 2:36 PM UTC

dmitriid wrote: post #174

privateSFacct wrote: post #156

Earlier quoted context omitted.

Do people not use the web, particularly media sites. PLEASE go browse a bunch of non-AMP media sites with adblocker off. 500kb is TINY by comparison to what is out there outside of AMP.

People do. And people who understand what the web and AMP are know that AMP isn't the solution. By the time you've loaded CNN's AMP page, you'll have loaded at least 4 MB: ~2 MB of AMP prefetching done on Google's search results page and another ~2.2 MB on the AMP page itself. If Google adhered to its own page performance standards, as outlined here: https://developers.google.com/web/fundamentals/performance/w... , C…

Isn't CNN something like 7-8MB without AMP?

Re: Neither PWA nor AMP are needed to make a website load fast

#225

Post by collinmanderson » Tue, Dec 11, 2018, 2:51 PM UTC

seanwilson wrote: post #66

Solar19 wrote: post #13

The author says you can do these things anyway without AMP, but what he doesn't get is that web developers were not doing them. It took the nudge of AMP to get decent performance on the mobile web. He also failed to mention a key AMP rule: all CSS is in the head, a max of 50 KB. There is no external CSS at all. That's crucial. It reverses a persistent anti-pattern in web development that calls for a bunch of separate…

> all CSS is in the head, a max of 50 KB. There is no external CSS at all. That's crucial. It reverses a persistent anti-pattern in web development that calls for a bunch of separate files for CSS and JS. This means CSS and JS cannot be cached between page loads however so you're requesting the same data every time while navigating pages. It's a tradeoff against faster page loading. I'm surprised there isn't a better…

One trick I'm interested in trying: use external CSS if the referer is coming from the same site, otherwise include CSS inline. That way people who only view one page (a large percentage of visitors) get it inline, and people who view multiple pages get it cached.