Accelerated Mobile Pages

From IndieWeb
Jump to: navigation, search

Accelerated Mobile Pages (AMP) is a Google-led project that speeds up a subset of HTML through caching and dependencies on google:

IndieWeb Support

The pull request by Aaron Parecki adds h-entry support to AMP example(s) and thus makes AMP more IndieWeb friendly by default

The PR was subsequently closed with the comment "We decided to remove metadata requirements from AMP." See:


XML like fragility

It appears that initial implementation(s) of AMP HTML consuming code treat it similarly to old XML consuming code, which is to fail in a fragile way, e.g. as noted in


Screenshot of an Android device showing trying to display an article from with only a sad-mobile-device graphic and an error message:
Sorry, this page is not valid AMP HTML
followed by a footer link to continue to

Additional citations:


More: (to be put into citation template, and inserted into the above list)

See Also

  • Google
  • Twitter
  • 2017-10-26 Ethan Marcotte: Seven into seven.
    Significant features and changes require the approval of AMP’s Technical Lead and one Core Committer, that list seems exclusively staffed and led by Google employees
  • 2018-06-03 Jeremy Keith AMPstinction
    performance on the web is so important that it deserves a long-term solution, co-created by all of us: not some commandents delivered to us from on-high by one organisation, enforced by preferential treatment by that organisation’s monopoly in search.
    • "lol, amp. i noticed that a page would suddenly appear after 8 seconds of waiting if i disabled js, which seemed pretty weird.
      turns out that there's a css3 anim to hide the page for 8 full seconds (that is skipped when the js loads ofc). this is *required* by the amp standard.
      your page fails validation if you don't do this.sure makes these goog results look kinda suspicious, huh" @🌺 Revya Centauros 🌸 August 5, 2018
  • 2018-09-05 The mysterious case of missing URLs and Google's AMP