3 ms·
Isn't the first thing AMP does pull in some javascript that was required to render the page? I recall there being some relatively long delay showing an empty pa
by the8472 5y ago
Isn't the first thing AMP does pull in some javascript that was required to render the page? I recall there being some relatively long delay showing an empty page if you had some stuff blocked because it was waiting for a fallback. Or maybe that was some other google thing that did it. That's exactly the opposite of HTML first with small sprinkles of CSS and JS.
- ignoramous 5y agoWell, I meant, a web-standard like AMP aimed at clamping down webpage-obesity would be nice (instead of AMP).
- the8472 5y agoI think most of that could be achieved by a bunch of CSP rules that disable various features. No frames, no 3rd-party js, various request types restricted to same-site and data: URIs. Don't grant sandbox: allow-same-origin and the site will be a unique origin on each visit, thus effectively disabling cookies. So it's already possible to achieve quite restricted subsets of what a website can do. The issue is agreeing on what subset is useful enough for many sites.