4 ms·
> -1% negative impact on core business metrics including conversions in our test of JPEG-XRs [...] Let’s not use JPEG-XR on the Web. Is this an overreaction, o
by dahart 8y ago
> -1% negative impact on core business metrics including conversions in our test of JPEG-XRs [...] Let’s not use JPEG-XR on the Web.
Is this an overreaction, or a subversive call to improve the decode perf of JPEG-XR? I'm certainly on the performance-is-a-feature bandwagon myself, but 1% ux impact is pretty small. And shouldn't we assume that decode perf will improve in the near future? Is there any reason to assume that this problem is permanent and unfixable?
- mediumdeviation 8y ago> but 1% impact is pretty small The best you can say here is that it’s within the margin of error, in which case the effect is so small it’s literally unmeasurable. In that case the null hypothesis still wins, and you should not switch. > Is there any reason to assume that this problem is permanent and unfixable? IE11 as tested in the article is not getting anything other than security patches. The users who use IE11 are probably also the users most affected by poor performance since they most likely have the oldest hardware.
- dahart 8y agoInteresting response, thanks. Your comment gives me even more questions, though! > The best you can say here is that it’s within the margin of error What is preventing JPEG-XR from becoming faster and a net ux positive, tomorrow or in the future? Isn't the best I can say that today's results might be a bug or fluke or a quick and dirty implementation, and not a permanent problem? > IE11 as tested in the article is not getting anything other than security patches. The title and conclusion both said we should avoid JPEG-XR on the web, not that we should avoid it on IE11. You're right, the article focused on the problem with IE11. Is it already a net positive on Edge? (The article didn't say.) Should the shim to make it work in the old browser that fewer people use really override the potential benefits on the newer browser that more people are already using? Does it seem reasonable or unreasonable to make future web decisions depend on an old browser that's on life support today and has small and declining market share?
- deleted 8y ago[deleted]
- jonas21 8y agoIt's a 1% impact to conversion rate which, if you have over $1B in annual revenue like Trivago, is quite a large amount of money. And even if you don't, taking a 1% hit to your conversion rate and hurting user experience just because you want to use a fancy new image format is probably not a good idea.
- dahart 8y agoAgreed, with all of that. It doesn’t answer my question, though, right? If the IE11 problem is temporary, and the IE11 perf gets improved next week in response to this article, then Trivago might have to do a 180, no? Even if we wait a while, IE11 usage will dwindle. Couldn’t the mere passage of time easily turn the story of JPEG-XR into a 1% or more net positive for Trivago, especially if the format is already a win on Edge? Every new technology fails to stack up to decades old standards by some metrics, yet we improve on and build new things anyway because we can see the future potential. This article isn’t acknowledging future potential. My question is what justification is there for declaring the format permanently unusable?
- jonas21 8y agoI don't think the author is saying not to use JPEG-XR for all time. They're just saying not to use it right now on production web sites.
- jbreckmckye 8y agoWithout a breakdown of the stats and methodology, we have no way to know if this result was statistically meaningful, nor whether Trivago ran any null hypothesis tests. We don't even know that there were no confounding factors - just none the author thought of. The may be a spurious figure.
- jonas21 8y agoExcept that the author claims it's a statistically significant result immediately before reporting the 1% number. The full phrase (which was truncated in the other comment) is: "we were able to statistically verify a -1% negative impact on core business metrics including conversions"