blocks|key|1357689|text|我不确定只为一个供应商进行优化是不是一个有用的努力：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1357690|1357691|关于HTML，大多数浏览器都是为标准布局技术(表格，无表格等)而编写的。|unordered-list-item|1357692|渲染引擎在IE6和IE8之间有很大的不同，所以这就像两个不同的浏览器|1357693|大多数优化技术都是跨浏览器的标准(将javascript放在底部，这样你就不会阻止页面加载，将javascript移动到外部文件，使用多个图像主机名等)|1357694|为了利用并行加载的优势，不要使用表格进行整体布局，确保缓存头是正确的，等等。我会争辩说，对于IE来说，几乎没有更多的东西可以获得；|1357695|如果你真正关心的是优化IE的Javascript代码，那么有许多好的跨浏览器的Javascript库在为浏览器平台的最佳执行时间进行角逐，因此，再一次，选择一个跨浏览器的解决方案是|1357696|浏览器环境不断发展的方向，你的客户可能会在未来的某个时刻转移到另一个平台上；现在针对几种不同的浏览器进行优化将最终得到更兼容的代码，这些代码在未来某个时候进行平台更改时更有可能表现良好|1357697|我认为，编写跨浏览器优化的代码将导致更易维护的代码库，减少神奇的IE黑客攻击，它们存在的理由很快就会消失在time|1357698|的迷雾中|1357699|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|11|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|12|8|@]|9|@]|A|$]]|$1|P|3|Q|5|E|7|13|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|14|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|U|$]]

I am not sure it is a useful endeavor to optimize for only one vendor:

<ul>
<li>regarding HTML, most browsers are written to optimize for standard layout techniques (tables, table-less, etc.) </li>
<li>the rendering engines are quite
different between IE6 and IE8, so
already that is like two different
browsers </li>
<li>most of the techniques for optimizing
are standard across browsers (put
javascript at bottom so you don't
block page loads, move javascript to
external file, use multiple hostnames
for images etc. to take advantage of
parallel loading, don't use tables
for overall layout, make sure caching
headers are correct, etc.) </li>
<li>once you have a site optimized for Firefox, I would argue there is little more to be gained as far as tweaking it for IE; there is probably more you can do at the application level at this point (optimize queries, etc.), unless your site is largely static content, in which case you can investigate caching, HTTP compression, etc. </li>
<li>if your concern is actually in optimizing Javascript code for IE, then there are many good cross-browser Javascript libraries that are in an arms-race for best execution times across browser platforms, so again, picking a cross-browser solution is the way to go </li>
<li>the browser landscape is constantly evolving, and your customers are likely to move on to another platform at some point down the road; optimizing for several different browsers now will end up with more compatible code that is more likely to perform well when a platform change is made at some point in the future </li>
<li>I would argue that writing cross-browser optimized code will result in a more maintainable code base with fewer magic IE hacks, whose reason for existence will soon be lost in the mists of time</li>
</ul>

blocks|key|1358406|text|我不会假装知道绝对的答案。但有一种方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1358407|1358408|使用诸如wget之类的工具来测量获取页面的时间|unordered-list-item|1358409|使用诸如firebug之类的工具来测量总体时间为浏览器|1358410|提供时间|1358411|虽然这可能不是一个完全令人满意的答案，但我会观察到这是最简单的。|1358412|顺便问一下，您认为使用“浏览器级别测试”可以突出哪些性能方面，而使用"firebug级别测试“则无法突出这些性能方面？|1358413|干杯,|1358414|jrh|1358415|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

I don't pretend to know the absolute answer. But one method would be:

<ul>
<li>use tools like wget to measure time in which a page is fetched</li>
<li>use tools like firebug to measure overall speed</li>
<li>difference gives you time taken by the browser</li>
</ul>

While this may not be a completely satisfactory answer, I will observe that this is the easiest.

By the way, what do you think are the performance aspects that you can highlight using a "browser level test" that you can't with a "firebug level test"?

Cheers,

jrh

blocks|key|56727|text|在文档的开头和末尾放置一个脚本块，并设置window.onload。通过Number(new+Date)获取每个“序列点”的当前时间戳，您可以获得页面需要以浏览器无关的方式呈现多长时间的第一印象。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|56728|entityMap^0|K|D|10|G|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Put a script block at the beginning of the document, at its end and set <code>window.onload</code>. Grab the current timestamp via <code>Number(new Date)</code> at each of these 'sequence points' and you can get a first impression of how long the page needs to render in a browser-agnostic way.

blocks|key|988749|text|您可以使用IE+high+performance+tester。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|988750|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codeplex.com/IEJst^0|8|N|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You can use the IE <a href="http://www.codeplex.com/IEJst" rel="nofollow noreferrer">high performance tester</a>.

blocks|key|988765|text|你可以获得Firebug+for+IE+(以及Opera和Safari)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|988766|http://getfirebug.com/lite.html|offset|length|988767|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|V|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

You can get Firebug for IE (and Opera and Safari):

<a href="http://getfirebug.com/lite.html" rel="nofollow noreferrer">http://getfirebug.com/lite.html</a>

blocks|key|988794|text|我真的很喜欢AOL's+PageTest工具，它结合了Firebug、YSlow和PageTest中的许多实用工具，并将其包装在一个具有一些好功能的漂亮的web界面中。首先，它可以在来自美国或国际的IE7或IE8+(no+6，抱歉)上运行，让你对那里的性能有更好的了解。它提供了类似于Firebug网络面板中的瀑布图，这对于确定时间被花在哪里很有用。它还提供了与YSlow中的建议类似的修复建议。最后，它允许您在同一站点上运行多个试验，以便您可以在最小化外部因素的同时获得更准确的结果。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|988795|在很大程度上，我同意OrbMan的观点，即针对所有浏览器进行优化是很重要的。由于这些优化是跨浏览器的，因此您将在性能方面获得最大收益。只有到了那时，才是时候开始考虑特定于浏览器的改进了。|988796|有一堆Google+Tech在线演讲都在谈论如何提高web性能。This+blog+post包含与此主题最相关的谈话列表。|988797|entityMap|0|LINK|mutability|MUTABLE|url|http://www.webpagetest.org/test|1|http://juixe.com/techknow/index.php/2009/05/05/top-javascript-and-web-performance-presentations-on-google-tech-talks/^0|6|E|0|0|0|W|E|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

I really like <a href="http://www.webpagetest.org/test" rel="nofollow noreferrer">AOL's PageTest</a> tool, it combines a lot of the utility found in Firebug, YSlow, and PageTest and wraps it up in a nice web interface with a few nice features. First, it can be run on IE7 or IE8 (no 6, sorry) from the US or international locations to give you a better idea of performance there. It provides waterfall charts like those in the Firebug net panel which are useful for determining where time is spent. It also provides recommendations for what to fix which are similar to those in YSlow. Finally, it allows you to run multiple trials on the same site so that you can get more accurate results while minimizing the external factors. 

For the most part I would agree with OrbMan in that it is important to optimize for all browsers. Since those optimizations are cross-browser you will get the most bang for you buck in terms of performance. Only then is it time to start considering browser-specific improvements. 

There are a bunch of Google Tech Talks online which talk about improving web performance. <a href="http://juixe.com/techknow/index.php/2009/05/05/top-javascript-and-web-performance-presentations-on-google-tech-talks/" rel="nofollow noreferrer">This blog post</a> contains a list of the talks which are most relevant to this topic.

blocks|key|4207241|text|WebWait可以在任何浏览器中运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4207242|这是你的web性能实用工具带上的另一个工具。|4207243|entityMap|0|LINK|mutability|MUTABLE|url|http://webwait.com/^0|0|7|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

<a href="http://webwait.com/" rel="nofollow noreferrer">WebWait</a> works in any browser.

It's yet another tool to have in your web performance utility belt.

I know everyone who reads the question will think "Firebug!" right away. Maybe some will think "YSlow!" and "Google Page Speed!"

While I really like these tools, I'm more concerned with how the quickly the page will render in IE 6/7/8. All of the above tools require Firefox. That's all fine and you can definitely test the underlying speed of getting the page to the browser but what about when it comes to actually rendering the page?

I haven't seen any really good answers on how to test optimization at the browser level. How do you write performance tests for HTML/JS across difference browsers?

How do you do page performance tests?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我知道每个读过这个问题的人都会想到"Firebug!“马上就来。也许有些人会想"YSlow!“和"Google Page Speed!“虽然我真的很喜欢这些工具，但我更关心的是页面在IE 6/7/8中渲染的速度。所有上述工具都需要Firefox。这一切都很好，而且您肯定可以测试将页面发送到浏览器的底层速度，但是当实际呈...

问如何进行页面性能测试？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何进行页面性能测试？EN