After installing all in one in Windows have found out that access speed is slower than online. Debug shown that access even for single picture to get 304 Not Modified answer takes 0.6 seconds from localhost. 99% of this time is connection (data not even started sending at all).

(sorry, not enough karma to post links or pictures, so remove space in link)

Changing to IP address 127.0.0.1 it improves 5-10 times. But still as you can see lower - pictures taking 65ms just to connect.

I suspect there is no keep-alive connections (even at online demo I see large delays) and something wrong with access by host. Any help in explanation would be great, since large delays in each connect are making things painfully slow - to show single page there are 5 subsequent requests which add time one to another.

I think it is also worth mentioning that sometimes, the sequence of requests are not smooth/continuous. The "loading.." status animation would lock the webpage, would unlock for some millisecond, then would lock surprisingly lock again.

I cant access your links. Error 403 by google (Forbidden). Anyway, I checked using Chrome Developer tools and I saw that even often reused images such as my user profile pic & search_reset.gif are not cached. I also don't understand why my profile pic was requested 3+ secs later after authentication

Not enough karma to upload pictures and can't share pictures from gdrive like before. Anyway - there are something wrong 300-600ms of connection on everything becomes 2 seconds for showing demo suppliers on localhost. Keep-alive, no cache issues are something that also makes it work slower 20 times

try putting the host name in your local hosts file which is in /etc/hosts or I think c:\windows\system32\etc\hosts (might be somewhere else by now on Windows, hopefully that is enough of a clue to find it)
This will take your DNS resolver out of the equation to test the performance. If that is the problem then maybe you are using a slow DNS server or are doing a query in a remote DNS before failing over to a local DNS query. Maybe using something like wireshark (I think that might run on Windows, but there are other packet analysis tools for windows) will allow you to trace the DNS packets.

localhost domain resolves 10000 faster than those delays. So it's not a problem at all. I have other http service on same localhost machine that replies in 0.05ms until finish of answer comparing to 600ms to get 304 Not Modified from OE. It's solvable by IP, but still - 60ms to answer 304?!