<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/24/2013 08:29 AM, leam hall
wrote:<br>
</div>
<blockquote
cite="mid:CACv9p5rrRMzkEOdxdxnLvzQHMnpysSoa9u831AL8b3Pr3jNGJA@mail.gmail.com"
type="cite">Any supporting ideas for pushing the argument of "Use
lots of small scripts for a big task, instead of one large one"?</blockquote>
<br>
When developing, always do that.<br>
<br>
In production, however, you should use something like the Closure
compiler from Google to take all of your JS code and minify and
concatenate it into a single script. This significantly speeds up
load time, as each request required which is greater than the
browser's connection limit will kill page load times.<br>
<br>
For site chrome (image files that are presentation, not content),
the same strategy should be used: all images should be placed into
a single large image and CSS used to render the fragments
("sprites") at the appropriate times and places.<br>
<br>
I'd also recommending merging CSS together where sensible.<br>
<br>
Obviously, on some pages you'll have multiple script src tags (e.g.,
google analytics or piwik, or functionality which is contained to a
single page/frame). But as for the general rule, the production
code should be minified and delivered in a single file when
possible.<br>
<br>
Just my 2¢,<br>
Mike<br>
<br>
<div class="moz-signature">-- <br>
<table border="0">
<tbody>
<tr>
<td> <img src="cid:part1.00000100.08020603@naunetcorp.com"
alt="Naunet Corporation Logo"> </td>
<td> Michael B. Trausch<br>
<br>
President, <strong>Naunet Corporation</strong><br>
☎ (678) 287-0693 x130 or (888) 494-5810 x130<br>
<br>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>