The AMP project has a lot going for it, but it also has a lot going against it. In my opinion, the cons outweigh the pros.
The project has been in existence for more than a year now and it’s still not mature. It should have been relatively mature in the first three months, especially since it’s a Google project.
Here’s a quote from TechRadar:
Supposedly, forms now work with it. I couldn’t get a simple contact form to work and I’m no neophyte. A few days ago, I was preparing to get around forms and comments by using non-AMP pages. And then I decided not to.
As an AMP only website, I was either going to have to do a lot of work or do without the things I wanted to give my visitors.
AMP HTML is too restrictive. It’s unforgiving as well. If a page doesn’t validate, it doesn’t get indexed as an “AMP page”. I have better things to do with my time, so I opted to get rid of AMP completely.
Yes, it’s supposed to make the mobile web a lot faster and it does. It seems, though, that it’s designed for single article-type pages more than entire websites.
That’s what doesn’t make sense to me. Either support everything you can from the beginning or don’t bother. Partial support sucks to no end.
One other thing. If you rely on AdSense for income, you’ll shoot yourself in the foot if you use AMP ads. They load slower than non-AMP ads. Google claimed to be working on it back in October. I guess not.
So… if you want a fast website without any ads, forms or comments (or a decent search service), go for it. Otherwise, I can only recommend waiting at least another year.
Previous and Next Articles (if any):