5 ms·
Even worse, to have the delivery faster with HTTP2, the developers will have to optimize it even more than now. And we know that that phase of optimization was
by acqq 12y ago
Even worse, to have the delivery faster with HTTP2, the developers will have to optimize it even more than now. And we know that that phase of optimization was traditionally ignored by most of those who aren't Google, because it's hard and the benefits for most of the producers non-existent or non-obvious. It's economics that will work against the speedups, just like it was without HTTP2.
"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!"
- sauere 12y agoMight want to show the boss this: http://www.tagman.com/mdp-blog/2012/03/just-one-second-delay-in-page-load-can-cause-7-loss-in-customer-conversions/ http://www.tagman.com/mdp-blog/2012/03/just-one-second-delay...
- insertnickname 12y agoAren't there studies that show that slower pages decrease conversion rates though? Managers might like that... but then again, we really need these share buttons and huge image headers and 10 tracking scripts and Raptorize.
- acqq 12y agoAnd as soon as the buttons and the scripts are delivered from other servers, you effectively can't speed their delivery up. So you can't claim even the 20% you assumed at the start: "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."
- personZ 12y agoAnd as soon as the buttons and the scripts are delivered from other servers, you effectively can't speed their delivery up. 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.
- grey-area 12y ago"Do we save something? Do we win something?" 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.
- acqq 12y agoI know about buttons, but the site owners do want to run the adds, and the adds typically don't come from the same site. And the discussion is about the benefits of HTTP2 optimizations.