How to Optimize Website Content Delivery Using Whole-Site Acceleration

Consumers are moving their most important transactions online because of their greater confidence in the quality and security of the transactions. Consumers migrate to Websites that are consistently responsive to their wants and needs, so Website performance has a critical impact on users' experience, customer site loyalty and revenue generation. Here, Knowledge Center contributor David Drai explains how content providers and e-tailers can use whole-site acceleration technology to optimize their Website content delivery.

bug_knowledgecenter_70x70_%282%29.jpg

A growing number of Websites are delivering a diverse mix of content that includes static (cacheable), dynamic (non-cacheable) and secure data. This trend, plus the increasing adoption of personalization and new browser presentation technologies, has created a vast, unmet need for whole-site delivery that is both unified and adaptable.

Content providers and e-tailers alike have come to understand that the traditional content delivery network (CDN) model is ill-equipped to globally and strategically accelerate content delivery. Content providers and e-tailers also recognize that their Website performance has a critical and tangible impact on their users' experience, customer site loyalty and revenue generation. Whole-site acceleration promises to be an ideal solution to optimize all communications between the origin server and the user. However, there is still some confusion about what constitutes whole-site acceleration.

Traditional CDN model is highly fragmented

Basic CDNs have proven effective at pushing large volumes of static content at scale over a distributed network. Some content providers utilize secondary CDNs to optimize delivery of video. Others are constrained from delivering static content over a CDN because they have Secure Sockets Layer (SSL) content that cannot be split between providers, as the routing decision is done on the Domain Name System (DNS) level when it is still not known if the required content is HTTP or HTTP Secure (HTTPS). Content providers have limited options for acceleration of dynamic, non-cacheable content.