Hacker News Reader

Google in their Page Speed ranking consider 100kb == 100ms.

See: https://code.google.com/speed/page-speed/docs/mobile.html#De...

BTW, their Page Speed thing is now available online: https://developers.google.com/pagespeed/

I wonder if there is any better optimization that browsers can do for this (like at least cache the AST if the exact same JS is loaded).

Parent talks about parsing speed.

So does Google.

Interesting. Is parse time generally a function of code length, or overall complexity/CPU time?

(I'm not an expert) but it's more than simply code length - it also depends on if the library runs any functions at parse time, and perhaps also how many variables it puts in the global space.

For example: I discovered that my tiny localStorage library was taking 300ms to load, and that was because I was doing feature detection at parse-time and that feature detection attempted to actually set an item in localStorage. I postponed that, and got the load time down to 20ms.

Do you mind sharing what are you using/doing to benchmark that? cheers