4 ms·
That's primarily because of third party advertising and marketing / analytics scripts though. I really doubt the core client-side rendering of a page (which isn
by robomc 5y ago
That's primarily because of third party advertising and marketing / analytics scripts though. I really doubt the core client-side rendering of a page (which isn't even common for up-to-date implementations), and the bundled js required for that to take place, is what's sinking your battery.
It's also hard to picture a news website where the webpack chunks are going to be a noticeable fraction of the total page load expense, when images are factored in.
For example, on CNN's homepage, of the 10MB of data and 200 requests my browser did, around 1MB of it was actual core JS served from a CNN domain, and even less of it looked to have ever gone near a package manager.
- kreeben 5y agoAll that JS needs to become 1. parsed 2. lexed 3. eval'ed and executed Not cheaply, but expensively.
- cerved 5y agobut the article is about using frameworks to deliver the core as an app. What you're talking about is another problem
- robomc 5y agoTrying to picture a major website where something like react-dom, via webpack, is the expense as opposed to all the marketing / advertising / analytics fetches, bindings and page updates.