Javascript |
For a list of all requirements and guidelines pertaining to posting a new Help topic, please click here.
This Month's Contests | Staff Member of the Month | Hosts Looking for Hostees | Hostees looking for Hosts | BigBookofResources
Submission Guidelines
Javascript |
Feb 15 2011, 01:26 AM
Post
#1
|
|
Sex, Blood, & RocknRoll Group: People Staff Posts: 5,305 Joined: Nov 2007 Member No: 596,480 |
Is it better to have one big JS file or to link to them separately?
|
|
|
Feb 15 2011, 05:09 PM
Post
#2
|
|
Senior Member Group: Official Designer Posts: 5,880 Joined: Nov 2007 Member No: 593,382 |
One big file. Fewer http requests but the difference is so small it's not worth it because you lose the organization. Also look at this this:
http://rakaz.nl/2006/12/make-your-pages-lo...-css-files.html You'd have to weight the pros and cons though because it reduces size therefore making it load faster but it also add pressure on the server which may end up making it slower. (It probably won't unless you have a really crappy server with a heavy load already.) Lastly, read this. Every web design should read through it. http://developer.yahoo.com/performance/rules.html |
|
|
Feb 16 2011, 02:58 PM
Post
#3
|
|
/人◕‿‿◕人\ Group: Official Member Posts: 8,283 Joined: Dec 2007 Member No: 602,927 |
One big file. Fewer http requests but the difference is so small it's not worth it because you lose the organization. Also look at this this: http://rakaz.nl/2006/12/make-your-pages-lo...-css-files.html You'd have to weight the pros and cons though because it reduces size therefore making it load faster but it also add pressure on the server which may end up making it slower. (It probably won't unless you have a really crappy server with a heavy load already.) Lastly, read this. Every web design should read through it. http://developer.yahoo.com/performance/rules.html the way I figure I figure one big file is better for smaller sites but if you've got a lot of things going on but only need a few things on the home page, one or two more on the buy page, only one thing on a comments page, etc. then it's better to go with several smaller js files. say someone wants to browse your site for something but never goes to the checkout or comments sections it doesn't make sense to send them all that code anyway. since js files are cached anyway, it's not like the handful who actually use everything will be making all that many http requests from 10 or 12 extra files |
|
|