Opera 9 … something is happening … oops, doesn’t show anything one more time …

Sorry guys but what kind of browser I should use to see this interesting application ?

a) Speeds on the local network aren’t very useful to a large number of web developers. The fact that this site uses a normal ADSL connection (as opposed to being on my LAN or using my ultra-high speed work connection) is very appealing to me.

b) The detailed information is useless to most web developers. I don’t care about what headers are being sent or what method is being used. Tamper Data also doesn’t have a visual interface to let you SEE how long it takes to load items. It also uses your browsers cache so you have to do a full refresh if you want accurate first-page-load results.

Conceptually is quite the same, but with 2 adventadges:

a) Speed calculated from the site to your machine (wherever it is), so you can evaluate speeds in different contexts (for example, different ISPs).
b) Much more detailed information.

網頁 Page 中, 到底哪個地方是讓頁面卡住的, 會造成使用者頁面出不來, 或速度特別慢的, 此分析器一掃就很清楚囉~ :)
頁面分析器: OctaGate SiteTimer
詳細介紹說明(原文): OctaGate SiteTimer: Time your pa…

Josh; I exclusively use Firefox and for me SiteTimer has worked very well with both FF 1.5 and FF 2.0. If there’s an error message, I’d very much like to know what it is.
Mortimer; could you send me the error message that appears?
Jacob; our download method has been hand coded using a reg-ex expression that separates out page items that should also be downloaded, if we’ve omitting any items, I’d very much like to know which, an example page would be great!
Gideon; the reason you’re getting so varied results is that the server is fairly heavily loaded due to the Ajaxian impact. All requests travel to an ADSL server, and then the pages are downloaded from that account and the results are reported back. As the ADSL line gets saturated, the page download process will be slowed down also.
Ryan Breen; Processing CSS is something we’ll definitely add, but as for processing JavaScript, that would require a totally different approach. Without actually executing the JavaScript, it’s impossible to know what items will actually be executed as part of a page load. Thus, timing AJAX pages will be very difficult.
Now, we could use IE (for instance, there are probably better browsers out there…) as a download agent, and hook into the IE item download events – that would allow us to process AJAX pages. But it would also mean that our server would quickly fill up with every IE virus known to man…

Alex

(Still a cool tool though..)