We also remember, as in the note at the beginning of the chapter, that the types of resources that risk benefiting most from the AMP features would be precisely those related to news sites, having a rapid and continuous turnover of news and therefore having to support a significant amount of traffic as a hardware structure and an almost absolute readability as a human experience.
This sort of problem that prevents (perhaps) in the firm and unchanged old form of scripts from many too many years ago. Old companies, with old developers (inside) who do not update their technical offers due to the benefit of our ios database laziness or rather inability, often denying those who turn to them (not always a capable technician) the possibility of improving their appeal to end users.
Let's move on to the graphic elements.
As mentioned above, a minimal visualization of the "colorful" aspects of the situation may not always be a super successful solution.
The conversion power of a nice, qualitatively decent shot or a pop-up generated by a plugin, or even a carousel of news or photographs, can be lost if the scripts are not compatible with AMP and you are not able to fix it, potentially leading to even fewer conversions, if originally the solution adopted also caught them with tailor-made calls to action . AMP is therefore a decidedly effective solution if we know where to put our hands, but it is certainly not the philosopher's stone of performance on a site and will help little if, even if the site/blog itself is very fast, there are still structural flaws or content unsuitable to generate even "only" leads.