[dmix]

As long as the top of the article content (headline + first few paragraphs) loads immediately I don't care if it loads 700kb afterwards for other interactive content. 'Progressive enhancement' should be the primary goal; size reduction is just one means to achieving that but not always required.

From testing out one of the example blogs and this doesn't seem to be a UX issue:

https://bricolage.io/tools-administer-facebook-groups/

[maerek]

That's not progressive enhancement, it's lazy loading.

Progressive enhancement would be making all of the content visible and accessible, then adding functionality on top after the base page load is complete. If JS is required to simply view the text on a page, you're doing it wrong.

[morgante]

GP clearly stated that JavaScript is not required to view the text on the page.

[dmix]

Is that not a rewording of what I just said?

[dredmorbius]

You might not. A capped-bandwidth or pay-by-the-byte mobile user might.