YSlow (determine why web pages are slow to load).Wireshark (sniff traffic and inspect the lot across various protocols).WinMerge (compare and merge files and directories).The Regulator (edit and test regular expressions).SysInternals (Inspect everything Windows with Filemon, Regmon, PsTools).Page Saver (save an entire web page as an image).

NET Resourcer (inspect and edit resource files)

Firefox Web Developer Toolbar (inspect and dynamically modify web pages).

Firefox User Agent Switcher (change your browser user agent string).

Firefox Modify Headers (change your IP address, among other things).

Firefox Live HTTP Headers (view HTTP headers).

Firebug (inspect and modify web pages, debug Javascript, view network stats).

Fiddler (a reverse HTTP proxy, inspect headers, view traffic).

IEDevToolbar (like FF's Web Developer toolbar for IE).

I have read a lot about that problem - the keep alive problem is excluded (I also disabled the options in Fiddler) Firebug marks it as 'waiting time' without more info, when Fiddler is unactive. That is really awesome, but I don't think, I can convince my customers to install Fiddler :-)) I can wait 2 minutes and load a new page, and I get the same results. Now when I start Fiddler, the first page load after that is around 20-40ms more than page generation time and all next loads as fast as the first - not much more than 300ms.

Page generation time is mostly around 200ms. This does not really depends on a keep alive or a new connection. (PHP / Yii Framework) When I load a page, there are access times around 550ms - 2,5s. I am a little bit stucked with my problem, so maybe I've missed something.Ī project, i am currently working on - running 'locally' in a VirtualBox, bridged network. First of all, thanks a lot for this great advantage piece of software :-)

Fiddler vs wireshark vs firebug