Thanks for the info. Is there any benefit to placing these cold fusion scripts off the page like you would for javascripts in a .js file? Is that even possible? Also, would there be any benefit to placing HTML content before these CF scripts on the page? Here are some examples of the CF on the page.

[img]<cfoutput>#appPath#</cfoutput>/common/images/header.gif[/img]<br clear="left">

<cfif isDefined("cookie.memberID") and cgi.script_name does not contain "logout.cfm"><a href="<cfoutput>#linkRegular#</cfoutput>/member_returns.cfm"><cfelse><a href="<cfoutput>#linkRegular#</cfoutput>/support/returns.cfm"></cfif>

<cfif cgi.script_name contains "index.cfm">

<cfapplication sessionmanagement="yes" name="XXXXXXXXXXX" clientstorage="XXXXXXXX" clientmanagement="yes">

<cfset dsn = "XXXXXXXX">
<cfparam name="appVarMemberID" default="0">
<cfset bgcolor_blue = "ADCFEB">
<cfset bgcolor_yellow = "FDF592">

<cfif cgi.script_name contains "checkout.cfm" or cgi.script_name contains "member_reg.cfm" or cgi.script_name contains "member_reg2.cfm" or cgi.script_name contains "billing" or cgi.script_name contains "member_profile.cfm">

<cfset appPath = "https://www.XXXXXXXXXXX.com">
<cfelse>
<cfset appPath = "http://www.XXXXXXXXXXX.com">
</cfif>
<cfset linkssl = "https://www.XXXXXXXXXXX.com">
<cfset linkRegular = "http://www.XXXXXXXXXXX.com">
<cfif cgi.script_name does not contain "cron_">
<cfinclude template="common/includes/header.cfm">
</cfif>