Web 2.0 Expo

March 25, 2008 12:52 pm | 5 Comments

I’ll be speaking at Web 2.0 Expo in San Francisco April 25 at 1:30pm. My talk is called Even Faster Web Sites. This is my next set of performance best practices including how to load scripts without blocking and the dangers of inline scripts. If you’re thinking of coming please the discount code “websf08sbg” to save an extra 10%.

5 Responses to Web 2.0 Expo

  1. Joao Prado Maia | 27-Mar-08 at 6:50 am | Permalink |

    Steve,

    That looks really interesting. It’s too bad that I will be attending the MySQL conference just the previous week, or I would try to attend Web 2.0 for your session.

    Maybe you could include those new rules into the 2nd edition of your book?

    –Joao

  2. Hans | 04-Apr-08 at 6:49 am | Permalink |

    believe I found an anomaly in YSlow. some extensions values in the yslow.js are not being being picked up. I have found the extension values are being defaulted to the values in lint.js, specifically:
    pref(“extensions.firebug.yslow.pointsGzip”, 1);
    pref(“extensions.firebug.yslow.gzipFileSize”, 700);
    What I found was the yslowFirebug.js getPref() would receive a “undefined” type as the nsiPrefBranch type is INVALID (0)

  3. marvin mitchell | 29-Apr-08 at 7:54 am | Permalink |

    as usual steve your talk was enlightening and inspiring. really excited to here about your new focus on js execution.

  4. ccruz | 29-Apr-08 at 5:52 pm | Permalink |

    Hi Steve,

    Your Web 2.0 session was easily one of the most valuable I attended.

    I had one lingering question, though. You mentioned that large chunks of inline script will block page rendering and suggested using setTimeout’s to circumvent the problem.

    Could you please provide a code sample of this technique in action?

    Thanks so much!!

  5. Steve Souders | 29-Apr-08 at 8:28 pm | Permalink |

    ccruz: In my slides I have a Cuzillion page that shows how an inline script with a 5 second loop blocks the page from rendering:

    https://stevesouders.com/cuzillion/?ex=10020

    To show how setTimeout avoids the problem I took the document source from that example and wrapped the 5 second loop in a function called through setTimeout:

    https://stevesouders.com/inline-scripts-settimeout.php

    You can use the “Now:” time value to see that this second example renders immediately.