Hello Everyone, Today in this post I am going to tell About Advantages & Disadvantages of Using AMP Blogger - Do you want to implement Accelerated Mobile Pages (AMP) on Blogger? Or you want to know the serious advantages and disadvantages of making an AMP Blogger Template? If your answer is yes, then you have come to the right website. Before making your site ready for AMP, read why big companies haven't adopted AMP.
What are Mobile Accelerated Pages (AMP) ?
AMP HTML is an open source project by Google to provide mobile-optimized content that loads instantly anywhere. In short AMP makes your site load faster like a fast bullet on smartphones but at the expense of most of your ad revenue and third-party JavaScript. So, have you understood yet what is AMP? But AMP is platform independent, providing publishers to optimize content for mobile and make it accessible for all devices via a web browser. It has some advantages but some disadvantages, which are worth noting before you choose AMP.
Here are some AMP limitations :-
- Only allow asynchronous scripts
- Static size of all resources
- Don't let the extension mechanism block rendering
- Keep all third-party JavaScript off the critical path
- All CSS must be inlined and bound in size less than 50,000 bytes
- The font trigger must be efficient
- Minimize style recalculation
- Prioritize resource loading
Difference Between AMP and Responsive Template :-
Before converting your template to AMP, it should be made mobile responsive first by adding a CSS media query and some breakpoints.
AMP is basically a much simplified/optimized version of your responsive template with the addition of some custom HTML tags.
Advantages and Disadvantages of Using AMP :-
- Loading AMP Templates Faster AMP pages load much faster than responsive blogger templates.
- AMP Templates Increase Ranking AMP increased The Washington Post's SERP rankings and organic traffic by 23%.
- Your Blog page views will increase. Blog Pages will load instantly thus providing a better user experience as far as speed is concerned.
- AMP templates are best suited for news blogs.
Deficiency :-
- Bad AMP Affects Ad Earnings. You won't make as much money as you would with a full-fledged mobile website.
- Buddy Can't Use JavaScript at all! All interactive widgets and plugins that make your blog look cool are not allowed. you have to use the JavaScript library available on Google.
- Buddy Cannot Use Blogger Comment Form. However you can use Facebook/Disqus/Google+ comment plugins instead but since the official comment form by Blogger uses an uneditable iframe so it's not allowed.
- Buddy Can't Use Blogger Template Editor You can't customize your template in Template Editor. <b:skin> tags and <b:template-skin> tags are removed or commented out.
- All Images Posted Must Be Edited You need to edit the <img> tag of all images in your blog post one by one with supported tags amp <amp-img> . Which of course takes time on blogger if you have more than 100 posts.
- You can't use Widgets in the Sidebar AMP doesn't allow third party JavaScript. If you want to use a widget that runs on JavaScript then you can't use it. Some of the widgets available in the layout section that use text + images are only supported after their code has been edited in the template section to make them compatible.
- Buddy Can't Sell Items on your Blog. Add to Cart button not allowed.
- All Video and Audio embedded in Post Must be Edited You need to edit all your YouTube/Facebook/Vimeo videos, all your soundoud audio clips via different embed tags.
- AMP supports limited Ad Networks. BuySellAds does not currently support AMP. You will suffer a lot in BSA income if you use AMP. Currently only AdSense ads are properly supported.
- The XMLNS attribute should be removed. The xmlns attribute is added inside the opening <html> tag if your blog is providing important information to the web browser about the web technologies used by your blog. AMP asks you to remove all those attributes and add only the amp="amp"attribute. Your blog will not be validated by http://w3.org if the xmlns attribute specifying the xml namespace for the document does not exist.