4 ms·

"All AMP is, is a decided-upon set of restrictions for what you can do on a page". You say that like it's a bad thing! But that's the entire point. Without a c

"All AMP is, is a decided-upon set of restrictions for what you can do on a page". You say that like it's a bad thing! But that's the entire point. Without a clear set of rules, almost no one makes fast pages in real life. This is especially true when you are working in a company where a wide mix of people have competing objectives. The developers want a fast page, the designers want a pretty page, the PMs want conversion, the business folks want lots of ads, etc. It makes it nearly impossible to build something fast without clear rules. Take a random article on the TheVerge.com as an example. I'm sure they have fantastic web developers who want the site to load quickly and they definitely know how to build beautiful pages. But check out their normal responsive page you get if you visit their site directly on your phone: http://www.theverge.com/2016/3/15/11233030/jj-abrams-moon-shot-review-google-lunar-x-prize-documentary http://www.theverge.com/2016/3/15/11233030/jj-abrams-moon-sh... Using Chrome's "Regular 2G" throttling, that page takes 19.82s to hit DOMContentLoaded and an insane 1.3 minutes to hit Load. The total mobile page weighs 2.5mb! Now check the AMP version of that same page. You can find it by looking for the 'link rel="amphtml"' tag in the header of the page: http://www.theverge.com/platform/amp/2016/3/15/11233030/jj-abrams-moon-shot-review-google-lunar-x-prize-documentary http://www.theverge.com/platform/amp/2016/3/15/11233030/jj-a... Using the same Chrome throttling settings, it hits DOMContentLoaded in 802ms and Load in 33.33s. And even then, almost all of that time is spent loading fonts and (in this particular article, very poorly optimized) images. To a mobile user, that is a way better experience - the difference between bouncing and reading. And the only difference was having "a decided-upon set of restrictions".

kup0 11y ago
As a desktop user, that is a way better experience too, but because AMP seems to be mostly mobile-focused, we desktop users get the "normal" experience typically. If the site was built from the beginning with performance in mind, we'd all benefit, no matter what we're using to view the site. I get that it has more to do with business side of things vs. the development side of things. Lots of hands in the pot at these companies and webdevs are only one part of it.

kup0 11y ago

As a desktop user, that is a way better experience too, but because AMP seems to be mostly mobile-focused, we desktop users get the "normal" experience typically. If the site was built from the beginning with performance in mind, we'd all benefit, no matter what we're using to view the site. I get that it has more to do with business side of things vs. the development side of things. Lots of hands in the pot at these companies and webdevs are only one part of it.