Content Performance Policy

Content Performance Policy
►http://yoavweiss.github.io/ContentPerformancePolicy

Therefore, there’s an increasing need for a mechanism that would give authors control over their sites, and give them the opportunity to opt-out of various features of the Web platform that are inherently slow or from behaviors that are known to irritate users and result in bad mobile user experience. These same mechanisms can be used for guarantees for content embedders as well as content blockers, and enable them to make smart descisions based on the known performance characteristics of the content.

#webperf_standard_CPP_draft_clevermarks

CPP - Lazy loading of images
▻http://yoavweiss.github.io/ContentPerformancePolicy/#lazy-loading-of-images

“Images on the page that are outside of the initial viewport can often be downloaded and delay the page’s onload event without actually being seen by the user. That issue is significantly worse on mobile, where the viewports can be very long. A lazy loading directive can be used to indicate the browser that images outside of the first few images are all lazy loaded. The browser can then act on that directive and avoid loading those images.”

#lazyload_image_standard_draft_CPP_clevermarks

CPP: A Standardized Alternative to AMP
▻https://timkadlec.com/2016/02/a-standardized-alternative-to-amp

“I like the work AMP has done from a technical perspective, and I love the ambitious goal of fixing performance on the web. Let’s find a way of accomplishing these goals that doesn’t lose some of the openness that makes the web so great in the process.”

#webperf_standard_AMP_Google_clevermarks