4 ms·
It was often 10000ms for me, and there would be popups and paywalls that AMP circumvents.
by dheera 5y ago
It was often 10000ms for me, and there would be popups and paywalls that AMP circumvents.
- missblit 5y agoAMP actually supports paywalls: https://amp.dev/documentation/components/amp-access/ https://amp.dev/documentation/components/amp-access/ This extension is also actually kinda interesting in that it embeds a small domain specific language [1] that's interpreted with a lex-style parser in JavaScript. This can itself be a bit heavy on the CPU if a website uses it too judiciously! [1] https://github.com/ampproject/amphtml/blob/main/extensions/amp-access/0.1/access-expr-impl.jison https://github.com/ampproject/amphtml/blob/main/extensions/a...
- goodcanadian 5y agoIt's fascinating to me as I moved away from Chrome on mobile specifically because amp caused me so many problems. The solution to page load failures was always editing the URL to give me the original which worked so much better. Hear that Google? The experience was so bad that I changed browsers to avoid it.