Hacker News Reader

> - Constraining the html so that the load itself can't break privacy or add jank to the search result page.

Why this? If the HTML is already loaded from Google's servers, the load shouldn't be able to break privacy even more, and jank shouldn't be affected by the specific HTML that's being served, just by its size. So Google could just preload everything that's small enough.

View on HN

Good question. Preload that actually renders the documents includes running enough javascript and parsing enough CSS that the initial document will render. With a non-constrained document, that can include fetching resources not on Google's servers and which can peg the CPU, causing jank.

If you do constrain what can run in your preload to avoid these, you end up designing AMP.

Reply on news.ycombinator.com