Accelerated Mobile Pages is an Open Source Initiative to overcome the slow and frustrating experience of web pages and to provide fast mobile experience. Google together with other publishers and technology companies found this solution – AMP Project to bring the whole internet to your mobile really fast – be it images or videos. AMP is a fantastic approach to make the mobile web faster.
How does Accelerated Mobile Pages work?
AMP basically has three components
1. AMP HTML
These are a subset of HTML designed to create “reading” contents than interactive contents. This strips out most of the elements that make the app pages load slowly in mobile devices.
2. AMP JS
3. AMP CDN (Content Delivery Network)
Cache and optimize AMP-enabled pages for better performance.
Pros and Cons of AMP
Pros of AMP
- Instant speed
- Increased performance and reliability
- Increased customer visits
- Excellent support for ads
- Improved ranking
Cons of AMP
- Rewrite your template to accommodate the restrictions (like, CSS must be inline and less than 50 KB).
- A custom amp-imp element must be used for images and width and height must be included explicitly.
- Custom tag amp-video must be used to embed videos via HTML 5. Amp-YouTube must be used to embed YouTube videos.
Is using Accelerated Mobile Pages good or bad?
Performance is crucial for a website to be successful. If the web pages cannot load fast, the user will simply leave your website and try somewhere else.
Instead of using AMP to shorten your piece of code, focus on finding slow areas that affect your app performance and think of ways to fine-tune and optimize your code. You won’t end up displaying the stripped-down version of your code and can utilize the power of your website to its fullest. In other words, AMP is not of much importance for developers who aim for code optimization and for those who are not interested in integrating a third-party concept to their code.