IE7 Javascript 文件加载 - 优化
我目前正在对一个大型网络项目进行一些优化工作。我已经在进行 JavaScript 文件合并、缩小和压缩。但我对一点感到困惑。
由于一些非技术原因，我的用户中 IE7 和 IE8 各占 50% 左右。经过一些研究后，我得到的印象是 IE7 顺序加载 JavaScript 文件，而 IE8 并行加载它们。我知道，对于更现代的浏览器（IE9+、FF、Chrome 等）来说，这将不再是问题。
这是一个准确的说法吗？如果是，那么加载文件的最佳实践是什么？
I'm currently doing some optimization work on a large web project. I'm already doing JavaScript file combining, minification and compression. But I'm confused on one point.
For a number of non-technical reasons, my users are about 50% each IE7 and IE8. After doing some research, I'm getting the impression that IE7 loads the JavaScript files sequentially and IE8 loads them in parallel. I understand that going forward that this will not be an issue with more modern browsers (IE9+, FF, Chrome, etc).
Is this an accurate statement? If yes, then what is best practice for loading the files?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
该说法是正确的，但您应该记住，即使是现代浏览器也只能与同一服务器建立有限数量的连接。因此，当您的页面、脚本、CSS 和图像都位于同一服务器上时，浏览器一次可能只加载其中的 2 或 4 个。因此，为脚本添加子域或不同的域来欺骗浏览器并使其与图像一起加载脚本可能是一个好主意。
一种更简单的解决方案是将所有脚本合并为一个脚本。您可以“即时”执行此操作或将其缓存。您甚至可以最小化脚本（这意味着注释和空格被删除，变量名称被缩短）。您不应该最小化和组合原始脚本，但您可以缓存组合/最小化的脚本，这样就不需要在每个请求时最小化它们。
如果这样做，就可以减少流量，并且浏览器只需要一次对该文件的请求，从而消除了多个连续请求的开销。
请参阅这篇 MSDN 博客文章 显示了脚本加载的一些其他技巧。
That statement is correct, but you should remember that even modern browser will make only a limited number of connections to the same server. So when your page, scripts, css and images are all on the same server, the browser may load only 2 or 4 of those at a time. Therefor it may be a good idea to add a subdomain or a different domain for scripts to trick the browser and make it load the scripts alongside with the images.
An even simpler solution is to merge all scripts into one script. You can do this 'on the fly' or cache it. You can even minimize the scripts (which means comments and whitespace are stripped and variable names are shortened). You shouldn't minimize and combine the original scripts, but you can cache the combined/minimized scripts so they won't need to be minimized with each request.
If you do this, you reduce traffic, and your browser will only need one request for the file, eliminating the overhead of multiple sequential requests.
See this MSDN blog article which shows some other tricks for script loading.