How the ASP speeds up the Web site opening

One trick: increasing the efficiency of using the request collection
Accessing an ASP collection to extract a value is a time-consuming, resource-intensive process. Because this operation contains a series of searches for the related collection, this is much slower than accessing
a local variable. Therefore, if you intend to use a value in the request collection more than once in a page, you should consider storing it as a local variable.
For example, write your code in the following form to speed up script engine processing:
 

 
  
 
 
   
  
strtitle=request.form ("Title")     
 
   
  
 strfirstname= Request.Form ("FirstName")     
 
   
  
strlastname=request.form ("LastName")     
 
   
  
 If len (strtitle)  Then strTitlestrTitle=strTitle &  " "     
 
   
  
if strfirstname= " Then strFullName=strTitle &   "  & strLastName    
 
   
  
 elseif len (strfirstname) =1 then    
 
   
  
strfullname=strtitle & strfirstname &  ". "  &  strlastname    
 
   
  
 else    
 
   
  
strfullname=strtitle &  strfirstname &  " "  & strLastName    
 
   
  
 end if    
 
  
 

Tip Two: Direct access to the appropriate set
Do not use the form of strpage=request ("page") to get the argument if it is not a choice, because it will search all the collections sequentially-
QueryString, Form, Cookies, ClientCertificate, servervarible until the name of the first matching value is found. This is more appropriate than direct access
The collection is inefficient and unsafe unless it is absolutely guaranteed that the value will not appear in another set.
For example, you might want to search for a Web server name that satisfies a customer request, which is found in the Request.servervarables collection in each query
"SERVER_NAME" to achieve. However, if the other collection also contains a value named "SERVER_NAME" (the key name is case-insensitive), use the request
("SERVER_NAME"), you get the wrong result. In summary, you should access the appropriate collection as direct as possible.

Tip Three: Use the Response.IsClientConnected property before a time-consuming operation
Using response.isclientconnected is a useful way to observe whether a user is still connected to the server and is loading the Web page created by ASP. If the user disconnects
Or stop downloading, we don't have to waste the server's resources creating pages because the buffer content will be discarded by IIS. So, for those who need a lot of time to compute or
Resources to use more pages, it is worth checking at each stage whether the visitors are offline:

 
  
 

  
   
  
...... Code to create the page
  
   
  
If response.isclientconnected Then
  
   
  
Response.Flush
  
   
  
Else
  
   
  
Response.End
  
   
  
End If
  
   
  
...... Code to create next part of page