Hi all,
Wondering if anyone has implemented / is implementing AMP for some pages on their website?
Or if you've looked at adopting some of the AMP design principles on your site to help speed things up?
Would love to hear from you!
meg
Still on TNEW v6: I'm in the process of this. No plans for AMP at the moment, but I'm a little weary of maintaining another version of our site. We did some performance tuning in our somewhat bloated template by removing some un-needed scripts, stylesheets, images, etc.
So far I've shed about 3 seconds off our page load time with these tweaks. Our biggest bottleneck at the moment is the amount of API calls required on the TNEW event listing, but we have bypassed that by using our marketing site instead.
In process: - The second phase of this is moving images and our stylesheets into a high-speed CDN instead of our web server. This reduces the load on that server and potentially creates a speed boost in load times for those images.
Cons: AMP is horrible, it breaks the web.
Pros: AMP actually is a great resource for designers that are stuck with the task of implementing horrible designs. Forced to make a horrible consumer-hostile design by a customer? Use AMP to make the web better under the guise of search. It forces sites whose content is mainly text or information to follow strict guidelines. The mobile portion is really just the tip of the iceberg.
+100