Better HTTP/2 Prioritization for a Faster Web
"Web pages are made up of <i>dozens (sometimes hundreds) of separate resources that are loaded</i> and assembled by the browser into the final displayed content."<p>Could that be the reason that that the web needs to be "faster" (despite tremendous advances in CPU, storage, bandwidth and network speeds)?<p>The dozens (sometimes hundreds) of separate resources are loaded <i>by default</i>.<p>What is their purpose?  Where do they come from?  Are all of them necessary?<p>What if an advanced user could tell the browser to only load certain resources from certain sources?<p>For example, maybe skip certain ads and tracking, as specified by the user.<p>Perhaps do not load the Facebook "Like" buttons (images), but load all other images.<p>Control exactly which Javascripts to load.<p>In <i>addition</i> to the options that browsers now provide, provide more fine-grained controls.<p>Could that make the web faster?<p>A bonus would be if these user-defined, fine-grained browser settings could be saved in a portable, interoperable format, e.g. to external media, in addition to being able to save them to "the cloud" (which may be servers run by advertising-supported browser authors).  Browser authors do not need to know which resources users may wish to block.