Thursday 14 September 2017

AMP (Accelerated Mobile Pages) pros and cons details



AMP Pros

#1 It speeds up website load time
This one is obvious. With no useless elements to slow them down, AMPs are lean, slick, and fast. Users enjoy pages that don’t make them wait, so AMPs basically guarantee that your site brings in more visitors.

#2 It increases mobile ranking
Although AMP is not a ranking factor by itself, it has a positive influence on mobile ranking due to its faster load time. Potentially, if Google starts prioritizing AMPs, it will have even more of an effect on SERPs.

#3 It improves server performance
If your site generates tons of traffic from mobile, AMP will reduce the load on your servers and improve their performance. But this has a huge downside (see con #3).


AMP Cons

#1 Ad revenue is reduced

Though Accelerated Mobile Pages Project supports ads, the potential to bring in revenue is severely limited. And it is not a piece of cake to implement ads on AMP-run pages as well.

#2 Analytics are a bit stripped

AMP supports Google Analytics but requires a different tag, which needs to be implemented on all AMP pages. Obviously, it takes a lot of time to place this tag and be able to collect and analyze data.


#3 Amazing speed is achieved, thanks to cache
Google doesn’t offer any specific technology to make your pages super fast. What it actually does is saves cached versions of AMP-tagged pages and, whenever visitors access them, simply serves them up from the cache. You figure out the rest.

AMP allows your site to load faster and guarantees better UX, but its disadvantages raise several serious questions:

Are you ready to sacrifice at least a part of your ad revenue?
Can you live without all the charts and tables in Google Analytics?
And, most importantly: Are you so sure that you want to depend on Google through cache?
These are no easy questions, but you should definitely consider detailed answers to them. But before you do it, let’s compare AMP and responsive design.




Reference Link: https://www.searchenginejournal.com/do-i-need-amp/181292/

1 comment: