When I launched a pet products website, wordpress was thinking about creating it on a classic html basis because of its heavy behavior, and I found an ad for "Google AMP".
I don't remember the details,
"Increase AD CLICK rate on mobile sites accelerated by amp sites"
I think it was a catchphrase like that.
Sites with classic configurations of html, css, and jquery are very light and fast.
AMP is accelerated by the presence of a CDN (content distribution network) of a site made of AMP called "AMP Cache".
It's a good opportunity, so I decided to build a site using Google AMP.
The actual page → FORSMILE
This article provides an overview of AMP and how it can benefit you.
What is Google Amp? Get an overview
AMP means Accelerated Mobile Pages.
AMP Homepage→AMP
Officially, it is called the "Web Component Framework".
I roughly checked the contents, it is a feeling that the hard design part was pulled out from "ONSEN UI" or "Vuetify".
Just like the ONSEN UI and Vuetify, you can use AMP own "tags" in addition to html tags.
I think there are a lot of tags that are optimized mainly for functionality.
JavaScript frameworks like Vue, it simply feels like only tags are added.
AMP's own coding rules exist, and debugging detects errors if you violate them.
AMP coding rules are fine-grained on a page-by-page, tag-by-tag page, but you can detect coding that doesn't match the rules in the debug above. It seems to be troublesome somehow, but if you are an engineer who has experienced speeding up the website, it will be a convincing rule.
If you express AMP in one word, it is exactly as the following phrase on the official website.
"AMP is a simple and robust format to ensure your website is fast, user-first, and makes money."
Well, what I felt when I actually introduced it is that there are rules that are not very related to speedup, and that religious disputes are likely to occur among engineers. I'm implementing it and I'm like, "Is that it? Isn't this a good thing? I also thought. It is discussed in GIT etc., and it seems that it is a policy to develop while incorporating the opinions of users in the future, so it is interesting that there is still a possibility that it will change in the future.
3 Benefits of USING AMP
Become an SEO measure. Especially mobile
The official announcement declares that whether amp is in place or not will not affect your search standings. However, as an evaluation criterion for current SEO, there is a tendency to place importance on "speed" such as display speed and not causing users to wait time. Therefore, it can be said that amp sites that simply display faster are a framework that can gain a considerable advantage from an SEO point of view.
–Added on 2020/12/02
It was quick for the PC page to rise to the top of the search engine. Although it is multiple keywords, the site was displayed firmly in the search results. In the case of landing pages that are not AMP, some pages are finally displayed in the search by making full use of external links and internal links. The article that was changed to AMP and uploaded was a hit in less than 7 days only by Organic Search without any measures against external links.
As it may happen, AMP seems to have an SEO advantage.
Faster display speeds and less user departure due to load delays
This renders faster than you can experience. There are still parts that depend on the image for image loading, but I feel that it is also fast thanks to the page being cached by a mechanism called "AMP Cache".
Slower screen display results in a lower rate of user withdrawal, which is likely to be closer to a more user-first page.
Useful tags become available
Adding AMP makes it possible to use tags that make it easy to create different components.
It is attractive that various tags are available, from carousels and accordion dynamic components to cooperation with SNS such as Twitter.
Disadvantages of using AMP
Currently, I think that there are many cases that are not suitable for AMP except for pages with very simple configurations.
It is due to amp's own coding rules mentioned in the overview. This rule can be faster, but having it can't introduce other frameworks or introduce it to existing pages.
If you have an existing website, we recommend that you create a new AMP page separately instead of refactoring the existing page. As a search engine countermeasure, you can link existing pages and AMP pages using html's same page judgment mechanism (link rel="canonical").
In addition, because unique coding rules are set for each tag, it often does not work even if the tag is embedded unless you think about the structure of the html and code it. In addition, there are cases where cooperation with other platforms (Google Adsense, etc.) does not work well, and I think that it is a disadvantage that it still remains a developing feeling.
AMP's Recommended Degree
It will be a complete my opinion, but I thought it would be good to use it if it is a simple site.
If you decided to use it for business, the addition of AMP will cause pages that can be implemented in AMP and pages that cannot be implemented in AMP, so there is an unnecessary design cost. However, I doubt whether complex pages can benefit from AMP. This is because approximate web page conversions are not realized by page display speed alone. Amp is only used for conductor pages from Twitter and advertisements, but I think it is good at this stage.
I started making it, so I will continue to use it as it is. I want the day will come when the above evaluation will change.