demo · v134 · performance
Policy Bundle Builder
Configure a page (HTML size, embedded JS, inline-everything? linked CSS?) — see whether the expect-no-linked-resources hint is appropriate, and get the matching Document-Policy header + estimated parse-time savings.
page profile
20 KB
0
0
1
?
verdict
0
ms parse saved (est.)
resulting header
Document-Policy: expect-no-linked-resources
matching meta tag
<meta http-equiv="Document-Policy" content="expect-no-linked-resources">
when this hint is worth setting
Speculative HTML pre-parsing exists because most pages declare lots of subresource references in their markup; pre-parsing kicks fetches off early. But if you're shipping a tiny SPA shell that just bootstraps a single bundle and inlines everything else, the speculative pass is pure overhead.
expect-no-linked-resources tells the browser: skip speculative parsing — there's nothing to find. Misuse the hint and you regress LCP; use it correctly on a small shell and you trim a few ms off the critical path.