> It's so much worse than that though. It's not for no reason, they actually call this is a best practice. Everyone's browser already has jQuery cached if you load it from jQuery's site, right? So yeah, just load all seventeen of your random javascript things from their original sites. Now your site is fast because all those pages are already in everyone's cache!
Uh, what "best practice" site did that come from? W3Schools? I'm not a web dev anymore, but the best practice recommendation as far as I know has always been to combine and minify assets into as few requests as possible. Unfortunately most of the web still sucks and doesn't do this.
> It's so much worse than that though. It's not for no reason, they actually call this is a best practice. Everyone's browser already has jQuery cached if you load it from jQuery's site, right? So yeah, just load all seventeen of your random javascript things from their original sites. Now your site is fast because all those pages are already in everyone's cache!
Uh, what "best practice" site did that come from? W3Schools? I'm not a web dev anymore, but the best practice recommendation as far as I know has always been to combine and minify assets into as few requests as possible. Unfortunately most of the web still sucks and doesn't do this.