As @mdekker , I was considering AMP for my e-commerce site but soon realised that doing so would mean to AMP-everything, which goes against pretty much every other web technology out there.
Do you want to have your own amazing web content manager, an awesome menu and advanced e-commerce search (like Thirty-bees’ Elastic Search Project)? You better forget about all of that. Nothing will work. NOTHING.
I decided to take a different approach and optimize everything on my Thirty-bees store to reach a sub-second page load time, and optimize it even further for mobiles. I.e.:
Reduce the DOM size. Doing so will allow slower clients (such as mobiles) to render your Thirty-bees store faster
Reduce the amount of fancy CSS animations and transitions. These give extra-load to the browser for rendering, compositing and painting everything on the screen. Since a mobile has a very limited amount of resources, this impacts directly on the website rendering performance.
Use a full-page cache option, Thirty-Bees has many of them in the Performance section.
And the list could go on and on and on, but I guess you get the idea.
I prefer to personalize my store with the technologies that I love. Google’s AMP was against everything I’ve learned and loved about web development.
@mdekker It looks like I need to override beesblogpost.php, beesblog.php and post_list_item.tpl. I cannot find a reference to post_list_item in any file so will have to add it. Unless I am missing the elephant in the room?