That being said, there are technical reasons why this hasn't happened yet. The good news is that some web standards (ex: https://wicg.github.io/feature-policy/) are being worked on that would (hopefully) allow Google to verify performance of sites without relying on AMP.
This would give Google no excuse to give AMP content special treatment, and would hopefully relegate AMP to what it should've been since day one: a framework for performance, but one that wasn't required or bolstered by any Google-colored carrots.
> The developer may want to use the policy to assert a promise to a client or an embedder about the use—or lack of thereof—of certain features and APIs. For example, to enable certain types of "fast path" optimizations in the browser, or to assert a promise about conformance with some requirements set by other embedders - e.g. various social networks, search engines, and so on.
You're right that there's more to it though.
Website did ridiculous things for SEO when Google was the main traffic-driver on the web. Ridiculous. If Google sufficiently penalized bloat in ranking most websites would remove the bloat. But it never was a significant enough factor.
IIRC they treat AMP pages the same as any other in terms of ranking, but since AMP is super fast, it gets a natural boost.
(obviously AMP gets other benefits like the lightning bolt badge and inclusion in the carousel)
I believe that some of the data in the carousel is pulled from the way that AMP is structured, however I'm not 100% sure.
https://search.googleblog.com/2012/01/page-layout-algorithm-...
i think its kinda hilarious how there is this fixation with load speeds amongst web devs. most people i know are far more concerned with everything other than the load time.
The caveat comes in when no alternative exists, and when the access to some information of service on very constrained connections (such as you'd see in remote third-world regions with poor Internet access) meets some reasonable definition of vital, but I've not seen where AMP is playing a significant part in that.
For example, Reddit loads extremely fast, and AMP pages are absolute shit, I don't know why they decided to use it.
And I'd rather view the website as intended (minus the ads, sorry), than in a shitty cut down version that takes 3 seconds less to load.
Fast websites stayed fast, and slow websites stayed slow. They also gave out tons of free "speed test" tools to make it easy for developers to test their speed, and improve it. They even made apache and nginx plugins that would auto-optimize assets as it served them! And still basically nobody used them.
Plus it's not just about "faster than XXXms". What is that time measured to? Time to text on the screen? Can they game it by lazy-loading images, then videos, then ads, then 6mb of other javascript and social networking stuff and a comment system and...?
You could try a "size limit", but then you penalize asset heavy sites (like high-resolution image sharing sites, or video sites).
So their solution was to make a very restrictive system where you are forced to do things "the right way" (for at least one definition of "right"), and to pump that up in the search results.
Plugins were made for common blogging and news platforms, and now a portion of the web loads significantly faster for many, and I think that's a win.
It's not perfect, but it's at least the first thing that I've seen google try in this area that is actually working.
Obviously there is benefit to Google as a company in that now results that are served through their AMP system are faster than those of some of their competitors, and AMP gives them a nice easy way to pull some structured information from an article for things like the carousel or other non-search offerings, but I genuinely don't believe that was the main motivator, seeing as Google has years of examples of failed attempts to "fix" this problem (though maybe I'm just not cynical enough!).