Group items tagged

Apparemment le lien fournit pour Prada n'est pas le bon, petite confusion je pense entre Prada US / EN. Les chiffres dans l'article ne correspondent pas avec les données de webpagetest. Dans l'article on évoque "Load/response time", où se trouve cette donnée sur webpagetest ?

Depending on whom you ask, the ideal page load can be 100 milliseconds, 400 milliseconds, 2 seconds... you get the picture. In our industry, we talk a lot about big, hairy, audacious performance goals, but what about the other end of the spectrum: the performance poverty line?

"while 75% of the top 100 retail websites employ a Content Delivery Network (CDN), the median home page takes a full second longer to become interactive than the median page that does not use a CDN"

When we look back over the history of web performance we see a heavy focus on reducing the number of requests and getting files to the browser quickly. Our platform has changed a lot, and while optimizing for network performance remains a crucial part of our jobs, we now have to broaden our performance horizons. Our users also expect smooth scrolling, animations and interactions, even on mobile devices. In short we need to deal with not just how quickly our sites and apps load, but also how quickly they run. [video] In this session Paul takes a lightning tour of how Chrome converts the DOM into pixels, see how our code affects its workload, and arrive at a modern workflow for finding (and eliminating) rendering bottlenecks.

et les posts suivants : http://www.stevesouders.com/blog/2010/12/15/controljs-part-2/ http://www.stevesouders.com/blog/2010/12/15/controljs-part-3/