WordCamp Denmark Keynote
•Transferir como PPTX, PDF•
7 gostaram•3,461 visualizações
Frederick Townes presented on optimizing websites for performance. He discussed working backwards from user experience, prioritizing the largest issues. Factors that can improve performance include front-end and back-end optimization, reducing payload size, caching, optimizing databases and runtime, reducing workload, and using content delivery networks. Key metrics to measure include page load time, time to first byte, and time on site. Common cases like JavaScript optimization and recommended plugins were also covered.
![Hi! ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (7)
Semelhante a WordCamp Denmark Keynote
Semelhante a WordCamp Denmark Keynote (20)
Último
Último (20)
WordCamp Denmark Keynote
- 1. Working Backwards Frederick Townes, CTO Mashable.com WordCamp Denmark, 15.05.2010
- 3. Founder @ W3-EDGE.com
- 4. Founded @ W3-MARKUP.com
- 5. Creator of W3 TOTAL CACHE
- 6. Co-host of the WordPress Community PodcastIntroduction
- 8. Solve the largest issues first
- 9. Rinse and repeatIntroduction
- 11. Developed WP themes and / or plugins?
- 12. Uses WP to power their entire site?
- 13. Used W3 Total Cache?
- 14. Read Mashable.com before?
- 15. No interest in seeing any code today?Introduction
- 16. What we thought we made… Introduction
- 17. What was actually delivered… Introduction
- 19. Which factors can be controlled
- 20. Measure results
- 21. A look at common cases
- 22. Discuss your questions and challengesIntroduction
- 24. Slow speeds cost you money, 500ms means a 20% traffic loss (Google)
- 25. The more responsive the site, the lower the user’s learning curve
- 26. The web is moving towards “real-time” interactivityWhy performance matters
- 30. Create sprites using http://spriteme.org/
- 31. Use http://punypng.com/ to reduce image size
- 32. Minify: combine CSS / JS files respectively when possible
- 33. Use AJAX if possible
- 34. Avoid cookies
- 35. Lazy load images
- 36. Upgrade jQuery to improve JavaScript performanceWhich factors can be controlled
- 39. Configure MySQL properly: - Use slow query log to resolve bottlenecks - Use http://mysqltuner.pl/ to key_buffer, query_cache, etc
- 40. Cache queries, if possibleWhich factors can be controlled
- 42. Object caching optimizes runtime performance
- 43. Opcode caching further enhances PHP performanceWhich factors can be controlled
- 45. Use fragment caching - Side bar widgets - Complex elements
- 46. Don’t allow WP to handle 404 errors for static objects
- 47. Reduce latency for static objects (use a content delivery network)Which factors can be controlled
- 49. Time to first byte
- 50. Render start time
- 51. Time on site / page views per visitMeasure results
- 54. Use Firebug (http://getfirebug.com/) Net tab + YSlow (http://developer.yahoo.com/yslow/)
- 57. Use Chartbeat or Woopra to monitor real-time user reading / writing etc
- 58. Ask your users for feedback
- 59. Follow the money, e.g. AdSense revenue increaseMeasure results
- 61. Use <link> not <style> in <head> and put it above any JavaScript
- 62. Use the asynchronous tracking code for Google Analytics
- 63. Place ad network code after <body>, use networks like BuySellAds.comor OpenX.com, not DoubleClickfor Publishers
- 64. Put any scripts not necessary for the interface above the </body> tag
- 65. Use a content delivery networkA look at common cases
- 71. BuddyPress / bbPress
- 72. PollDaddy
- 73. NextGenGallery
- 74. PubSubHubHub
- 75. Robots Meta or Platinum SEO
- 76. WP-PageNavi
- 77. W3 Total CacheBonus
- 78. Thank You.Questions? Site Review? ftownes@w3-edge.com frederick@mashable.com @w3edge