content delivery summit 2012: marrying cdns with feo for maximum acceleration

7/31/2019 Content Delivery Summit 2012: Marrying CDNs with FEO for maximum acceleration

1/31

2012 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 1

Marrying CDNs with Front-End Optimizationfor Maximum Acceleration

Joshua Bixby

2012 Content Delivery Summit


2/31


3/31


Speed = Value

250ms is close tothe magic numbernow for competitive

advantage on theWeb.

Harry Shum, Microsoft

INCREASED REVENUES

n 10% increase in revenue(for every 1s of improvement)

n 12% increase in revenue(by improving page load speedfrom 6s to 1.2s)

n 5% increase in revenue(for every 2s of improvement)

n 50% more page views for

fastest visitors(relative to slowest)

n 9% more traffic(for every 400 ms ofimprovement)

INCREASED PRODUCTIVITY

n 2% increase in productivity

n 100% increase in productivity(when application sped up by2.7s)

n Fewer errors, a fasterengineering cycle & enhanced

data integrity

n 25% increase in productivity


4/31


Brief history of time saving

1993 20021999 20062000 200719961995 1998 20042003 20092008 2010 2011

Infrastructure Delivery Transformation


5/31


Delivery vs Transformation

Original Delivery Transformation (FEO)

9.5 seconds63 roundtrips




6/31


Case study: FEO in action


7/31


Before: Performance summary


8/31


WaterfallFirst View Repeat View


9/31


Before: Performance snapshot


10/31


Step 1: Turn on compression and keep alives

~17.8 sec ~10.5 sec


11/31


How did we do?

Original

+KA+Comp

First View

52% 34%40%

Improvement


12/31


Step 2: Implement a CDN

Problem: Time to first byte


13/31


Before and after

~10.5 sec ~8.3 sec


14/31


TTFB savings

Per object TTFB savingsof ~50%


15/31


Before and after CDN: Video

http://youtu.be/BR5hO5rL8lE
http://youtu.be/BR5hO5rL8lEhttp://youtu.be/BR5hO5rL8lE


16/31


We can do better

Still too many roundtrips

Not fast enough!

Still too many bytes


17/31


Step 3: Adding FEO

Reduce roundtripsCombine images

Combine JavaScript

Combine CSS

Re-order requests

Reduce payload even more

Minify CSS and JavaScriptAdd image compression

Increase concurrency

Add a couple of domains to the mix


18/31


How did we do?

+CDN

+FEO

First View 19% 54%Improvement

0.5 sec 4.6 sec

45%

Seconds Gained

81

11


19/31


Before and after: The final, fastest version

http://youtu.be/IPn0T1UacIA
http://youtu.be/IPn0T1UacIAhttp://youtu.be/IPn0T1UacIA


20/31


The proof is in the numbers


21/31



22/31


Theres no single magic bullet for making pages faster.

Adding FEOto CDN/DSAresulted in

~45% fasterpage loadacross allbrowsers


23/31


FEO in the CDN


24/31


FEO lineage

Real-time FEO

One page at a timeNo offline process

(e.g., Pagespeed, Aptimize)

Real-time FEO with advanced learning

Offline learning engine to enhance the real-time engine

(e.g., Strangeloop, Blaze.io)


25/31


FEO in the CDN


26/31


FEO in the CDN


27/31


Key areas of integration


28/31


Measurement

This IS NOT whereyour user is. STOPtesting from here!


29/31


Mobile


30/31


High growth

FEO-accelerated sites are 30-50% faster.

5 of top 10 internet retailers have an automatedFEO strategy and plan to implement it in 2012.

CDNs are increasing their MRR with customersby 40-50% on top of existing acceleration solutionslike DSA.

200+ top sites have been running automated FEOfor 2+ years.

Significant innovation in mobile and desktopacceleration is coming in 2012.

Rapid adoption

Speed

Stability

High margin

Rapid innovation


31/31

2012 Strangeloop Networks Strangeloop Faster Websites Automatically 31 2011 Strangeloop Networks Strangeloop Faster Websites Automatically 31

content delivery summit 2012: marrying cdns with feo for maximum acceleration

Documents