You are here: Home » NewsFeeds » I decided to disable AMP on my site

I decided to disable AMP on my site

I have a long history with Google’s Accelerated Mobile Pages (AMP) project, but yesterday I drew the final straw.
I was on Twitter (in Safari on iPhone 6) and I noticed that somebody linked to my site using an AMP link. I replied with a real link, but when I clicked on it, I was redirected back to the AMP version of my page.

Thanks for sharing here is non amp link so all images load: https://t.co/6drRK5Cugz
— Alex Kras (@akras14) June 23, 2017

I copied the link generated by Twitter and noticed that it looked as follows:
https://t.co/6drRK5Cugz?amp=1
Note the amp=1 in the path. When I hit the link, it responded with the following HTML page:

                    https://www.alexkras.com/simple-guide-to-finding-a-javascript-memory-leak-in-node-js/amp/window.opener = null;location    .replace(`https://www.alexkras.com/        simple-guide-to-finding-a-javascript-memory-leak-in-node-js        /amp/`)

The sole purpose of this page is to redirect the reader to the AMP version of the link.
My Issues with AMP As a Publisher
When AMP first came out, I was optimistic. AMP’s aim is to make the web


 

Original article