![]() ![]() How does Google know to index the AMP pages? No, because the plugin adds a canonical tag to the AMP pages that leads to the original content. In order to see it, simply add /amp/ after the post’s original URL (and if that doesn’t work, try additing /?amp=1). ![]() From now on, the plugin will create an AMP version for every post or page you have on your site. In order to do so, use a custom action addition to WordPress, as explained here. Since AMP creates a leaner version of your internet site, it is likely that you won’t like some of the design changes, and you may wish to play a little with the CSS. So, after our quick introduction, let’s go to the technical part: Part #2: Setting up AMP on a WordPress Siteįirst you need to install this AMP Plugin by Automattic with the following link: Google AMP Cache – Google’s proxy server saves the pages, and optimizes their display to the user, which of course includes faster loading times. Loading Javascript in parallel to the page’s other elements – instead of upfront, avoids additional load time, which again, would harm the user experience. So, for example, replacing the tag with the tag enables the page to render the images only as the user sees it on his screen – instead of loading together with all the page’s elements, which would harm the user experience.ĪMP JS – only specific tags can be used in AMP pages, one of the main goals of AMP JS being to turn anything that contains Javascript into an asynchronous element. This appears to be one of the reasons that Google got involved, to find a solution that will address everyone’s interest.ĪMP is made up of three central elements:ĪMP HTML – a list of custom tags and a whole lot of restrictions (and a few additions that enable rich content). So okay, AdBlocker can solve the problem on the user’s end – but then we’re looking at a serious loss of ROI for the big publishers. In a funny Google video, they explained this issue in a rather amusing way by showing that the most problematic contributors to lag are the numerous advertising networks and analytics systems installed on the page. If that doesn’t scare you straight, consider another research finding that every second of delay when you website loaded, reduces your conversion rate by 3.5%. ![]() For example, KISSmetrics’ study found that 40% of a site’s visitors will leave if the loading time is greater than 3 seconds. Speed critically affects user experience. So yes, “mobile friendly”, “adapted” and “responsive” websites are terms we are already tiring of hearing, but they don’t actually solve the most significant factor on mobile sites – i.e., loading times. The reason that Google initiated this project to begin with is due the growing trend of site traffic seeping from the desktop to mobile devices, however most site owners have not yet adapted their site to be properly mobile-friendly (and probably will never do that properly…). Consider, for example, that Google recently added AMP to its search results pages, which comes together nicely with the new prioritization of mobile sites, as announced by Google in April of 2015 (note that priority is not yet being given to AMP pages, at least not officially, but this will certainly happen soon). However, the project has grown and gained momentum. The initial goal of AMP was to shorten the load time of news sites viewed on mobile devices. Implementing AMP Analytics through Google Tag ManagerĪ lot of content already published about this subject, and I’m not going to be reinventing the wheel here, but a short overview is in order to make sure everyone is on the same page:ĪMP is an open-source project, spearheaded by Google.Today I’m going to show you how to implement Google Analytics (or “AMP Analytics”) in your website, and how to install it through Google Tag Manager.īefore we get started, here is a list of topics we will be discussing: Google AMP Project is a very hot topic in these days.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |