This works for Google because their sites load almost entirely from Googleworld.
Functioning again as a barier against net neutrality, it goes against everything that made the Internet open and great.
Much easier to throttle traffic from a website when it's actually from a website. If many websites reference the same external resources, it's harder to throttle websites individually.
"Hey boss, I need people to work on optimization of the delivery of every page of our site."
"Do we save something? Do we win something?"
"No, but to some of our clients the content will appear in three instead of four seconds, if don't use the Google analytics and the Facebook button."
"Go away!"
"Hey boss, we can't even dream to deliver the pages as Google does, let's just pay them for all the things we want to be our internet presence."
Aside from the fact that choosing to use those sorts of resources is optional, those (facebook/google+ buttons and likes, etc) are virtually always asynchronous loads -- they do not hold up the render of the root page whatsoever. So if your target is displaying the recipe in 200ms, but the Facebook button takes 400ms -- guess what, the recipe page will still be shown in entirety in 200ms.
Yes, you win at least two things by removing social links or other third party hosted code:
Security - your site is no longer liable to be hacked via the js you're including on every page. This will happen to one of these major social services, perhaps after they run out of money or are acquired by some large corporation and security becomes an afterthought. At that point millions of websites across the web will have js injected which steals data/code/credentials because they are hot loading js on every request from several domains. I expect it to be a major scandal when it hits and make people rethink including live dependencies from all over the web on a website.
Speed - users get faster page loads, which directly translates into more sales/engagement etc.
These are not at all intangible or without measurable results.
It's quite possible to have simple social buttons/links using a url and traditional web which function in pretty much the same way but send you to a page to share/like/comment instead of taking over your page with a little social popup. The real reason services like FB etc want you to include their js on every page has nothing to do with improving your user experience or making your website better, it's so that they can improve their tracking, so you'd also be doing your users a favour from that perspective too, as well as benefiting the business.
And the discussion is about the benefits of HTTP2 optimizations.
What is the point of this sort of lowbrow sarcasm, fueled by raw cynicism?
Web applications have gotten significantly more complex. From a developer perspective, managing resources separately is a lot easier than using image sprites, giant merged CSS files, etc, though such is often forced because of the known inefficiencies of HTTP. Yes, this seems like an improvement. Are there sites that have other problems? Yeah, sure, of course. That doesn't make it less of a benefit.
The point is that the modern web is an abomination. The web isn't for applications, it's for documents, but web developers refuse to acknowledge this, so they do everything in their power to circumvent how the web works (or should work) to avoid making a native application.
The world would be much better served by plain, unrendered Markdown documents (or something similar) served statically by an FTP server and rendered appropriately by the client. No JavaScript, no CSS! Just a document. In cases where this is insufficient, build something appropriate to deal with it.
Yes, because who on earth would like interactivity on their site? Can you imagine it! Not having to reload the entire page on every little interaction! Blasphemy!.... /s
I'd love it if all browsers had an 'Enable code' button or somesuch which had to be manually clicked for every page which used JavaScript. And not remembered. That'd go a long way to ensuring that JavaScript were only used where necessary.
(for that matter, books have managed to be quite remarkable for centuries, with absolutely no interactivity)
As a result page loads take at least a couple seconds on a good connection, but a 5-10 second page load isn't unheard of.
This is what we did for our own site to make it fast: http://retromocha.com/learn/how-we-made-our-website-fast/
Honestly, a lot of people could get a lot faster sites if they just put the time and effort towards making them fast. It's not even that difficult, but most don't know or care to make the changes.
Google is doing a lot to make this stuff easier, but there are plenty of things holding us back, mostly it's lack of care to make things fast by the average website.