Google加速移动页面（AMP）简介

﹏ヽ暗。殇╰゛Y 2022-12-03 10:00 210阅读 0赞

*This article is also available [in French][]*

*本文也提供[法语版本][in French]*

[Google’s Accelerated Mobile Pages][Google_s Accelerated Mobile Pages] initiative is getting a lot of exposure since [its launch][] in early October. Let’s see what it is, how it works, and how you can publish your own AMP HTML pages.

自10月初[推出][its launch]以来， [Google的“加速的移动页面”][Google_s Accelerated Mobile Pages]计划获得了广泛的关注。 让我们看看它是什么，它如何工作以及如何发布自己的AMP HTML页面。

## 速度问题 **(**Speed Matters**)** ##

In this age of speed, a page that takes more than a few seconds to load is losing its appeal, and this is especially important on mobile phones.

在当今这样的速度时代，需要花费几秒钟才能加载的页面已失去吸引力，这在移动电话上尤其重要。

Many studies have shown that page load has a direct impact on sales. For instance, [conversion rates drop 27% after one second, and bounce rates drop 56%][conversion rates drop 27_ after one second_ and bounce rates drop 56] after the same amount of time.

许多研究表明页面加载量直接影响销售。 例如， [转换率在一秒钟后下降27％，而跳出率][conversion rates drop 27_ after one second_ and bounce rates drop 56]在相同时间后[下降56％][conversion rates drop 27_ after one second_ and bounce rates drop 56] 。

On the SEO side, [page speed is one of the many ranking factors][] for Google, hence your site’s visibility is at risk if it’s too slow.

在SEO方面， [页面速度是][page speed is one of the many ranking factors] Google [排名的众多因素][page speed is one of the many ranking factors]之一，因此，如果网站速度太慢，则其可见度会受到威胁。

Therefore, user experience, business goals, and findability are all impacted by site speed.

因此，用户体验，业务目标和可发现性都受站点速度的影响。

Responsive web design and carefully-crafted sites with performance in mind are part of the solution. While working on these issues, [we can’t blame others][we can_t blame others], or we’ll soon get closed inside walled gardens.

解决方案包括响应式网页设计和精心设计的网站，同时兼顾性能。 在解决这些问题时， [我们不能责怪其他人][we can_t blame others] ，否则我们很快就会在有围墙的花园中封闭。

[Facebook’s Instant Articles][Facebook_s Instant Articles] and [Apple News][] are answering these issues in their own way. Fortunately, the [AMP Project][], while promoted by Google, is an open-source project and you should give it a try.

[Facebook的Instant Articles][Facebook_s Instant Articles]和[Apple News][]正在以自己的方式回答这些问题。 幸运的是，由Google推动的[AMP项目][AMP Project]是一个开源项目，您应该尝试一下。

![AMP Page by the Washington Post][]

*[source][]*

*[资源][source]*

## AMP功能概述 **(**An Overview of AMP’s Features**)** ##

Performance best practices are built-in with AMP: asynchronous calls and lazy-loading on components, no repaint while loading the page, no FOUC effect, inlined critical CSS, no extensive use of the CPU and GPU, minimal JavaScript usage, a CDN by default for scripts, and a minimal tracking footprint.

AMP内置了性能最佳实践：组件上的异步调用和延迟加载，加载页面时不重绘，无FOUC效果，内联关键CSS， CPU和GPU的广泛使用，JavaScript的最少使用， CDN默认为脚本，并且跟踪足迹最少。

Everything that we should keep in mind when developing fast rendering pages has been enforced for us:

在开发快速渲染页面时我们应牢记的一切已为我们执行：

*  A [subset of HTML][] with a [few new tags][] to be handled by the JavaScript runtime renderer;
    
    [HTML][subset of HTML]的[子集，][subset of HTML]其中包含[一些新标签][few new tags] ，这些[标签][few new tags]将由JavaScript运行时渲染器处理；
 *  Only a [subset of CSS][few new tags] allowed;
    
    只允许[CSS][few new tags]的[子集][few new tags] ；
 *  One JavaScript to rule them all, and only a few allowed scripts for the extensions, all of them delivered through Google’s CDN;
    
    一种JavaScript统治所有这些脚本，只有少数允许扩展的脚本，所有这些脚本都是通过Google的CDN交付的；
 *  Each component width and height declared to prevent any repaint when loaded asynchronously.
    
    声明每个组件的宽度和高度，以防止在异步加载时进行任何重新绘制。

![AMP page by The Guardian][]

*[source][source 1]*

*[资源][source 1]*

## AMP页面的剖析 **(**Anatomy of an AMP Page**)** ##

Here is a minimalist AMP page:

这是一个简约的AMP页面：

<!doctype html>
    <html amp lang="en">
      <head>
        <meta charset="utf-8">
        <link rel="canonical" href="__CANONICAL_URL__" >
        <meta name="viewport"
              content="width=device-width,minimum-scale=1,initial-scale=1">
        <style>body {opacity: 0}</style>
        <noscript>
          <style>body {opacity: 1}</style>
        </noscript>
        <style amp-custom>
          __YOUR_OWN_CSS__
        </style>
        <script async src="https://cdn.ampproject.org/v0.js">
        </script>
      </head>
      <body>
        Your actual content.
      </body>
    </html>

As you can see, there is a default style to which you can add your own inline CSS, and an asynchronously-called script hosted on a CDN. We also have a viewport meta tag and a canonical link. And that’s about it.

如您所见，有一种默认样式，您可以向其中添加自己的内联CSS，以及CDN上托管的一个异步调用脚本。 我们还有一个视口元标记和规范链接。 就是这样。

**Styles** You can add your own styles within the `<style amp-custom>` element. However, [not all features are allowed][few new tags].

**样式**您可以在`<style amp-custom>`元素中添加自己的样式。 但是， [并非所有功能都允许][few new tags] 。

**JavaScript** The AMP JavaScript library includes built-in components and handles the loading of external resources behind the scenes, extensively lazy-loading as much as it can. It is also responsible for the painting of the page.

**JavaScript** AMP JavaScript库包含内置组件，可处理后台的外部资源加载，并尽可能多地进行延迟加载。 它也负责页面的绘画。

![AMP page on the NYTimes][]

*[source][source 2]*

*[资源][source 2]*

## 动手问答 **(**Hands-on Questions & Answers**)** ##

**How can I validate my AMP HTML code?** The validation of the code is provided within the Google Chrome’s DevTools. Navigating to your page with the hash *\#development=1* added at the end of the URL enables validation.

**如何验证我的AMP HTML代码？** 在Google Chrome的DevTools中提供了代码验证。 使用URL末尾添加的＃development *= 1*哈希导航到您的页面可启用验证。

**How do I reference an AMP HTML page in a normal HTML page?** AMP pages are declared as an alternative type of content, a bit like an RSS feed. Yet, the full auto-discovery mechanism used for RSS has not been implemented, as it would have required the creation of another MIME type like `text/amphtml`.

**如何在普通HTML页面中引用AMP HTML页面？** AMP页面被声明为替代内容类型，有点类似于RSS feed。 但是，尚未实现用于RSS的完全自动发现机制，因为这将需要创建另一个MIME类型，如`text/amphtml` 。

Instead, we use a new value for the `<link>` tag’s `rel` attribute in the head of the matching regular HTML page.

相反，我们在匹配的常规HTML页面的开头为`<link>`标记的`rel`属性使用新值。

**How do I tell browsers the AMP HTML page exists?** We can tell the browser an AMP page is a version of a full-fledged HTML page. As we don’t want any duplicate content penalty, we declare that page as canonical.

**如何告诉浏览器AMP HTML页面存在？** 我们可以告诉浏览器AMP页面是完整HTML页面的版本。 由于我们不希望重复内容，因此我们将该页面声明为规范页面。

**What is the SEO advantage to using this new format?** As we’ve seen above, an AMP page is a related version of a regular page, declared as canonical. Search engines will not list both pages, only the canonical page – unless the search is performed on a mobile device, in which case the AMP page could be favored.

**使用这种新格式的SEO有何优势？** 正如我们在上面看到的，AMP页面是常规页面的相关版本，声明为规范页面。 搜索引擎将不会列出两个页面，只会列出规范页面-除非搜索是在移动设备上进行的，否则可能会偏向AMP页面。

When searching for a specific news item, a carousel with the matching AMP pages previews is shown, as you can see [in this YouTube video by Addy Osmani][].

在搜索特定新闻时，会显示带有匹配AMP页面预览的轮播，就像您[在YouTube视频中Addy Osmani所][in this YouTube video by Addy Osmani]看到的[那样][in this YouTube video by Addy Osmani] 。

**Why does AMP HTML have a CSS rule that hides the <body> element?** The `<body>` element is hidden by default with CSS opacity when JavaScript is not supported by the client. As the whole layout is rendered by AMP’s JavaScript, the temporarily hidden body prevents the display of a broken page.

**为什么AMP HTML具有隐藏<body>元素CSS规则？** 当客户端不支持JavaScript时，默认情况下， `<body>`元素以CSS不透明性隐藏。 由于整个布局是由AMPJavaScript呈现的，因此临时隐藏的正文可防止显示损坏的页面。

There is another advantage to this, as it prevents any FOUT effect when using a CSS font. Usually, the browser loads the CSS font as soon as it encounters it in a style applied to an element of the document, hence it can start rendering the page before calling that external font. In an AMP page, the opacity style is removed once the fonts used in the page are loaded.

这还有另一个优点，因为它可以防止在使用CSS字体时产生任何FOUT效果。 通常，浏览器以适用于文档元素的样式加载CSS字体后立即加载，因此它可以在调用该外部字体之前开始呈现页面。 在AMP页面中，加载页面中使用的字体后，不透明度样式将被删除。

**How do I embed an image?** The `<img>` element is not supported by AMP and is replaced by the `<amp-img>` element. An [AMP image][] must set its width and height, and provides support for an `attribution` attribute.

**如何嵌入图像？** AMP不支持`<img>`元素，而将其替换为`<amp-img>`元素。 [AMP图像][AMP image]必须设置其宽度和高度，并支持`attribution`属性。

**How do I embed a video?** The HTML5 `<video>` element is replaced by the [amp-video][] element, and is a built-in component.

**如何嵌入视频？** HTML5 `<video>`元素被[amp-video][]元素替换，并且是一个内置组件。

Among the supported extensions, you can find a [YouTube extension][] to handle YouTube videos. Like for the other extensions, you need to call specific JavaScript in the `<head>` of your page to support it, in this case:

在受支持的扩展程序中，您可以找到一个[YouTube扩展程序][YouTube extension]来处理YouTube视频。 与其他扩展一样，您需要在页面的`<head>`中调用特定JavaScript来支持它，在这种情况下：

If you want to support responsive videos, the width and height values of your component should match the 16:9 aspect ratio.

如果要支持自适应视频，则组件的宽度和高度值应匹配16：9的宽高比。

<amp-youtube
      data-videoid="SqT0glwuYYo"
      layout="responsive"
      width="480" height="270">
    </amp-youtube>

**Are there other components available?** The AMP components are divided into built-in components (directly supported by the main JavaScript renderer) and extensions (which require calling a specific script for each).

**还有其他可用组件吗？** AMP组件分为内置组件(由主JavaScript渲染器直接支持)和扩展名(需要分别为它们调用特定的脚本)。

The [current list of built-in components][] includes:

[当前内置组件的列表][current list of built-in components]包括：

*  amp-ad: container to display an ad
    
    amp-ad：显示广告的容器
 *  amp-img: replacement for the HTML `<img>` element
    
    amp-img：替换HTML `<img>`元素
 *  amp-pixel: used as tracking pixel to count page views
    
    安培像素：用作跟踪像素以计算网页浏览量
 *  amp-video: replacement for the HTML5 `<video>` element
    
    amp-video：替换HTML5 `<video>`元素

The [current list of extensions][] includes:

[当前扩展列表][current list of extensions]包括：

*  amp-anim: runtime-managed animated image, most typically a GIF
    
    amp-anim：运行时管理的动画图像，通常是GIF
 *  amp-audio: replacement for the HTML5 `<audio>` element
    
    amp-audio：替代HTML5 `<audio>`元素
 *  amp-carousel: generic carousel for displaying multiple similar pieces of content along a horizontal axis
    
    amp-carousel：通用轮播，用于沿水平轴显示多个相似的内容
 *  amp-fit-text: expand or shrink font size to fit the content within the space given
    
    amp-fit-text：扩大或缩小字体大小以使内容适合给定空间
 *  amp-iframe: displays an iframe element
    
    amp-iframe：显示iframe元素
 *  amp-image-lightbox: allows for an “image lightbox” or similar experience
    
    amp-image-lightbox：允许使用“ image lightbox”或类似的体验
 *  amp-instagram: displays an instagram embed
    
    amp-instagram：显示嵌入的instagram
 *  amp-lightbox: allows for a “lightbox” or similar experience
    
    amp-lightbox：允许“ lightbox”或类似的体验
 *  amp-twitter: displays a single tweet
    
    amp-twitter：显示一条推文
 *  amp-youtube: displays a YouTube video
    
    amp-youtube：显示YouTube视频

**How do I display an ad from Google AdSense?** The [*amp-ad* component][amp-ad_ component] is used to display an ad. Like with other components, the width and height values must be set (I guess you’re used to this by now).

**如何显示来自Google AdSense的广告？** [*amp-ad*组件][amp-ad_ component]用于显示广告。 与其他组件一样，必须设置width和height的值(我想您现在已经习惯了)。

To display an AdSense ad, the code is as follow (don’t forget to replace the values of the `data-ad-client` and `data-ad-slot` attributes with your own).

要显示AdSense广告，代码如下(不要忘记用您自己的`data-ad-client`和`data-ad-slot`属性值替换)。

<amp-ad width="300" height="200" type="adsense"
      data-ad-client="ca-pub-1234567890123456"
      data-ad-slot="1234567890">
    </amp-ad>

The currently supported ad networks are [A9][], [AdReactor][], [AdSense][], [AdTech][], and [Doubleclick][]. Each comes with its own set of attributes. You can also [run ads from a custom domain][amp-ad_ component].

目前支持的广告网络是[A9][] ， [AdReactor][] ， [AdSense的][AdSense] ， [AdTech的][AdTech] ，并[双击][Doubleclick] 。 每个都有其自己的属性集。 您还[可以投放来自自定义域的广告][amp-ad_ component] 。

**How can I track my visitors with Google Analytics?** Trackers are implemented through the [amp-pixel element][] to count page views. To use a Google Analytics tracker on an AMP page, you need to follow the [Analytics Measurement Protocol ][Analytics Measurement Protocol]:

**如何使用Google Analytics(分析)跟踪访问者？** 跟踪器是通过[amp-pixel元素实现的，][amp-pixel element]以对页面浏览量进行计数。 要在AMP页面上使用Google Analytics(分析)跟踪器，您需要遵循[Analytics(分析)衡量协议][Analytics Measurement Protocol] ：

<amp-pixel src="https://ssl.google-analytics.com/collect?v=1
                    &tid=UA-12345678-1&t=pageview&cid=__CID__
                    &dt=__PAGE_TITLE__&dl=__PAGE_URL__
                    &z=__RANDOM_STRING__">
    </amp-pixel>

The Client ID (`CID` value) is generated on the server side as [valid v4 UUID][], the `PAGE_TITLE` and the `PAGE_URL` should be URL-encoded, and the `z` parameter is a cache buster.

客户端ID( `CID`值)在服务器端生成为[有效的v4 UUID][valid v4 UUID] ， `PAGE_TITLE`和`PAGE_URL`应该进行URL编码，并且`z`参数是缓存无效项。

## 速度提高 **(**The Speed Gained**)** ##

[Andy Davies][] shows us some benefits of the AMP pages implemented by The Guardian and BuzzFeed. Using [WebPageTest][], he’s painted a mixed picture about the speed gained for a variety of networks.

[安迪·戴维斯(Andy Davies)][Andy Davies]向我们展示了《卫报》和BuzzFeed实施的AMP页面的一些好处。 使用[WebPageTest][] ，他对各种网络所获得的速度描绘出了混杂的画面。

Here’s the same comparison with a regular site hosted in France on one server and called from the New York City, USA. The top set of images is the current [full-fledged web page][], and the bottom is the [AMP version][].

这与在法国托管在法国一台服务器上并从美国纽约市调用的常规站点的比较相同。 顶部的图像是当前[完整的网页][full-fledged web page] ，底部的是[AMP版本][AMP version] 。

**3G**

**3GFast**

**3G快**

**Cable**

**电缆**

**No network shaping**

**没有网络整形**

The regular page makes 34 HTTP requests, while the AMP version makes only 13. Of course the number of requests (and the page weight) varies depending on the ad served. The AMP version is always faster, it starts rendering about half a second before the vanilla version, and is sometimes visually complete even before the vanilla version starts rendering (on the 3G and cable connections).

常规页面发出34个HTTP请求，而AMP版本仅发出13个请求。当然，请求的数量(和页面权重)取决于所投放的广告。 AMP版本始终更快，它开始渲染的时间比香草版本早半秒，有时甚至在香草版本开始渲染之前(在3G和电缆连接上)在视觉上也完整。

I warmly invite you to take the test once you have a working example in your own code structure, as the results depend a lot on the optimisations you have implemented.

在您自己的代码结构中有一个有效的示例后，我热烈地邀请您参加测试，因为结果在很大程度上取决于您实现的优化。

![AMP page on Washington Post][]

*[source][source 3]*

*[资源][source 3]*

## 大型出版商的一些设计思路 **(**Some Design Ideas From Big Publishers**)** ##

The AMP format has already been embraced by many big players in the publishing industry. Here is a short list of a few of them, to illustrate their take on the design simplification.

AMP格式已经为出版业中的许多大型公司所接受。 这里是其中一些的简短列表，以说明他们对简化设计的看法。

*  The Guardian: [regular HTML][] / [AMP][source 1]
    
    卫报： [常规HTML][regular HTML] / [AMP][source 1]
 *  The Washington Post: [regular HTML][regular HTML 1] / [AMP][source]
    
    华盛顿邮报： [常规HTML][regular HTML 1] / [AMP][source]
 *  El País: [regular HTML][regular HTML 2] / [AMP][]
    
    埃尔帕斯： [常规HTML][regular HTML 2] / [AMP][]
 *  Folha de São Paulo: [regular HTML][regular HTML 3] / [AMP][AMP 1]
    
    圣保罗剧院(Folha deSãoPaulo)： [常规HTML][regular HTML 3] / [AMP][AMP 1]
 *  La Stampa: [regular HTML][regular HTML 4] / [AMP][AMP 2]
    
    La Stampa： [常规HTML][regular HTML 4] / [AMP][AMP 2]
 *  The New York Times: [regular HTML][regular HTML 5] / [AMP][source 2]
    
    纽约时报： [常规HTML][regular HTML 5] / [AMP][source 2]
 *  The Atlantic: [regular HTML][regular HTML 6] / [AMP][AMP 3]
    
    大西洋： [常规HTML][regular HTML 6] / [AMP][AMP 3]

## 现在轮到你了 **(**Now It’s Your Turn**)** ##

The [Accelerated Mobile Pages][Google_s Accelerated Mobile Pages] initiative is all about speed to deliver pages. To enforce its rules, many restrictions are applied – but in these limitations lies a real freedom to focus on content.

[加速移动页面][Google_s Accelerated Mobile Pages]计划的主要目的是提高页面交付速度。 为了执行其规则，应用了许多限制-但是在这些限制中，存在着真正专注于内容的自由。

You have seen in this article the steps needed to develop simple yet fully functional pages with pictures, videos, ads, and trackers. Animations, carousels, SVGs, and many other components are available to create great user experiences.

您已在本文中看到了开发带有图片，视频，广告和跟踪器的简单但功能齐全的页面所需的步骤。 可以使用动画，轮播，SVG和许多其他组件来创建出色的用户体验。

It would be great if you could share your own creations in the comments.

如果您可以在评论中分享自己的作品，那就太好了。

> 翻译自: [https://www.sitepoint.com/an-introduction-to-googles-accelerated-mobile-pages-amp/][https_www.sitepoint.com_an-introduction-to-googles-accelerated-mobile-pages-amp]

[in French]: https://www.linkedin.com/pulse/introduction-%C3%A0-lamp-de-google-accelerated-mobile-pages-alexis-ulrich
[Google_s Accelerated Mobile Pages]: https://www.ampproject.org/
[its launch]: https://googleblog.blogspot.ca/2015/10/introducing-accelerated-mobile-pages.html
[conversion rates drop 27_ after one second_ and bounce rates drop 56]: https://www.soasta.com/blog/mobile-web-performance-monitoring-conversion-rate/
[page speed is one of the many ranking factors]: https://www.mattcutts.com/blog/site-speed/
[we can_t blame others]: https://www.sitepoint.com/2mb-web-pages-whos-blame/
[Facebook_s Instant Articles]: https://instantarticles.fb.com/
[Apple News]: https://www.apple.com/news/
[AMP Project]: https://www.ampproject.org
[AMP Page by the Washington Post]: /images/20221123/94fe288d84fb48cd99586c592eab5b8f.png
[source]: https://www.washingtonpost.com/amphtml/lifestyle/style/six-ways-the-martian-subverts-expectations/2015/10/05/6bba4d42-6873-11e5-8325-a42b5a459b1e_story.html
[subset of HTML]: https://github.com/ampproject/amphtml/blob/master/spec/amp-tag-addendum.md
[few new tags]: https://github.com/ampproject/amphtml/blob/master/spec/amp-html-format.md
[AMP page by The Guardian]: /images/20221123/efa7279277bb4a93a26d16944d3aaf78.png
[source 1]: https://www.theguardian.com/science/2015/oct/06/mars-photos-the-martian-movie-nasa/amp
[AMP page on the NYTimes]: /images/20221123/616ca0f82f504d248451a0ba10f4f542.png
[source 2]: http://mobile.nytimes.com/2015/10/26/business/media/virtual-reality-has-liftoff-from-fox-innovation-lab.amp.html
[in this YouTube video by Addy Osmani]: https://www.youtube.com/watch?v=i2_lAEzmOPo
[AMP image]: https://github.com/ampproject/amphtml/blob/master/builtins/amp-img.md
[amp-video]: https://github.com/ampproject/amphtml/blob/master/builtins/amp-video.md
[YouTube extension]: https://github.com/ampproject/amphtml/blob/master/extensions/amp-youtube/amp-youtube.md
[current list of built-in components]: https://github.com/ampproject/amphtml/tree/master/builtins
[current list of extensions]: https://github.com/ampproject/amphtml/tree/master/extensions
[amp-ad_ component]: https://github.com/ampproject/amphtml/blob/master/builtins/amp-ad.md
[A9]: https://github.com/ampproject/amphtml/blob/master/ads/a9.md
[AdReactor]: https://github.com/ampproject/amphtml/blob/master/ads/adreactor.md
[AdSense]: https://github.com/ampproject/amphtml/blob/master/ads/adsense.md
[AdTech]: https://github.com/ampproject/amphtml/blob/master/ads/adtech.md
[Doubleclick]: https://github.com/ampproject/amphtml/blob/master/ads/doubleclick.md
[amp-pixel element]: https://github.com/ampproject/amphtml/blob/master/builtins/amp-pixel.md
[Analytics Measurement Protocol]: https://developers.google.com/analytics/devguides/collection/protocol/v1/reference
[valid v4 UUID]: https://en.wikipedia.org/wiki/Universally_unique_identifier#Version_4_.28random.29
[Andy Davies]: http://andydavies.me/blog/2015/10/13/accelerated-mobile-pages-ive-more-questions-than-answers/
[WebPageTest]: http://www.webpagetest.org
[full-fledged web page]: http://www.languagesandnumbers.com/articles/en/petra-jordan
[AMP version]: http://www.languagesandnumbers.com/articles-amp/en/petra-jordan
[AMP page on Washington Post]: /images/20221123/78f04e38224a46ec9dca0af0458d0d6f.png
[source 3]: https://www.washingtonpost.com/amphtml/news/the-switch/wp/2015/10/06/the-martian-nasa-and-the-rise-of-a-science-entertainment-complex/
[regular HTML]: http://www.theguardian.com/science/2015/oct/06/mars-photos-the-martian-movie-nasa
[regular HTML 1]: https://www.washingtonpost.com/lifestyle/style/six-ways-the-martian-subverts-expectations/2015/10/05/6bba4d42-6873-11e5-8325-a42b5a459b1e_story.html
[regular HTML 2]: http://economia.elpais.com/economia/2015/10/04/actualidad/1443971365_887425.html
[AMP]: http://amphtml.googleusercontent.com/amphtml/pages/CAIiEAleCrkFZu7TQ6qalp_SjFcqGAgEKg8IACoHCAowp5WhCTC1s3EwnPOOAw
[regular HTML 3]: http://www1.folha.uol.com.br/ilustrada/2015/10/1700162-com-2-album-rock-psicodelico-do-boogarins-amplia-sucesso-fora-do-pais.shtml
[AMP 1]: http://m.folha.uol.com.br/amp/ilustrada/2015/10/1700162-com-2-album-rock-psicodelico-do-boogarins-amplia-sucesso-fora-do-pais.shtml
[regular HTML 4]: http://www.lastampa.it/2015/10/14/scienza/tuttoscienze/scattata-la-corsa-per-marte-e-non-c-soltanto-la-nasa-wizfUBQ6Ox0PgrOHfZmxDJ/pagina.html
[AMP 2]: http://www.lastampa.it/2015/10/14/scienza/tuttoscienze/scattata-la-corsa-per-marte-e-non-c-soltanto-la-nasa-wizfUBQ6Ox0PgrOHfZmxDJ/amphtml/pagina.amp.html
[regular HTML 5]: http://www.nytimes.com/2015/10/26/business/media/virtual-reality-has-liftoff-from-fox-innovation-lab.html
[regular HTML 6]: http://www.theatlantic.com/politics/archive/2015/10/a-short-history-of-whether-obama-is-black-enough-featuring-rupert-murdoch/409642/
[AMP 3]: https://amp.gstatic.com/v/the-atlantic-amphtml.googleusercontent.com/amphtml/pages/CAIiEGZTcFZtopP7g7u5imKTZxYqFAgEKg0IACoGCAowm_EEMKAiMPtZ?amp_js_v=0
[https_www.sitepoint.com_an-introduction-to-googles-accelerated-mobile-pages-amp]: https://www.sitepoint.com/an-introduction-to-googles-accelerated-mobile-pages-amp/