Hi,

The reason you are getting this initial delay is because most shared hosting providers will shutdown your website after a variable delay of inactivity. The host you are using seems quite slow as the initial delay is normally somewhere around 5 seconds. But anyway, no delay is better.

There are 2 solutions:

1) use a keep alive service -- an external host that will periodically issue requests to your website so that it is never inactive and never shut down.

2) use a shared hosting provider that does not shutdown your website when inactive

There is no way to have separate DNN installations sharing memory, unless you have 1 DNN installation and many portals defined in it. But this would mean that you would not have host access, only admin access, limiting  what you can do. Also, you would not have control over the version of DNN you are running as your host would decide when / if to upgrade.

To save memory, you can place many DNN installations in the same application pool. Many hosts choose to run many DNN websites in the same application pool to reduce memory usage. But running many DNN installations in the same apppool reduces the stability of your website (one website can crash the apppool and make your website unavailable). And it also reduces the security of your website, since other websites in the application pool could access your configuration file or use other possible exploits to compromise your site.

Best for your website is a host not trying to save on memory: your website in a dedicated application pool that never shuts down. But you won't find this in any 4.99$ / month package.

I would advise to run a KeepAlive on your current host: http://www.mywebkeepalive.com/