How to fight back against Google AMP as a web user and a web developer (markosaric.com)

Article summary

The article discusses the issues with Google AMP and how it can be avoided by users and developers. It suggests using alternative search engines and browsers, and optimizing website speed without using AMP. The article also highlights the potential conflict of interest between Google's goal of a faster web and its own advertising business. By optimizing website speed and using alternative solutions, developers can create faster and more open web experiences without relying on AMP.

Main themes

• Google AMP
• Alternative search engines
• Browser choice
• Website optimization
• Conflict of interest
• Decentralized web
• Open standards
• Page speed and performance
• Advertising and revenue models
• Web diversity and innovation

What commenters say

• Google's penalties for slow page loading may not be effective in improving page speed due to its own conflict of interest in advertising revenue.
• AMP demotivates page speed performance improvements and favors large commercial websites over independent ones.
• Alternative search engines and browsers can help reduce reliance on Google and AMP.
• Optimizing website speed and using progressive image loading can improve user experience without relying on AMP.
• Google's control over the web through AMP and search rankings can stifle innovation and diversity.
• The use of AMP is driven by its fast loading times, but this may not be the only factor in its popularity.
• Developers should prioritize speed and user experience when building websites, rather than relying on AMP or other shortcuts.
• The web would benefit from more decentralized and open solutions, such as federated search and neutral replacements for AMP.
• Google's dominance in search and advertising makes it difficult for alternative solutions to gain traction.