Everyone who runs a website already does initial Web Performance optimization during development with browser web toolkits. In order to survive Black Friday, Cyber Monday and other events we do load testing, and for production monitoring we have real user monitoring solutions in place. By using these tools we already have the foundation in place to start working on a DevOps strategy for our companies.
In this session, we will explore why these tools are essential for a DevOps strategy. What limitations are we currently running into by using them with single page load apps? I will show real-life examples from different companies I’ve worked with, what their performance and DevOps problems were and how they tackled them.
25. 25 #kenzenhofer
Mobile Landing Page of Super Bowl Ad
434 Resources in total on that page:
230 JPEGs, 75 PNGs, 50 GIFs, …
Total size of ~
20MB
26. 26 #kenzenhofer
m.store.com redirects to www.store.com
ALL CSS and JS files are
redirected to the www domain
This is a lot of time “wasted”
especially on high latency mobile
connections
27. 27 #kenzenhofer
Critical Pages not Optimized!
Browse, Search
and Product Info
performs well
… because they don’t follow
best practices: 87 Requests, 28
Redirects, …
Critical Pages such as
Shopping Cart are very
slow …
34. 34 #kenzenhofer
“Teamwork” between Dev and Ops
SEV1 Problem in Production
Need access to log files
Where are they? Can’t get
them
Need to increase log level
Can’t do! Can’t change config
files in prod!
57. 57 #kenzenhofer
“Our customers expect the same experience
throughout all our channels no matter if it is
the website, mobile site or the real physical store!”
Mike Austin, Director of e-Commerce
RoomstoGo.com