‘Why I Decided To Disable AMP On My Site’

Web developer Alex Kras on Monday listed a number of reasons why he dislikes Google’s AMP project, and why he pulled support for it on his website. From his post: Back in the day we used to have WAP pages — specific web pages that were presented only to mobile devices. Opting into AMP, for publishers, is kind of like going back to those days. Instead of using responsive design (making sure that one version of the site works well on all devices) publishers are forced to maintain two versions of each page — their regular version for larger devices and mobile phones that don’t use Google and the AMP version. The benefit of AMP is that it imposes tough restrictions on content, making it load fast. The issue with this approach is that AMP becomes a subset of the original content. For example, user comments are often removed. I also find the way images load in AMP to be buggy. AMP tries to load an image only when it becomes visible to the user, rendering a white square instead of the image. In my experience I’ve seen it fail fairly regularly, leaving the article with an empty white square instead of the image. […] It’s up to publishers to decide if they want to add AMP support on their site. Users, however, don’t have an option to turn AMP off. It would be nice if Google provided a user level setting to turn results rendered as AMP off. Unfortunately, even if they were to add this option, it wouldn’t help much when Twitter of Facebook would decide to server AMP. Further reading: Kill Google AMP before it KILLS the web – The Register, The Problem With Google AMP, 2 Billion Pages On Web Now Use Google’s AMP, Pages Now Load Twice As Fast. John Gruber on open web: Fuck Facebook.


Share on Google+

Read more of this story at Slashdot.

Clip to Evernote

Leave a Reply

Your email address will not be published. Required fields are marked *