3 ms·
Yep :). There is some initial slowdown (from our testing, it ranges from 60 to 300 ms on average), but the benefits of being able to determine which resources y
by shawnjan8 14y ago
Yep :). There is some initial slowdown (from our testing, it ranges from 60 to 300 ms on average), but the benefits of being able to determine which resources you want to load through the properties of the browser can cause you great gains in performance. Plus, after the library has been downloaded once, the library is cached, and optimized by the JIT on every subsequent load.
- cbr 14y agoI would love to see some waterfalls or ideally real-user measurements. Actually, just a few sample pages, one with the Capturing version and one with the standard (media query) version would be helpful. I made some comparison pages myself, but I don't think they're very good: http://www.jefftk.com/test/capturing/off?ModPagespeed=off http://www.jefftk.com/test/capturing/on?ModPagespeed=off And when I ran webpagetest it didn't speed up download time on desktop or mobile (time to onload ("plt") decreased, but only because the images were postponed until after the onload event).