sxsw: even faster web sites

47
Steve Souders [email protected] http://stevesouders.com/docs/sxsw-20090314.ppt Even Faster Web Sites Disclaimer: This content does not necessarily reflect the opinions of my

Upload: steve-souders

Post on 07-May-2015

10.486 views

Category:

Education


0 download

DESCRIPTION

Presented at SXSW '09, this talk covers five best practices from my next book: Load scripts without blocking, Coupling asynchronous scripts, Don't scatter inline scripts, Use iframes sparingly, and Flush the document early.

TRANSCRIPT

Page 1: SXSW: Even Faster Web Sites

Steve [email protected]

http://stevesouders.com/docs/sxsw-20090314.ppt

Even Faster Web Sites

Disclaimer: This content does not necessarily reflect the opinions of my employer.

Page 2: SXSW: Even Faster Web Sites

17%

83%

iGoogle, primed cache

the importance of frontend performance

9% 91%

iGoogle, empty cache

Page 3: SXSW: Even Faster Web Sites

time spent on the frontend

Empty Cache

Primed Cache

www.aol.com 97% 97%

www.ebay.com 95% 81%

www.facebook.com 95% 81%

www.google.com/search

47% 0%

search.live.com/results 67% 0%

www.msn.com 98% 94%

www.myspace.com 98% 98%

en.wikipedia.org/wiki 94% 91%

www.yahoo.com 97% 96%

www.youtube.com 98% 97%April 2008

Page 4: SXSW: Even Faster Web Sites

14 RULES

1. MAKE FEWER HTTP REQUESTS

2. USE A CDN3. ADD AN EXPIRES HEADER4. GZIP COMPONENTS5. PUT STYLESHEETS AT THE

TOP6. PUT SCRIPTS AT THE

BOTTOM7. AVOID CSS EXPRESSIONS8. MAKE JS AND CSS

EXTERNAL9. REDUCE DNS LOOKUPS10.MINIFY JS11.AVOID REDIRECTS12.REMOVE DUPLICATE

SCRIPTS13.CONFIGURE ETAGS14.MAKE AJAX CACHEABLE

Page 5: SXSW: Even Faster Web Sites
Page 6: SXSW: Even Faster Web Sites
Page 7: SXSW: Even Faster Web Sites
Page 8: SXSW: Even Faster Web Sites

25% discount code: "ssouders25"

Page 9: SXSW: Even Faster Web Sites

Sept 2007

Page 10: SXSW: Even Faster Web Sites

June 2009

Page 11: SXSW: Even Faster Web Sites

Even Faster Websites

Split the initial payloadLoad scripts without

blockingCouple asynchronous scripts

Don't scatter inline scriptsSplit the dominant

domainFlush the document early

Use iframes sparingly

Simplify CSS Selectors

Ajax performance (Doug Crockford)

Writing efficient JavaScript (Nicholas Zakas)

Creating responsive web apps (Ben Galbraith, Dion Almaer)

Comet (Dylan Schiemann)Beyond Gzipping (Tony

Gentilcore)Optimize Images (Stoyan

Stefanov, Nicole Sullivan)

Page 12: SXSW: Even Faster Web Sites

AOLeBayFacebookMySpaceWikipediaYahoo!

why focus on JavaScript?

YouTube

Page 13: SXSW: Even Faster Web Sites

scripts block

<script src="A.js"> blocks parallel downloads and rendering

http://stevesouders.com/cuzillion/?ex=10008

Page 14: SXSW: Even Faster Web Sites

MSNScripts and other resources downloaded in parallel! How? Secret sauce?!var p= g.getElementsByTagName("HEAD")[0];var c=g.createElement("script");c.type="text/javascript";c.onreadystatechange=n;c.onerror=c.onload=k;c.src=e;p.appendChild(c)

MSN.com: parallel scripts

Page 15: SXSW: Even Faster Web Sites

asynchronous script loading

XHR Eval

XHR Injection

Script in Iframe

Script DOM Element

Script Defer

document.write Script Tag

Page 16: SXSW: Even Faster Web Sites

XHR Eval

script must have same domain as main page

must refactor script

var xhrObj = getXHRObject();xhrObj.onreadystatechange = function() { if ( xhrObj.readyState != 4 ) return; eval(xhrObj.responseText); };xhrObj.open('GET', 'A.js', true);xhrObj.send('');

http://stevesouders.com/cuzillion/?ex=10009

Page 17: SXSW: Even Faster Web Sites

XHR Injectionvar xhrObj = getXHRObject();xhrObj.onreadystatechange = function() { if ( xhrObj.readyState != 4 ) return; var se=document.createElement('script'); document.getElementsByTagName('head') [0].appendChild(se); se.text = xhrObj.responseText; };xhrObj.open('GET', 'A.js', true);xhrObj.send('');

script must have same domain as main pagehttp://stevesouders.com/cuzillion/?ex=10015

Page 18: SXSW: Even Faster Web Sites

Script in Iframe<iframe src='A.html' width=0 height=0 frameborder=0 id=frame1></iframe>

iframe must have same domain as main page

must refactor script:// access iframe from main pagewindow.frames[0].createNewDiv();

// access main page from iframeparent.document.createElement('div');

http://stevesouders.com/cuzillion/?ex=10012

Page 19: SXSW: Even Faster Web Sites

Script DOM Elementvar se = document.createElement('script');se.src = 'http://anydomain.com/A.js';document.getElementsByTagName('head')[0] .appendChild(se);

script and main page domains can differ

no need to refactor JavaScript

http://stevesouders.com/cuzillion/?ex=10010

Page 20: SXSW: Even Faster Web Sites

Script Defer<script defer src='A.js'></script>

only supported in IE (just landed in FF 3.1)

script and main page domains can differ

no need to refactor JavaScript

http://stevesouders.com/cuzillion/?ex=10013

Page 21: SXSW: Even Faster Web Sites

document.write Script Tagdocument.write("<scr" + "ipt type='text/javascript' src='A.js'>" + "</scr" + "ipt>");

parallelization only works in IE

parallel downloads for scripts, nothing else

all document.writes must be in same script block

http://stevesouders.com/cuzillion/?ex=10014

Page 22: SXSW: Even Faster Web Sites

load scripts without blocking

*Only other document.write scripts are downloaded in parallel (in the same script block).

Page 23: SXSW: Even Faster Web Sites
Page 24: SXSW: Even Faster Web Sites

asynchronous JS example: menu.js

<script type="text/javascript">var domscript = document.createElement('script');domscript.src = "menu.js"; document.getElementsByTagName('head')

[0].appendChild(domscript);

var aExamples = [ ['couple-normal.php', 'Normal Script Src'], ['couple-xhr-eval.php', 'XHR Eval'], ... ['managed-xhr.php', 'Managed XHR'] ];

function init() { EFWS.Menu.createMenu('examplesbtn', aExamples);}

init();</script>

script DOM element approach

Page 25: SXSW: Even Faster Web Sites

before

after

Page 26: SXSW: Even Faster Web Sites

load scripts without blocking

*Only other document.write scripts are downloaded in parallel (in the same script block).

!IE

Page 27: SXSW: Even Faster Web Sites

what about

inlined code that depends on the script?

Page 28: SXSW: Even Faster Web Sites

coupling techniques

hardcoded callback

window onload

timer

degrading script tags

script onload

Page 29: SXSW: Even Faster Web Sites

technique 5: script onload<script type="text/javascript">var aExamples = [['couple-normal.php', 'Normal Script Src'], ...];

function init() { EFWS.Menu.createMenu('examplesbtn', aExamples);}

var domscript = document.createElement('script');domscript.src = "menu.js";

domscript.onloadDone = false;domscript.onload = function() { if ( ! domscript.onloadDone ) { init(); } domscript.onloadDone = true; };domscript.onreadystatechange = function() { if ( "loaded" === domscript.readyState ) { if ( ! domscript.onloadDone ) { init(); } domscript.onloadDone = true; }}

document.getElementsByTagName('head')[0].appendChild(domscript);</script>

pretty nice, medium complexity

Page 30: SXSW: Even Faster Web Sites

case study: Google Analytics

recommended pattern:1

<script type="text/javascript">var gaJsHost = (("https:" == document.location.protocol) ?

"https://ssl." : "http://www.");

document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));

</script>

<script type="text/javascript">var pageTracker = _gat._getTracker("UA-xxxxxx-x");pageTracker._trackPageview();</script>

document.write Script Tag approach blocks other resources

1http://www.google.com/support/analytics/bin/answer.py?hl=en&answer=55488

Page 31: SXSW: Even Faster Web Sites

case study: dojox.analytics.Urchin1

_loadGA: function(){ var gaHost = ("https:" == document.location.protocol) ? "https://ssl." : "http://www."; dojo.create('script', { src: gaHost + "google-analytics.com/ga.js" }, dojo.doc.getElementsByTagName("head")[0]); setTimeout(dojo.hitch(this, "_checkGA"), this.loadInterval);},

_checkGA: function(){ setTimeout(dojo.hitch(this, !window["_gat"] ? "_checkGA" :

"_gotGA"), this.loadInterval);},

_gotGA: function(){ this.tracker = _gat._getTracker(this.acct); ...}

Script DOM Element approach"timer" coupling technique (script onload

better)1http://docs.dojocampus.org/dojox/analytics/Urchin

Page 32: SXSW: Even Faster Web Sites

asynchronous loading & coupling

async technique: Script DOM Element– easy, cross-browser– doesn't ensure script order

coupling technique: script onload– fairly easy, cross-browser– ensures execution order for external

script and inlined code

Page 33: SXSW: Even Faster Web Sites

bad: stylesheet followed by inline script

browsers download stylesheets in parallel with other resources that follow...

...unless the stylesheet is followed by an inline script

http://stevesouders.com/cuzillion/?ex=10021

best to move inline scripts above stylesheets or below other resources

use Link, not @import

Page 34: SXSW: Even Faster Web Sites

eBayMSNMySpaceWikipedia

don't scatter inline scripts

Page 35: SXSW: Even Faster Web Sites

iframes: most expensive DOM element

load 100 empty elements of each type

tested in all major browsers1

1IE 6, 7, 8; FF 2, 3.0, 3.1b2; Safari 3.2, 4; Opera 9.63, 10; Chrome 1.0, 2.0

Page 36: SXSW: Even Faster Web Sites

iframes block onload

parent's onload doesn't fire until iframe and all its components are downloaded

workaround for Safari and Chrome: set iframe src in JavaScript

<iframe id=iframe1 src=""></iframe><script type="text/javascript">document.getElementById('iframe1').src="url";</script>

Page 37: SXSW: Even Faster Web Sites

scripts block iframe

no surprise – scripts in the parent block the iframe from loading

IE

Firefox

Safari Chrome

Opera

script

script

script

Page 38: SXSW: Even Faster Web Sites

stylesheets block iframe (IE, FF)

surprise – stylesheets in the parent block the iframe or its resources in IE & Firefox

IE

Firefox

Safari Chrome

Opera

stylesheet

stylesheet

stylesheet

Page 39: SXSW: Even Faster Web Sites

stylesheets after iframe still block (FF)

surprise – even moving the stylesheet after the iframe still causes the iframe's resources to be blocked in Firefox

IE

Firefox

Safari Chrome

Opera

stylesheet

stylesheet

stylesheet

Page 40: SXSW: Even Faster Web Sites

iframes: no free connections

iframe shares connection pool with parent (here – 2 connections per server in IE 7)

iframe

parent

Page 41: SXSW: Even Faster Web Sites

flush the document early

gotchas:– PHP output_buffering – ob_flush()– Transfer-Encoding: chunked– gzip – Apache's DeflateBufferSize before

2.2.8– proxies and anti-virus software– browsers – Safari (1K), Chrome (2K)

other languages: $| or FileHandle autoflush (Perl), flush

(Python), ios.flush (Ruby)

htmlimageimagescript

htmlimageimagescript call PHP's flush()

Page 42: SXSW: Even Faster Web Sites

flushing and domain blocking

you might need to move flushed resources to a domain different from the HTML dochtml

imageimagescript

htmlimageimagescript

googleimageimagescriptimage204

case study: Google search

blocked by HTML document

different domains

Page 43: SXSW: Even Faster Web Sites

takeaways

focus on the frontend

run YSlow: http://developer.yahoo.com/yslow

this year's focus: JavaScript

speed matters

Page 44: SXSW: Even Faster Web Sites

impact on revenue

Google:

Yahoo:

Amazon:

1 http://home.blarg.net/~glinden/StanfordDataMining.2006-11-29.ppt2 http://www.slideshare.net/stoyan/yslow-20-presentation

+500 ms -20% traffic1

+400 ms -5-9% full-page traffic2

+100 ms -1% sales1

Page 45: SXSW: Even Faster Web Sites

cost savings

hardware – reduced load

bandwidth – reduced response size

http://billwscott.com/share/presentations/2008/stanford/HPWP-RealWorld.pdf

Page 46: SXSW: Even Faster Web Sites

if you want better user experience more revenue reduced operating expenses

the strategy is clear

Even Faster Web Sites

Page 47: SXSW: Even Faster Web Sites

Steve [email protected]

http://stevesouders.com/docs/sxsw-20090314.ppt