Why is Netscape slow in IIS 5.0?

A minor change introduced with IIS 5.0 may, in obscure situations, cause Netscape to render a page a bit slowly (though never by a minute, which I believe was an exaggeration by one individual). However, Microsoft did not to do this to thwart Netscape. All they did was change the response.buffer default property to "TRUE" (it was "FALSE" in IIS 4.0). 
 
When response.buffer is set to TRUE, the entire page is processed and stored in a "buffer" -- not being sent to the client until the entire page is processed. When response.buffer is set to FALSE, the page is "streamed" to the client as it is processed - so you will some lines of text, then the server will churn out some more lines and they will appear, and so on until the page is finished.  
 
So, if you are having this problem, try setting the following at the top of the page (you can also uncheck "Enable buffering" in the configuration/app options tab of any application, or the default web site, in Internet Services Manager): 
 

<%      Response.Buffer = False  %>

 
In addition to the above solution, Peter Krantz tells us the following: 

If you are running Windows 2000 you can easily fix this by bringing up the task manager, selecting the Process tab, right-clicking the netscape.exe image and setting the priority to Low which means that the IIS will be prioritized over netscape to process the form.

Remember that, in either case, Netscape is always going to have problems with HTML rendering, particularly with complex tables and CSS. This is just a fact of the Internet: Netscape has a terrible rendering engine (which makes it a GREAT test browser). I have found that, the more complex the page, the longer Netscape will take to load it... and this is independent of web server settings, web server software, and even platform.