Abstract: A preloader works in conjunction with a web/app server and optionally a profile server to cache web page content elements or components for faster on-demand and anticipatory dynamic web page delivery. The preloader uses a cache manager to manage requests for retrievals, insertions, and removal of web page components in a component cache. The preloader uses a cache replacement manager to manage the replacement of components in the cache. While the cache replacement manager may utilize any cache replacement policy, a particularly effective replacement policy utilizes predictive information to make replacement decisions. Such a policy uses a profile server, which predicts a user's next content request. The components that can be cached are identified by tagging them within the dynamic scripts that generate them. The preloader caches components that are likely to be accessed next, thus improving a web site's scalability.

Abstract: A system and method for delivering a web page can include receiving a web page request corresponding to a web page having cacheable content. In response to the web page request, a script can be executed to produce a template of the web page at run-time. The script can include a code block corresponding to a cacheable content fragment of the web page. A key identifying the cacheable content fragment can be inserted into the template. The template can be sent to a dynamic proxy cache. The dynamic proxy cache can insert the cacheable content fragment identified by the key into the web page. The web page including the cacheable content fragment can then be delivered to a user.