Performance is critical to the success of any website, and help with using today’s new tools is key. In this remarkable guide, 32 leading web performance experts offer practical tips, techniques, and advice for optimizing your site’s user experience.
Originally written for an online calendar, this collection of articles will inspire you to squeeze every ounce of performance from your site—whether you’re a web developer, mobile developer, or web designer. Check the table of contents and you’ll be convinced.
In order of appearance, Web Performance Daybook authors include:
Chapter 1 WebPagetest Internals
Resulting Browser Architecture
Get the Code
Chapter 2 localStorage Read Performance
What’s Going On?
Chapter 3 Why Inlining Everything Is NOT the Answer
No Browser Caching
No Edge Caching
No Loading On-Demand
Invalidates Browser Look-Ahead
Flawed Solution: Inline Everything only on First Visit
Summary and Recommendations
Chapter 4 The Art and Craft of the Async Snippet
The Facebook Plug-ins JS SDK
Parting Words: On the Shoulders of Giants
Chapter 5 Carrier Networks: Down the Rabbit Hole
Gold in Them There Hills
4G Won’t Save Us
Where Do We Go from Here?
Light at the End of the Tunnel
Chapter 6 The Need for Parallelism in HTTP
Introduction: Falling Down the Stairs
Current Best Practices: Working around HTTP
Experiment: Mining the HTTP Archive
Results: Serialization Abounds
Recommendations: Time to Fix the Protocols
Chapter 7 Automating Website Performance
Chapter 8 Frontend SPOF in Beijing
The Cause of Frontend SPOF
Avoiding Frontend SPOF
Call to Action
Chapter 9 All about YSlow
Chapter 10 Secrets of High Performance Native Mobile Applications
Keep an Eye on Your Waterfalls
Compress Those Resources
Don’t Download the Same Content Twice
Can Too Much Adriana Lima Slow You Down?
Chapter 11 Pure CSS3 Images? Hmm, Maybe Later
Getting My Hands Dirty with CSS3 Cooking
Are We There Yet?
Appendix: Code Listings
Chapter 12 Useless Downloads of Background Images in Android
The Android Problem
And the Lack of Solution
Chapter 13 Timing the Web
Chapter 14 I See HTTP
The Road Ahead
All I Want for Christmas…
Chapter 15 Using Intelligent Caching to Avoid the Bot Performance Tax
Chapter 16 A Practical Guide to the Navigation Timing API
Why You Should Care
Collecting Navigation Timing Timestamps and Turning Them into Useful Measurements
Using Google Analytics as a Performance Data Warehouse
Reporting on Performance in Google Analytics
Chapter 17 How Response Times Impact Business
Chapter 18 Mobile UI Performance Considerations
Embedding CSS and JS: A Best Practice?
Chapter 19 Stop Wasting Your Time Using the Google Analytics Site Speed Report
Problem: A Bug in Firefox Implementation of the Navigation Timing API
Solution: Filter Out the Firefox Timings in Google Analytics
Good News: The Bug Was Fixed in Firefox 9
Chapter 20 Beyond Web Developer Tools: Strace
What About Other Platforms?
Example: Local Storage
We’ve Only Scratched the Surface
Chapter 21 Introducing mod_spdy: A SPDY Module for the Apache HTTP Server
Getting Started with mod_spdy
SPDY and Apache
Help to Improve mod_spdy
Chapter 22 Lazy Evaluation of CommonJS Modules
Lazy Evaluation to the Rescue
Building Lazy Evaluation into CommonJS Modules
Chapter 23 Advice on Trusting Advice
Chapter 24 Why You’re Probably Reading Your Performance Measurement Results Wrong (At Least You’re in Good Company)
Why Does This Matter?
Chapter 25 Lossy Image Compression
Collecting and Analyzing the Data
Chapter 27 A Simple Way to Measure Website Performance
Chapter 28 Beyond Bandwidth: UI Performance
After the Page Loads: The UI Layer
Perception of Speed
Call for a Focus on UI Performance
Chapter 29 CSS Selector Performance Has Changed! (For the Better)
What Is It Still Slow?
Chapter 30 Losing Your Head with PhantomJS and confess.js
App Cache Manifest
Onward and Upward
Chapter 31 Measure Twice, Cut Once
Chapter 32 When Good Backends Go Bad
What Is a Good Backend Time?
Figuring Out What Is Going On
Chapter 33 Web Font Performance: Weighing @font-face Options and Alternatives
The animal on the cover of Web Performance Daybook Volume 2 is a Sugar Squirrel Biak Glider. The squirrel glider (Petaurus norfolcensis) is a nocturnal gliding possum, not to be confused with the flying squirrel. The flying squirrel of North America is a placental mammal, while the squirrel glider is a marsupial.Squirrel gliders are native to the range from the South Australian and Victorian Border through southeast Australia, where they inhabit dry forest and woodlands, to northern Queensland, where they inhabit a wetter eucalypt forest. These wrist-winged gliders make their home in hollowed out trees, lining their dens with leaves. Typically, they live in groups of one male, two females, and offspring.The squirrel glider's diet consists of predominantly insects and fruit, followed up by tree sap of the Eucalypt and Red Bloodwood variety, pollen, nectar, leaves, and bark. Squirrel gliders have bushy tails comparable to the ring tail possum, and use it as an extra limb to wrap around branches to hold on.The cover font is Adobe ITC Garamond. The text font is Linotype Birka; the heading font is Adobe Myriad Condensed; and the code font is LucasFont's TheSansMonoCondensed.
Comments about oreilly Web Performance Daybook Volume 2:
Web Performance DayBook Volume 2
The second volume from O'reilly Publishing wasn't what I expected it to be at all. Having not read the first book, I didn't know what it might contain. I received the book from the publisher for review and was actually pleasantly surprised by it's contents.
Essentially it is a collection of blog posts regarding, well, web site performance. You might wonder at the value of a printed book that contains blog posts that are freely available from the web, and initially I did too, but after reading the book, I certainly can now find a purpose and a place for it.
Aside form the fact that you can read it anywhere without a network connection, (including below 10,000 feet on an airplane), it saves you searching and weeding through plethora of posts about website performance.
The book is structured in chapters, with each chapter containing a prominent post dealing with something that has to do with website performance. Essentially it is similar to the web in that it doesn't have a beginning or end that progresses as the pages do. Given this format, I started by randomly choosing a chapter and then reading it.
You may not be able to apply every chapter to your own work, but you certainly can glean something from each chapter.
Delightfully, some chapters were heavy on code and technical information, while others presented more theory and general ideas for increasing your we site's performance. Thankfully, there are chapters devoted to mobile and desktop performance as well as server performance too.
For instance, Chapter 17, "Response Times Affect Business", dealt with the psychological and sociological aspects of page loading times. This chapter deals with user perceptions of response time when dealing with any interface and through data demonstrates how page-load times can often lead to them leaving your site.
Chapter 3, "Why Inlining Everything is NOT the Answer", was another favorite of mine. This chapter wasn't heavy on code, but used real examples of site's to explain the concepts of reducing the number of HTTP requests and how this can affect your page's performance.
Chapter 5, "Carrier Networks", examined the conundrum of despite every effort to optimize and improve your site's performance, mobile users might still be choked by their data carrier.
Chapter 9, "All About "YSlow" offered insight into yahoo's page-speed analysis tool in a general way.
A great code-heavy chapter was Chapter 11, "Pure CSS3 Images". This is a code-heavy chapter that goes into great detail and actually teaches you what the title says.
The only issue I encountered in the book were the charts and graphs in Chapter 2, "LocalStorage Read Performance". In the print version that I received, the shading for the charts made it impossible to correlate the legend provided and made the data difficult to comprehend. Other than the presentation of these charts, this chapter provided good information as to how storing information on the user's machine can affect the perceived performance of your site. It helped answer the question of "How expensive is this operation really?"
Bottom Line Yes, I would recommend this to a friend