High Performance Web Sites

Praise for High Performance Web Sites;Foreword;Preface; How This Book Is Organized; Conventions Used in This Book; Code Examples; Comments and Questions; Safari® Books Online; Acknowledgments;Chapter 1: The Importance of Frontend Performance; 1.1 Tracking Web Page Performance; 1.2 Where Does the Time Go?; 1.3 The Performance Golden Rule;Chapter 2: HTTP Overview; 2.1 Compression; 2.2 Conditional GET Requests; 2.3 Expires; 2.4 Keep-Alive; 2.5 There's More;Chapter 3: Rule 1: Make Fewer HTTP Requests; 3.1 Image Maps; 3.2 CSS Sprites; 3.3 Inline Images; 3.4 Combined Scripts and Stylesheets; 3.5 Conclusion;Chapter 4: Rule 2: Use a Content Delivery Network; 4.1 Content Delivery Networks; 4.2 The Savings;Chapter 5: Rule 3: Add an Expires Header; 5.1 Expires Header; 5.2 Max-Age and mod_expires; 5.3 Empty Cache vs. Primed Cache; 5.4 More Than Just Images; 5.5 Revving Filenames; 5.6 Examples;Chapter 6: Rule 4: Gzip Components; 6.1 How Compression Works; 6.2 What to Compress; 6.3 The Savings; 6.4 Configuration; 6.5 Proxy Caching; 6.6 Edge Cases; 6.7 Gzip in Action;Chapter 7: Rule 5: Put Stylesheets at the Top; 7.1 Progressive Rendering; 7.2 sleep.cgi; 7.3 Blank White Screen; 7.4 Flash of Unstyled Content; 7.5 What's a Frontend Engineer to Do?;Chapter 8: Rule 6: Put Scripts at the Bottom; 8.1 Problems with Scripts; 8.2 Parallel Downloads; 8.3 Scripts Block Downloads; 8.4 Worst Case: Scripts at the Top; 8.5 Best Case: Scripts at the Bottom; 8.6 Putting It in Perspective;Chapter 9: Rule 7: Avoid CSS Expressions; 9.1 Updating Expressions; 9.2 Working Around the Problem; 9.3 Conclusion;Chapter 10: Rule 8: Make JavaScript and CSS External; 10.1 Inline vs. External; 10.2 Typical Results in the Field; 10.3 Home Pages; 10.4 The Best of Both Worlds;Chapter 11: Rule 9: Reduce DNS Lookups; 11.1 DNS Caching and TTLs; 11.2 The Browser's Perspective; 11.3 Reducing DNS Lookups;Chapter 12: Rule 10: Minify JavaScript; 12.1 Minification; 12.2 Obfuscation; 12.3 The Savings; 12.4 Examples; 12.5

Steve Souders arbeitet als Chief Performance Yahoo! und hat innerhalb des Unternehmens an vielen Plattformen und Produkten gearbeitet. Er führte das Entwicklungsteam von My Yahoo! an, bevor er seine aktuelle Position antrat. Als Chief Performance Yahoo! hat er eine Reihe "bester Praktiken" entwickelt, um Websites schneller zu machen. Bevor er zu Yahoo! kam, arbeitete Steve für verschiedene kleine und mittelgroße Startups, darunter auch zwei Unternehmen, die er selbst mit gegründet hat: Helix Systems und CoolSync. Er hat auch bei General Magic, WhoWhere? und Lycos gearbeitet. In den frühen 1980ern fing sich Steve den Artificial Intelligence-Virus ein und arbeiete für verschiedene Unternehmen im Bereich Machine Learning. Er besitzt einen B.S. in Systems Engineering von der University of Virginia und einen M.S. in Management Science and Engineering von der Stanford University.