Performance of application is one of the important business KPI (Key Performance Indicators) which heavily contributes to the success of business.There are ways to improve the performance of the website like performing optimization, resources upgrade and etc.
Apart from traditional approaches to improve the performance, there is a lot of buzz and talk going on for AMP (Accelerated Mobile Pages- powered by Google ) these days.
As per wikipedia– “The Accelerated Mobile Pages Project (AMP) is an open-source website publishing technology designed to improve the performance of web content and advertisements. The AMP Project led by Google is a competitor to Facebook’s Instant Articles, and includes several other large search, social and web publishing platforms around the world.”
As part of this blog post– I would like to discuss if AMP can be leveraged for Sitecore applications, advantages and disadvantages and what are some key points to be considered before we plan to integrate AMP with Sitecore.
Advantages of AMP:
- Speed and Performance-AMP provides a great user experience across many platforms
- AMP complaint content always gets displayed first in search(organic search).
- Increased mobile device site loading.
- Boost in Ranking.
- Reducing the page bounce rate and better conversions.
- No custom JS/Plugins allowed, which can affect some of the execution efforts like Pagination, listing, search,etc..
- All CSS in AMP Page should not be more than 50 KB.
- Multiple Versions required (AMP and No-AMP).
- Increased development time- Increases developer time in 2 times(AMP and Non AMP layouts).
- Strict validation rules
- Inline CSS styles.
- Impact on Analytics and Sitecore Analytics?
- How it affects the website functionality, like carousels, products and other features?
- Impact on Personalization in Sitecore?
- Do we need separate layout or can be managed with same default layout.
Though we know AMP is a performance booster, but it’s worth to check above points and do a analysis to understand the Integration.
Apart from just AMPiying your website another important factor is to analyze and understand what pages should be migrated to AMP like:
- Home page
- Landing pages and other top performing pages which contribute to the overall business.
Also, when when AMP should be served?- when user is trying to search contents from Google- via organic search(this is default behavior) or when user hit your page directly is a point of discussion and depends on business requirements, Let’s discuss above points as part of my next post on AMP.
Here are some case studies are available and can be used as reference to understand it better.
I am very excited about AMP and it’s integration with Sitecore, i am pretty sure you guys are too?. I hope this give you a starting point and makes you think about AMP and how it can be leveraged with Sitecore.
Happy learning 🙂