我会用多个选项实际回答这个问题， 。
$ b

• 将库脚本（如jQuery库）放在头部分中。


• 将正常脚本放在首位，除非它成为性能/页面加载问题。


• 将与include关联的脚本放置在include和end内部。其中一个例子是asp.net页面中的.ascx用户控件 - 将脚本放在该标记的末尾。


• 将影响页面呈现的脚本放置在body （在body关闭之前）。
  
• 不要将脚本放在标记中，例如< input onclick =myfunction（）/> - ***将它放入脚本主体中的事件处理程序中。


• 如果您无法做出决定，请将其置于首位，直到您有理由不阻止页面阻止问题。

脚注：当你需要它而不是先前时，适用于页面阻塞（感知加载速度）用户的感觉是真实的，如果它被加载的速度更快，它的加载速度会更快（即使代码中可能还有东西）。编辑：引用：

• 讨论： http://west-wind.com/weblog/posts/154797 .aspx
  和这里： http：// msdn。 microsoft.com/en-us/library/3hc29e2a.aspx


• jQuery文档准备讨论： HTTP：// encosia .COM / 2010/08/18 /不要-LET-jquerys文档准备，慢你关机/ utm_source = Feedburner的&放大器; utm_medium =电子邮件&放大器; utm_campaign =进料％3A + Encosia +％28Encosia％29


• 此问题的其他答案也提供有效信息。 使用www.google.com和www.bing.com搜索相关信息（有很多引用）

注意：如果您将脚本块置于标记内，它可能会影响某些浏览器的布局占据空间（ie7和歌剧9.2已知有这个问题），所以把他们放在一个隐藏的div（使用一个CSS类，如： .hide {display：none;知名度：隐藏;标准：请注意，如果有问题，标准允许在任何地方放置脚本块： http://www.w3.org/TR/1999/REC- html401-19991224 / sgml / dtd.html 和 http：//www.w3 .org / TR / xhtml11 / xhtml11_dtd.html

编辑2：请注意，只要有可能（总是？），您应该将实际的Javascript放入外部文件和参考那些 - 这不会改变相关的序列有效性。

I have seen both ways, both implementation work just the structures are a bit different. In your experience, which work better and why?

I would answer this with multiple options actually, the some of which actually render in the body.

• Place library script such as the jQuery library in the head section.
• Place normal script in the head unless it becomes a performance/page load issue.
• Place script associated with includes, within and at the end of that include. One example of this is .ascx user controls in asp.net pages - place the script at the end of that markup.
• Place script that impacts the render of the page at the end of the body (before the body closure).
• do NOT place script in the markup such as <input onclick="myfunction()"/> - better to put it in event handlers in your script body instead.
• If you cannot decide, put it in the head until you have a reason not to such as page blocking issues.

Footnote: "When you need it and not prior" applies to the last item when page blocking (perceptual loading speed) - the users perception IS thier reality, if it is percieved to load faster, it does load faster (even though stuff might still be occuring in code).

EDIT: references:

• asp.net discussion: http://west-wind.com/weblog/posts/154797.aspx and here: http://msdn.microsoft.com/en-us/library/3hc29e2a.aspx
• jQuery document ready discussion: http://encosia.com/2010/08/18/dont-let-jquerys-document-ready-slow-you-down/?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+Encosia+%28Encosia%29
• the other answers on this question present valid information as well.
• use www.google.com and www.bing.com to search for related information (there are a lot of references)

Side note: IF you place script blocks within markup, it may effect layout in certain browsers by taking up space (ie7 and opera 9.2 are known to have this issue) so place them in a hidden div (use a css class like: .hide { display: none; visibility: hidden; } on the div)

Standards: Note that the standards allow placement of the script blocks virtually anywhere if that is in question: http://www.w3.org/TR/1999/REC-html401-19991224/sgml/dtd.html and http://www.w3.org/TR/xhtml11/xhtml11_dtd.html

EDIT2: Note that whenever possible (always?) you should put the actual Javascript in external files and reference those - this does not change the pertinent sequence validity.