I've got a page that couldn't be more simple:
<%@ Page Trace="true" %>
<html>
<head></head>
<body>
<h1>Hello World</h1>
<a href="/OtherPage.aspx"/>Other Page</a>
<p><%=DateTime.Now.ToString()%>
</body>
</html>
… but it takes forever to load. There is no database or web service call to slow it down. The trace command reveals that the time from Begin PreInot to End Render is .000049 seconds, but the page itself takes several seconds to load. It is a new web site I just created for this test, and just has a web.config & two test files. The only thing in the web.config is access control:
<authorization><allow users="domain\me" /><deny users = "*"/></authorization>
What else could IIS be doing with all of that time?
Best Answer
Time to turn on Failed IIS Request Tracing!
I realise that the request is actually not failing, but you should be able to set Status 200 on the trace to track successful requests as well. There is a tutorial on iis.net that tells you to use failed request tracing for tracing successful requests, so I assume it should work.