-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Description
What's the issue?
AMP pages often have missing images or other content in iOS.
How do we reproduce the issue?
Buy someone on the team an iPhone and let them use it as their primary device. They’ll soon spot broken pages.
Here’s the latest broken page which has caught my ire and finally made me come here to post this.
- https://rigor.com/blog/web-performance-bookshelf/amp?__twitter_impression=true - AMP validation passes but none of the main content loads (initial paragraph loads but scroll down and the actual books don’t load).
And here’s a handful more just by doing a Google search for “AMPhtml” and checking out the lightning bolt results to see which are broken:
-
https://www.ampproject.in/docs/ads/a4a_spec.html (AMP validation passes but large white space just above Boilerplate heading).
-
https://amp.dev/documentation/guides-and-tutorials/learn/intro-to-amphtml-ads/ - AMP validation passes but gap above menu bar when opening from Google SERPS and scrolling down the page as the “real URL” bar vanished and page menu bar doesn’t move up to fill the gap.
-
https://www.google.ie/amp/s/www.fenj.nl/seo/wat-is-amp-html/amp/ - Passes AMP Validation but headline is all broken - maybe due to a bad font?
-
https://www.google.ie/amp/s/resultadosdigitais.com.br/blog/o-que-e-google-amp-html/amp - Passes AMP Validation but scrolling up and down leads to long pauses of white space - in an iPhone XS (so a pretty decent phone!) on Home WIFI (so pretty decent connection).
-
https://www.google.ie/amp/s/swapps.com/blog/what-its-amp-and-why-you-should-use-it/amp/ - Passes AMP validation but headline is unreadable - black on dark blue. Real page has white font.
Will add more as I spot them.
I suspect in a lot of cases they are poorly coded sites. But then why do they pass AMP validation? And if AMP is so brittle and HTML is so robust (all of the above sites load fine with non-AMP versions) then why is AMP better?
What browsers are affected?
Safari - latest IOS 13.3.1 and every single version of AMP on Safari on iOS since AMP was launched has had these issues.
Which AMP version is affected?
Every single version of AMP on Safari on iOS since AMP was launched has had these issues.
AMP is a terrible experience in iOS. I presume it’s better in Chrome but maybe it’s the same there? If not can you browser detect iOS and automatically redirect those users to the real site? I for one would massively appreciate that as clicking the little bar, or opening in Safari from in app browser (e.g. Twitter) and then editing the URL to guess the non-AMP URL is massively frustrating and ruining the web for me.