Webpage is Slow to Open

 This article is suitable for an IT Adminstrator

Ref: 201302201603
Last Edited: February 20th, 2013


A webpage in a Triaster process library is slow to open. It may open significantly quicker on subsequent occasions.

The webpage is likely to be an ASPX page, with an address such as:
http://MyHost/Triaster%20Browser%20Toolkit%202011/Menu/frames.aspx?tool=home&library=triaster sample library&site=live


In Triaster Server 2011, the assemblies associated with the ASP.NET v2.0 applications which serve these webpages are digitally-signed with an Authenticode signature identifying Triaster as the publisher. When such an assembly is invoked, the system will try to verify the certificate over the Internet, checking that the certificate hasn't been revoked against a Certificate Revocation List (CRL). That can delay the opening of a webpage, especially if the server doesn't have Internet access.


One of these workarounds should suffice.

Disabling the certificate check

Signature verification can be disabled by this configuration in the Aspnet.config file on a computer:

<?xml version="1.0" encoding="utf-8"?>
        <generatePublisherEvidence enabled="false"/>

The Aspnet.config file may be found in:


on a 32- or 64-bit version of Windows respectively.

Configure the application pool Idle Time-out

By setting the application pool Idle Time-out to zero, the worker process that runs the application won't shut down when not required to process requests. The first time an associated page is opened may be slow, but subsequent opening should be quicker, and remain so.

This assumes IIS 7.x:
  1. Open Internet Information Services (IIS) Manager.
  2. In the left-hand pane, expand '<Computer Name> (<User>)'.
  3. Click 'Application Pools'.
  4. In the middle pane, right-click the relevant application pool > 'Advanced Settings...'.
  5. In 'Advanced Settings', under 'Process Model', set 'Idle Time-out (minutes)' to 0.
  6. Click OK to close the dialog.

More Information:

Best Practice - <GeneratePublisherEvidence> in ASPNET.CONFIG

Where should I set generatePublisherEvidence to false in an asp.net app?

Should I Authenticode sign my .NET assembly?

FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start

Need further help? Contact the Triaster Support team by e-mailing support@triaster.co.uk or by calling us on + 44 (0)870 402 1234.
Do you have any feedback or suggestions that you would like to share with Triaster? We would love to hear from you! Please e-mail feedback@triaster.co.uk