1 / 28

Los Angeles – Web Perf - Meetup

Web Ops Performance. State of Retail Web Performance. Los Angeles – Web Perf - Meetup. Mehdi Daoudi – CEO Catchpoint Systems – mehdi@catchpoint.com. WHY?. PROTECT YOUR BRAND!. Online users are impatient. If a site is slow - they are gone!

trent
Download Presentation

Los Angeles – Web Perf - Meetup

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Ops Performance State of Retail Web Performance Los Angeles – Web Perf - Meetup Mehdi Daoudi – CEO Catchpoint Systems – mehdi@catchpoint.com

  2. WHY?

  3. PROTECT YOUR BRAND! • Online users are impatient. If a site is slow - they are gone! • Unlike in brick and mortar company, every competitor is a click away! • Happens once you lose a sale, pageview, widget…, happens frequently you lose a customer! Performance is the 5th P of the Marketing Mix. Performance is a Business Differentiator!

  4. Know about performance issues before your customers! Customers are Not LAB RATS!

  5. State of Retail Web PerformanceHoliday Season 2011

  6. Some Performance Charts 60% Of The Sites Started Displaying Content In Less than 1 Second

  7. Some Performance Charts

  8. Some Performance Charts 72% Of The Sites Took Longer Than 3 Seconds To Load All The Content

  9. Some WPO Stats: Requests to Primary Host 60% Of The Sites Served 10 Or More Requests From The Same Domain As The Page!

  10. Some WPO Stats: Number of Hosts 22% Of The Sites Had Requests To More Than 20 Unique Hosts!

  11. Some WPO Stats: Number of Requests 66% Of The Sites Had 60+ Requests, 32% Had 101+

  12. Some WPO Stats: Size Four Sites Served More Than 1.5 Megabyte Of Content

  13. Some WPO Stats: Big Picture

  14. Beware of Scores!!!!

  15. Newegg

  16. Victoria Secrets

  17. Crate & Barrel https://sandbox.fiftyone.com/welcome/resources/themes/overall-style.css https://sandbox.fiftyone.com/welcome/resources/2825/css/master.css

  18. WPO 2012 Recommendations • Lighten Up Page Design: Lighten up the page design to exclude pieces that might impact performance such as: personalization, ads, content optimization, unnecessary embellishments, and content not related to this special event. By removing this content you will not only speed up the rendering of the page on the browser, but will also reduce load on the servers. • Server Side Performance: Look at the data collected from your monitoring tools to find where you can optimize your infrastructure, front end code, SQL Queries, Databases, backend etc. For the majority of the sites there is room for improving the performance and availability of their systems. • Web Performance Optimization: Apply WPO techniques to your pages, to speed up the rendering of the page. You should aim to implement all of them, but if resources are limited focus on these four rules: • Decrease Number of Requests: Decrease number of requests made by a webpage through elimination, sprites, data URIs, etc. • Decrease Number of Bytes: Decrease the number of bytes for entire page through elimination, file optimization, minifying content, and compression. There is no reason to load JavaScript libraries with overlapping functionalities and no reason to serve HTML, CSS, and JavaScript uncompressed. • Defer Loading of JavaScript: JavaScript loading and execution is still a major bottleneck for rendering content. Aim to design pages that defer the loading and execution of JavaScript when possible. • Deliver Static Content from a CDN: Do not load static content like Images, JavaScript, and stylesheets, from the same host as the site. Host static content in CDN, or other group of server, relying on domains that do not set/store cookies and serve it from two unique domains to increase the amount of parallel requests the browser can make. • 3rd Party Providers (non CDN): Load 3rd party provider tags asynchronously post Document Complete or remove them when not required during that time period. It will speed up the load of the page - and eliminate any risks associated with their performance during this key time period

  19. Facelift – Perflift THIS IS LA!!!

  20. Toolbox

  21. Standalone Chrome – Developer tool IE 9 – Developer tool Fiddler HTTPWatch Yslow Dynatrace Wireshark Firebug Dig for DNS MTR (Matt traceroute) Online: WebPageTest Redbot Google Page speed (http://pagespeed.googlelabs.com/) Toolbox 

  22. DNS Connect Time Wait Time (TTFB) Render Start Time Document Complete Key Metrics 

  23. Monitor Action Plan  Optimize Monitor… do it again And it’s never over. Improvement Starts with Measurement If you can not measure it You can not improve it

  24. Robots.txt

  25. Robots.txt

  26. One MORE CHART!

  27. Speed VS Functionality

  28. THANK YOU. http://blog.catchpoint.com @catchpoint

More Related