From a discussion with @deoxxa and @yoshuawuyts: is there any hard data on JS size impacting page load time (via CPU) across devices?
-
-
I believe you can see the parse time in the inspector. It is extremely negligible compared to network.
2 replies 0 retweets 0 likes -
What I'm getting at: everybody says "you should keep your JS/CSS small". Apart from network, no reason why.
1 reply 0 retweets 0 likes -
I think there are a number of different things to consider. small in relation to what?
2 replies 0 retweets 0 likes -
Replying to @KoryNunn @mipearson and
A massive application is going to be 'large' but might be developed in a 'light' way
1 reply 0 retweets 0 likes -
Replying to @KoryNunn @mipearson and
where as a 'small' 100kbs is actually huge if all you want to do is scroll to a button on the page.
1 reply 0 retweets 0 likes -
what if you’re scrolling a page full of 6MB PNG images?
2 replies 0 retweets 1 like -
We're talking JS weight here alone I assume. Assets not included.
1 reply 0 retweets 0 likes -
JS & CSS. I'm also interested in CSS parsing speed, for similar reasons.
2 replies 0 retweets 0 likes
hah, from folks that have run benches I've heard that IE6 compatible CSS is probs what you want to be using @KoryNunn @deoxxa
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.