responsive-and-fast-implementing-high-performance-responsive-design

Recommendations

Info

Summarizing Responsive JavaScript and CSS 32 5. HTML Over-Downloading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 DOM Bloat 33 Conditionally Loading HTML 34 Prioritizing Critical Resources 36 Summarizing Responsive HTML 36 6. RESS and Adaptive Delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Adaptive Delivery 37 Adaptive Delivery versus Responsive Web Design 38 Implementing RESS 39 RESS Content 40 RESS Granularity 40 RESS Detection 41 RESS for Resources 41 RESS and Caching 43 First-Party Cache 43 Third-Party Cache 44 Summarizing RESS and Adaptive Delivery 46 7. Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 What to Use When 48 The Bigger Performance Picture 49 Responsive and Fast 49 iv | Table of Contents
CHAPTER 1 Quick Introduction to RWD Background Mobile took the web by surprise. The fast growth of cellular devices (and subsequently feature phones) was impressive by itself, only to be compounded by subsequent disruptions such as the launch of the iPhone, the rapid and diverse growth of Android, and the emergence of tablets, led by the iPad. And the next wave of devices is already well on its way, with voice-based systems, smart watches, connected eyeglasses, and even connected mirrors and fridges. As is often the case, many organizations initially chose to outsource the handling of this brave new world. Building in-house knowledge and technology is hard and time-consuming, and nobody knew for sure whether mobile devices were just a fad, or whether some new revolution would take over before the current one settled down. Even organizations that kept mobile internal usually created separate teams to handle it, separating this risky new turf from the more stable, revenue-generating desktop business. For the mobile web, this separation manifested as separate mobile sites, known as mdot (or m.) sites. Organizationally, this separation was a good way to let independent teams work effectively. Technically, a separate mobile website was easier to tune for mobile displays and capabilities. Lastly, for many organizations, “mobile strategy” included both mobile web and native mobile apps, and mdot sites were aligned more closely with apps than with the desktop sites. 1
Page 2 and 3: 5 seconds is the difference between
Page 4 and 5: Responsive & Fast by Guy Podjarny C
Page 8 and 9: Dedicated Website Challenges While
Page 10 and 11: appear as though they were written
Page 12 and 13: Cellular connections, however, chan
Page 14 and 15: strategic solutions for them. It’
Page 16 and 17: Figure 3-1. Distribution of bytes o
Page 18 and 19: Although the picture looks smaller
Page 20 and 21: CSS Responsive Images I previously
Page 22 and 23: Standardizing Responsive Images If
Page 24 and 25: Art Direction use case). The srcset
Page 26 and 27: In this example, the src attribute
Page 28 and 29: enough, since chances are the image
Page 31 and 32: CHAPTER 4 JavaScript and CSS Over-D
Page 33 and 34: Given the page-wide impact CSS and
Page 35 and 36: if (document.documentElement.client
Page 37 and 38: These additional rules can be inclu
Page 39 and 40: CHAPTER 5 HTML Over-Downloading By
Page 41 and 42: Content That Always Shows if ( win
Page 43 and 44: CHAPTER 6 RESS and Adaptive Deliver
Page 45 and 46: 2. Separate the cached responses re
Page 47 and 48: RESS Detection After you’ve decid
Page 49 and 50: If you plan on using a single RESS
Page 51 and 52: The Vary header instructs the cache
Page 53 and 54: CHAPTER 7 Summary Over the course o
Page 55 and 56: Use RESS for removing big chunks of
Page 57:
Wait. There’s More. 4 Easy Ways t
show all

responsive-and-fast-implementing-high-performance-responsive-design

Create successful ePaper yourself

Delete template?

Save as template?