Uploaded on

Web Performance Optimalisation drives traffic, improves UX, increase revenue and reduces costs.

Web Performance Optimalisation drives traffic, improves UX, increase revenue and reduces costs.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
703
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
7
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Web Performance Optimizationstevesouders.com/docs/amsterdam-meetup-20120509.pptxDisclaimer: This content does not necessarily reflect the opinions of my employer.
  • 2. WebWPO Performance Optimizationdrives trafficimproves UXincreases revenuereduces costs
  • 3. backend frontend “waterfall chart”
  • 4. Top 10 24% - backend 76% - frontend
  • 5. 10,000+ 8% - backend 92% - frontend
  • 6. www2012.wwwconference.org/proceedings/proceedings/p41.pdf
  • 7. research.att.com/articles/featured_stories/2011_03/201102_Energy_efficient
  • 8. Mobile State Machine ?
  • 9. www.intuit.com 125 requests1,847 kB1.587 seconds start render9.651 seconds PLTmbox.js docwrites /mbox/standard blocks ie7.css blocks renderingdon’t docwrite scriptsdomain shardingPNGs take 3-6 seconds to downloadwww.webpagetest.org/result/120503_RC_46SJA/
  • 10. quickbooks.intuit.com106 requests 632 kB1.265 seconds start render5.740 seconds PLTmbox.js docwrites /mbox/standard blocks ie7.css blocks renderingdon’t docwrite scriptsdomain shardingadd caching headerswww.webpagetest.org/result/120503_B9_46SJB/
  • 11. turbotax.intuit.com 112 requests 438 kB2.412 seconds start render3.523 seconds PLTrendering extremely blockedconcat scripts, concat stylesheetsdon’t mix inline & external scriptsdon’t docwrite scriptsdomain shardingadd caching headersspriteswww.webpagetest.org/result/120503_ZV_46SJC/
  • 12. turbotax.intuit.com this is turbotax this is turbotax on Page Speedwww.webpagetest.org/compare
  • 13. Caching
  • 14. max-age (days) 3% 8% 16% none max-age <= 0 0 < max-age <= 1 55% 1 < max-age <= 30 15% 30 < max-age <= 365 365 < max-age 3%HTTP Archive: 54K URLs, 4.6M resources55% - NO caching headers18% - cacheable < 1 day 73% }http://httparchive.org/interesting.php#max-age
  • 15. adoption is slowhttp://httparchive.org/trends.php?s=intersection
  • 16. Why so few caching headers? resources are dynamic lack of awareness
  • 17. 55% uncacheable 46% 46% same as same as 38% Jan 15 Jan 15 Jan 15 Feb 1 Feb 15 “uncacheable” resources aren’t very dynamic 2 weeks is a long gap - daily would be higher http://www.stevesouders.com/blog/2012/03/22/cache-them-if-you-can/
  • 18. all resources 46% 44% 35% same as same as Jan 15 Jan 15 Jan 15 Feb 1 Feb 15 “uncacheable” resources are LESS dynamic 2 weeks: 46% (uncacheable) vs. 44% (all) 4 weeks: 38% (uncacheable) vs. 35% (all) who votes for “lack of awareness”?
  • 19. Resources unchanged over me for 100% ALL resources100%80%60% 45%40% 36% 32% 28% 26% 24% 22% 21% 19% 18% 17% 17%20% 16% 15% 14% 14% 13% 12% 12% 11% 11% 10% 10% 9% 0% 2/11 3/15 4/15 5/16 6/15 7/15 8/15 9/15 10/15 11/15 12/15 1/15 2/15 36% of resources unchanged after 1 month only 11% of resources cacheable for > 1 month http://www.stevesouders.com/blog/2012/03/22/cache-them-if-you-can/
  • 20. 40-60% of users missing cacheable resources 20% of page viewshttp://www.yuiblog.com/blog/2007/01/04/performance-research-part-2/
  • 21. (my) browser cache sizes: • Chrome: 320 MB (cap)* • IE 9: 250 MB • IE 7-8: 50 MB • Firefox 11: 830 MB* • Opera 11: 20 MB • iPhone 4: 30-35 MB • Galaxy Nexus: 18 MB* Based on available disk space – I had 50 GB free.
  • 22. Chrome for Windows stats: • 30% (48%?) of users have a full cache • full cache users reach that point after 4 hours of active browsing (20 clock hours) • 7% of users clear their cache 1+ per week • 19% of users experience “fatal cache corruption” 1+ per weekhttps://plus.google.com/103382935642834907366/posts/XRekvZgdnBb
  • 23. recap: • resource owners underutilize max-age • users are often missing cacheable resources • cache sizes are small; caches fill quicklyhttps://plus.google.com/103382935642834907366/posts/XRekvZgdnBb
  • 24. what can we do?• gather more/better stats• make caches bigger (and fix corruption)• improve purging logic (mime type, etc.)• more intelligent, personalized browsers
  • 25. cache compressed or uncompressed? Compressed responses Browser cached compressed? Chrome 17 yes Firefox 11 yes IE 8 no IE 9 no Safari 5 no Opera 11 yeshttp://www.stevesouders.com/blog/2012/03/27/cache-compressed-or-uncompressed/