Sessions at Velocity Europe 2011 about Web Performance on Tuesday 8th November

Your current filters are…

  • The Future of Application Performance Management

    by Brian Doll

    Web applications are being shipped faster, deployed instantly to the cloud and are catering to the ever-growing needs of a technologically connected audience.

    How do you manage it all? How do you maintain high performance in your application, stay on top of your server performance and ensure your end users are getting the best service you can deliver? Find out with New Relic!

    At 10:05am to 10:10am, Tuesday 8th November

    Coverage video

  • Betfair's Site Rebuild: Fast - We Promise

    by Tim Morrow

    Betfair recently launched a beta version of their Sports betting website and is in the process of rolling out the site to new customers. We would like to present our journey so far and our results:

    Faster page load times Improving our operational insight into the performance of our website Significantly increasing our rate of deployment through continuous delivery How it impacted our bottom line

    Our talk will explore the initiative in great detail. We will discuss:

    • Why we launched our Customer Commitment
    • The Betfair site architecture
    • Performance techniques applied including reducing the number of HTTP requests, reducing DNS lookups, minification, flushing the buffer early, eliminating iframes, using cookie-free domains for components, optimising CSS sprites
    • How we measure performance How we measure the key business metrics including page load times, conversion rates such as registration, bets placed and revenue per customer

    At 11:20am to 11:50am, Tuesday 8th November

    Coverage video

  • Rethinking the Mobile Web Performance Experience

    by Jon Jenkins

    The complexity of website content (as measured by the HTTP Archive) continues to increase. Meanwhile, the number of mobile browsing devices is increasing at more than 25% each year. Due to their limited processing power, memory, storage and network bandwidth these devices pose new challenges in terms of web performance as sites become more complex. To date, the approach to solve these issues has been to create mobile versions of web sites with limited content and simplified layout. This talk will present a new way we are looking at the mobile browsing challenges at Amazon.com. We will present data about site latency among various classes of devices and usage of mobile versions of the site. Much of the presentation will focus on technical approaches to dramatically reduce web site latency for this class of users.

    At 1:00pm to 1:45pm, Tuesday 8th November

    Coverage slide deck

  • Measuring Web Performance

    by Stephen Thair

    How do you measure web page performance?

    We all talk a lot about how fast our web pages are but are we comparing apples with apples?

    There are at least 6 different ways to measure web page performance, and multiple metrics to gather such as initial render, “above the fold” time or onLoad event time.

    The goal of this talk is to put web performance measurement in perspective by identifying and classifying the different ways of measuring web performance.

    So what dimensions can we compare them on?

    1. Accuracy?
    2. What metrics do they collect?
    3. “Completeness” of measurement – e.g. can they measure 3rd party or CDN content?
    4. Ease of implementation / use?
    5. Scalability (e.g. are they suitable for “real-user monitoring” type solutions or are they more developer/single-user oriented?)
    6. Are they suitable for Mobile devices?
    7. Are they suitable for measuring web API’s?
    8. What’s the cost?
    9. Suitable for SME vs Enterprise?

    We will also talk about the “active monitoring versus real-user monitoring” debate… what are the pro’s & con’s of each approach and will one eventually supplant the other?

    At 2:40pm to 3:25pm, Tuesday 8th November

    Coverage slide deck

  • How DRY affects JavaScript performance - faster JavaScript execution for the lazy developer

    by Mathias Bynens

    Let’s unravel the grey area of improving actual JavaScript code itself and discover the truth and science of JavaScript performance patterns.

    While improving network performance of your scripts through file size and the script loading is critical, the run-time performance of your JavaScript code has the most direct effect of the visceral feel that your users experience.

    I created jsPerf.com, the JavaScript performance testing playground, to settle the scores of JavaScript performance recommendations. I’ve come up with a simple theorem — easily summarized. Basically, the biggest enemies of performance when it comes to JavaScript (in descending order) are:

    1. Reading/writing to the DOM
    2. Function calls
    3. Lookups (scope lookups, property lookups, array item lookups)

    Of course, there’s not much you can do in JavaScript without using any of these things. The idea is that if you can get rid of a DOM read by using a function call or a property lookup instead, you should do it. Similarly, if you can replace a function call with a scope lookup, go for it! It will result in DRY code with much better performance.

    I spend a lot of time reviewing other people’s JavaScript code for performance issues, and I think it’s safe to say this presentation covers about 70% to 80% of the improvements that I usually end up recommending. It’s a simple principle, and it’s easy to apply it once you understand it fully —there just needs to be someone to explain it all to you. I’m that guy!

    The basic gist of this idea fits in one slide, but I’d like to take the time to A) explain what exactly these slow things are (so even JavaScript beginners that don’t know what a scope lookup is can follow along); and B) show lots of practical, real-world examples of how applying this technique can result in better performance, regardless of whether you’re using JavaScript libraries or plain vanilla JavaScript. A is especially useful for people who are new to high-performance JavaScript, but B will be useful for more advanced JavaScript coders as well.

    I believe this technique is useful because it can be applied to all the JavaScript code you’ll ever write, and it’s guaranteed to have a positive impact on performance (among other advantages). It will be useful for both JavaScript beginners (because everything will be explained properly) and advanced scripters that want to focus on performance while coding JavaScript.

    At 3:55pm to 4:15pm, Tuesday 8th November

    Coverage slide deck

  • Empirical Results from Page Speed and mod_pagespeed

    by Andrew Oates, jmarantz and Matthew Steele

    Page Speed Analysis tools provide performance metrics for web-sites, and mod_pagespeed and Page Speed Service automatically rewrite web sites by applying web performance “best practices”. But exactly what is the impact on web site latency and usability from implementing these transformations? We’ll share what we’ve learned from running Page Speed and mod_pagespeed in the field.

    What is the impact of specific web performance optimizations on metrics like page load time and time to first paint? What is the interaction between latency, page structure, and network-level decisions such as when to flush web pages so that browsers can start rendering? In this talk, we’ll present our latest findings and show developers how to apply these findings to their own web sites.

    We’ll conclude with a discussion of new features being added to Page Speed analysis & rewriting tools to translate these learnings into a faster web.

    At 4:20pm to 4:40pm, Tuesday 8th November

Schedule incomplete?

Add a new session

Filter by Day

Filter by coverage

Filter by Topic