301 Redirect in classic ASP

<%
Response.Status = "301 Moved Permanently"
Response.AddHeader "Location", "http://www.website.com/"
Response.End
%>


Above code is enough for Redirection but its better put a link because you never know a user might have turned off auto redirection

<table>
    <tr>
        <td align="center" width="100%">
            <h1>The page you are looking for has moved...</h1>
            We have recently updated our site and the page you are looking for has moved.
            Click <a href="http://www.website.com/">here</a> to continue
        </td>
    </tr>
</table>

Why ASP.NET appears to be faster than Classic ASP?

 Pages with the .aspx extension use compiled ASP.NET (based on Microsoft's .NET Framework), which makes them faster and more robust than server-side scripting in ASP, which is interpreted at run-time; however, ASP.NET pages may still include some ASP scripting

Reference: http://en.wikipedia.org/wiki/Active_Server_Pages

Classic ASP Built-in Objects

ASP 2.0 provided six built-in objects: Application, ASPError, Request, Response, Server, and Session. Session, for example, represents a cookie-based session that maintains the state of variables from page to page. The Active Scripting engine's support of the Component Object Model (COM) enables ASP Websites to access functionality in compiled libraries such as DLLs.

Reference: http://en.wikipedia.org/wiki/Active_Server_Pages