I am considering performance suggestions that many pages have about asp.net about. In particular, remove the unused portion of httpmodules:
<httpModules>
<add name="OutputCache" type="System.Web.Caching.OutputCacheModule"/>
<add name="Session" type="System.Web.SessionState.SessionStateModule"/>
<add name="WindowsAuthentication" type="System.Web.Security.WindowsAuthenticationModule"/>
<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule"/>
<add name="PassportAuthentication" type="System.Web.Security.PassportAuthenticationModule"/>
<add name="RoleManager" type="System.Web.Security.RoleManagerModule"/>
<add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule"/>
<add name="FileAuthorization" type="System.Web.Security.FileAuthorizationModule"/>
<add name="AnonymousIdentification" type="System.Web.Security.AnonymousIdentificationModule"/>
<add name="Profile" type="System.Web.Profile.ProfileModule"/>
<add name="ErrorHandlerModule" type="System.Web.Mobile.ErrorHandlerModule, System.Web.Mobile, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
<add name="ServiceModel" type="System.ServiceModel.Activation.HttpModule, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
</httpModules>
There are tons of HTTP modules here, and I'm sure that not all of them are used by your application. Removing an unused HTTP module can definitely give a slight increase in performance, as there will be less work to do. Assume that the application does not require Windows authentication. To remove the inherited parameter, in the httpModules section of the web.config application, add the remove element and specify the name of the module that is not required. Example:
<httpModules>
<remove name="WindowsAuthentication" />
</httpModules>
Does anyone know where there is a description of what everyone does, some are obvious, but not all, I've tried google for a long time.