Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Web performance optimization (WPO)


Published on

A presentation from SEO Campixx Barcamp 2011 in Berlin. Web Performance Optimization is about making websites faster. Here i discussed different measures and show the impact on competitive advantage and possibly rankings on Google. Undeniably you can say that better performance leads to more sales and better usability in terms of bouncing rates. View image slides here:

Published in: Technology, Design
  • Experiential failures and learning have enabled our core team to establish site performance best practices. The best practices are grouped into categories that cover different aspects of page load optimization / site performance optimization:
    Are you sure you want to  Yes  No
    Your message goes here
  • Nice deck.

    If anyone is using .net, check out A great resource for web performance optimization that merges and minifies CSS as well as automatically sprites its background images. It not only creates the sprite file automatically, but it does it on the fly through an HttpModule along with merging and minifying all CSS. It lso optimizes the sprite image using quantization and lossless compression and it handles the serving of the generated files using ETags and Expires headers to ensure optimal browser caching. The setup is trivial involving just a simple web.config change. See this blog post about its adoption by the Microsoft Visual Studio and MSDN Samples gallery:!.aspx
    Are you sure you want to  Yes  No
    Your message goes here
  • In this optimizing performance it is very true that the aim is to satisfied the customer needs.
    such an incredible ideas
    Are you sure you want to  Yes  No
    Your message goes here

Web performance optimization (WPO)

  1. Website Performance Optimization<br />Mariusz Kaczmarek<br />
  2. “If it is fast and ugly, they will use it and curse you; if it is slow, they will not use it.”<br />David Cheriton<br />Source:<br /><br />2<br />
  3. Categorization<br />3<br />
  4. Optimize performance?<br /> More sales <br /> Less bandwidth & server peaks <br /> Customer satisfaction <br /> Might influence rankings <br />Competitive advantage<br />Source:<br />4<br />
  5. “…optimize front-end performance first, that's where 80% or more of the end-user response time is spent” <br />Prof. Steve Souders<br />Source:<br /><br />5<br />
  6. Effective measures?<br /> Website performance optimization should be aligned with the <br /> service / website / target audience you work with.<br /> Focus areas could be:<br /> Image optimization & compression<br /> JS performance (asynchronous, cached)<br /> Reduction of DOM elements <br /> Teaching customers and employees!<br />6<br />
  7. Combined Scripts<br />  Server-sided combination<br />  Avoid @import for combining<br />  JS tool: HEADjs<br />7<br />
  8. CSS Performance<br />  Reuse of round corners and <br /> shadow classes  font-faces instead of pictures<br />  CSS-Sprites<br /> Universal > tags > classes > IDs<br />Source:<br /><br />8<br />
  9. Postponed Loading<br /> Use of GET with AJAX<br /> Google Instant takessnapshots 5-10s after onLoadevent?<br />Tools: <br />ContolJS<br />ImageLoader<br />LazyLoad<br />Source:<br />9<br />
  10. Event handlers, components,XHRs<br />User interaction, XHRs<br />backend<br />components<br />request<br />Site loaded<br />HTML sent<br />request<br />onload<br />5-10s<br />Google Instant Snapshot<br />Modifiedimage from High Performance Web Pages | Stoyan Stefanov | Yahoo! Exceptional Performance | PHP Quebec, March 13, 2008<br />Source:<br />10<br />
  11. DNS Lookups & Redirections<br /> Avoid 301 redirections (e.g. in HTML)<br /> !=<br /> usage of not morethan2-5 different<br />domains on average<br /> better: domain-aliases for parallel downloads ||<br /> cookielessdomainsforstaticcontent<br />Source:<br />11<br />
  12. Content Delivery Network<br />Geographical distribution<br /> Minimizes DNS-Lookups <br /> Optimized caching und uptime<br /> (by dynamic DNS resolving)<br />Source:<br />12<br />
  13. Image Compression<br /> <br /> Progressive JPEG<br />baseline<br /> progressive<br />Source:<br />13<br />
  14. Vector Graphics<br /> Canvas Elemente with HTML5<br />Ai->Canvas<br />Progressive JPEG 13,3 kB -> HTML5 2,38 kB<br />Saved: 82%<br />14<br />
  15. Shape the DOM Tree<br /> <h1><em>Heading</em></h1> - useCSS‘sitalicsinstead<br />  Tool: DOM-Monster<br />  Avoid iFrames<br />15<br />
  16. Chunking<br /> flushfunction<br />Source:<br /><br />16<br />
  17. Performance Test Tools<br /><br />Slow<br />Show<br />Webpagetest<br /> Browser based<br />Speedtracer<br />YslowFireBug<br />More tools:<br />17<br />
  18. Competition Analysis<br /> Possible performance profiles (by Souders & students)<br /><br /> Simple linear regression analysis<br />Wolfram Alpha: linear fit {1, 87},{2, 77},{3, 95},{4, 68}<br /><br />18<br />
  19. Pareto Rule 80/20<br />Optimizationneeds time!<br />Lessons learned: Concentrate on biggestchunks<br />Source: JavaScript: The Good Parts - Part Six: Ajax Performance | Douglas Crockford<br />19<br />
  20. Questions? Discuss!<br />Let’s be friends <br />Twitter: BONOSEO<br />Facebook: kaczmarek.mariusz<br />Ssssshh… SouderSlides from Stanford:<br />20<br />
  21. Statistics 2010<br />Additional<br /> Average website size: 320 kB<br /> Compression is possible for 2/3 of overall data<br /> 80% of content is loaded from one host<br />Source: Statisticnumbers from 4.2 billionsites<br />21<br />
  22. Inline Images<br /> Base 64 encoding<br /> Great forsmallstaticimages<br />Additional<br />Works until IE7<br /> Browser switch!<br />22<br />Source:<br />
  23. JavaScript Performance<br />Additional<br /> Tools: <br /><br /><br /> DRY and OO approach<br />Seconds per 10 million operations<br />Source: Besser PHP Programmieren – Professionelle PHP-Techniken | Carsten Möhrke<br />23<br />