The Most Misleading Measure of Response Time

Download CDN Balancing the Whitepaper

Share a few contact details and we’ll send a download link to your inbox.

First Name

Last Name

Work Email

Company

otm_Source:

otm_Medium:

otm_Campaign:

utm_Medium:

utm_Campaign:

utm_Source:

Lead Source:

Lead Source Category:

Lead Source Subcategory:

Industry:

Annual Revenue:

Num Employees:

Audience (db):

Audience Segment (db):

B2B:

B2C:

City (db):

Company (db):

Company Phone (db):

Country (db):

Country Code:

Demandbase ID:

Forbes 2000:

Fortune 1000:

Postal Code (db):

Primary NAICS Code:

State (db):

Street (db):

Website (db):

demandbase_production_live:

Ultimate_Parent_Name:

Latitude (L):

Longitude (L):

Marketing Alias:

Subindustry:

Web Conversion Type:

Web Conversion URL:

Job Level

Job Function

Job Title

Learn how Optimizely dramatically improved response times with CDN balancing. According to Compuware’s 2013 Application Performance Trends Report, “a one-second delay in website response time equals 11% fewer page views, 16% decrease in customer satisfaction and a 7% loss in conversions.”

This whitepaper explores:

The various ways businesses can measure response times for the client-side, third party code they host on their websites
Why looking at average response time paints a distorted picture of the actual amount of time it takes to load a page
How Optimizely improved the response times of its variation code by 40% globally and by more than 160% in North America.