Re:Justice Department meeting state AG offices Tuesday to di...
by judge2020 on Monday February 03, 2020 @07:57PM
(#22231197)
The issue is that AMP forces companies to use a lightweight site instead of just letting them know how to build a good lightweight site. When you can't include a bunch of bad legacy code and a bunch of off-site resources, the page speeds up dramatically regardless of if it's amp or not. Unfortunately the only thing that made this push happen was Google prioritizing AMP.
[ Parent
| on HN ]
Re:Justice Department meeting state AG offices Tuesday to di...
by lern_too_spel on Monday February 03, 2020 @08:06PM
(#22231265)
> When you can't include a bunch of bad legacy code and a bunch of off-site resources, the page speeds up dramatically regardless of if it's amp or not.
This is true, but my point was that just doing that will still leave it slower than AMP, so the search engines will still prefer AMP results.
AMP pages can be safely prerendered, which is what makes all other options slower. If you defined your own HTML subset that allowed safe prerendering, you will have simply reinvented AMP, and you might as well contribute to the AMP project instead to get all the existing search engines to use it.