Select Page

Category: amp

Weekly Platform News: Feature Policy, Signed Exchanges, iOS browsers

👋 Hey folks! This is the first edition of a new weekly update we’ll be posting that covers timely news at the intersection of development standards and the tools that make them available on the web. We often talk about the pace of change in our industry. It’s fast and touches everything from the HTML, CSS and JavaScript we write to the landscape of browsers that renders them. Please help us welcome Šime Vidas, who will be keeping us all on the up and up with curated updates from his own blog of regular development updates, Feature Policy...

Read More

AMP News

AMP is controversial, to say the least. Dave and I did a show on it about a year ago that to me felt fairly balanced in addressing some of the issues. Let’s cover some recent news and responses. One thing that isn’t usually controversial: it’s fast. AMP pages are damn performant. Even that, though, is contentious. Ferdy Christant notes: Technically correct AMP pages will perform very similar to any non-horrible web page. The difference between AMP performing instantly and getting numbers ranging from 2–8s as seen above have to be explained. Part of that answer you can probably guess: the cache is simply very fast. It’s hard to compete with a Google-class CDN. You don’t need AMP to have a fast website. FYI @CityLab article pages load faster than @nytimes AMP pages. Just to show you do not need AMP to have fast loading pages #webperf — Michael Donohoe (@donohoe) February 23, 2018 The most controversial bit is that carrot offered for using AMP: the search results news carousel. The carousel is extremely prominent in Google search results, and AMP is a one-way ticket to get in. You could make a site faster than AMP, but that doesn’t meet the criteria for entry. Tim Kadlec: there has been no indication of any attempt to address the first issue, that of incentivization and premium placement. In fact, not only...

Read More