3 ms·
I get about ~7ms in chrome on a mbp and ~200ms on my shitty nexus s. http://danheberden.com/tools/howlongtoloadjquery.htm http://danheberden.com/tools/howlongto
by danheberden 13y ago
I get about ~7ms in chrome on a mbp and ~200ms on my shitty nexus s. http://danheberden.com/tools/howlongtoloadjquery.htm http://danheberden.com/tools/howlongtoloadjquery.htm
- nostrademons 13y ago74ms for initial load and averaging about 20ms subsequent loads on a MBP with Chrome. Ubuntu Chrome is similar. 837ms initial load, average about 140 ms subsequent loads on a Moto X on T-Mobile.
- danheberden 13y agoI thought we were taking download time out of this
- nostrademons 13y agoThe "subsequent load" time should be pretty close to this. I'm getting about 20-30ms of "Evaluate script" time when I run a profile in Chrome's Timeline tool.
- bentlegen 13y agoCool. A few comments: * You're loading the unminified version. * You're factoring the network request time into the benchmark. I was interested in pure parse time. Which was 27ms according to Chrome Developer Tools: http://i.imgur.com/hgFiGTu.png http://i.imgur.com/hgFiGTu.png (the score on the page was 110ms). I'm curious what people who complain about "parse time" consider to be an acceptable score. Edit: Ah, I didn't realize you were discarding the network time. I was fixated on the number spat out by the page.