4 ms·

That is not the typical use case. As web engineers one of our goals is to make websites faster. Speed is a very important UX. Also unless you have a fast websi

That is not the typical use case. As web engineers one of our goals is to make websites faster. Speed is a very important UX. Also unless you have a fast website, people will drop off your site and google won't rank you. No point of having great images with good EXIF data if people never see the image. For photography websites, it does make sense to keep it but in general no point wasting those extra bytes which add upto GBs in wasted bandwidth.

polote 9y ago
Removing EXIF data won't make your website faster lol. You should find other ways to achieve your goals ;)
- ShirsenduK 9y ago
  Even when your webpage has over 100s of images? Which is the case for listing pages of e-commerce sites, video sites, social networks etc. As a frontend engineer, I find every way to achieve my goals as every ms matters :).
  - onion2k 9y ago
    Even when your webpage has over 100s of images? On a page with 100s of images removing the EXIF data from all the images would very likely have less of an impact than removing 1 image. Optimising is good, but you need to concentrate on optimising the right things. Start with the biggest impact and work downwards; chances are you'll never get to the point where stripping EXIF data makes a measurable difference. Besides, if you're worried about every ms then you wouldn't implement a website that loads hundreds of images on to a single page in the first place.
  - pmlnr 9y ago
    100s of images are 99% lazy-loaded, so not a concern. Get rid of the JS bloat instead, which doesn't effect the download speed at all, yet cripples the receiving box with the client-side rendering.
- deleted 9y ago
  [deleted]
- deleted 9y ago
  [deleted]
conradk 9y ago
I disagree that as web engineers, our goal is to make websites faster. Our goal is to make a website that suits the customer's needs. Sometimes, that can even mean making a website slower. I've had that request before because end users were surprised that the site loaded so fast. We made stuff slow on purpose so that the user thinks we are crunching data hardcore and giving their request some real thought before presenting the results. Sure, if the customer asks for ultimate speed and explicitly does not care about image metadata availability, then removing that metadata is fine. But otherwise, removing those few bytes probably won't change how fast your website loads by a significant amount. You're better off working on caching, reducing TTFB, automatically adapting image size to screen size, spriting icons with http1, server push with http2, gzipping, reducing the size of Javascript/CSS and working on perceived speed. This will probably be orders of magnitude more useful to users than removing image metadata. And it won't remove that useful information from images.
- ShirsenduK 9y ago
  Wow! I primarily work on consumer facing web products where speed does play a big part but glad to know where you are coming from. I have not had such request or perspective. :) Thanks for sharing your experience. Agree, that its not the first thing you should focus on. But saying you should not do it is what I was protesting. When you run your site through speed analysis tools like the site posted or WebPageTest(my favourite), you do get a set of tasks based on priority and removing exif data is generally low and I am not advocating against that.
- dmd 9y ago
  I've had such requests too. We had a system that returned query results in a few ms, and people rated it as untrustworthy, not valuable, etc etc. We added a fancy "computing... thinking... validating..." interstitial, and suddenly everyone loved it. It was literally just an animated gif with a meta refresh redirect.
- warrenm 9y ago
  >I disagree that as web engineers, our goal is to make websites faster. Our goal is to make a website that suits the customer's needs. The overwhelming majority of the time, to "make a website that suits the customer's needs" == make it faster
syrrim 9y ago
Recall that EXIF data is textual, and therefore no larger than kilobytes in contrast to the megabytes that JPEGs otherwise take up. While this may eventually add up to gigabytes of bandwidth, it will only be after downloading terabytes of JPEGs. One can imagine a variety of small things that are only useful to a minority of visitors, and go unnoticed by the rest. "alt" attributes on images are one example, that are often used by the blind, but are mostly unused by anyone else. Do you think provisions for the blind should be removed, due to wasting (tiny amounts of) data?
- ShirsenduK 9y ago
  When I spoke about bandwidth it was about the server. I should have made it more clear. Those costs add up over months. The alt tags are VERY important for SEO purposes.
  - tolien 9y ago
    The same applies whether it’s the server or user bandwidth, the volume used by EXIF data is going to be tiny compared to the relatively incompressible image data you’re shifting.

polote 9y ago

Removing EXIF data won't make your website faster lol. You should find other ways to achieve your goals ;)

ShirsenduK 9y ago
Even when your webpage has over 100s of images? Which is the case for listing pages of e-commerce sites, video sites, social networks etc. As a frontend engineer, I find every way to achieve my goals as every ms matters :).
- onion2k 9y ago
  Even when your webpage has over 100s of images? On a page with 100s of images removing the EXIF data from all the images would very likely have less of an impact than removing 1 image. Optimising is good, but you need to concentrate on optimising the right things. Start with the biggest impact and work downwards; chances are you'll never get to the point where stripping EXIF data makes a measurable difference. Besides, if you're worried about every ms then you wouldn't implement a website that loads hundreds of images on to a single page in the first place.
- pmlnr 9y ago
  100s of images are 99% lazy-loaded, so not a concern. Get rid of the JS bloat instead, which doesn't effect the download speed at all, yet cripples the receiving box with the client-side rendering.
deleted 9y ago
[deleted]
deleted 9y ago
[deleted]

conradk 9y ago

I disagree that as web engineers, our goal is to make websites faster. Our goal is to make a website that suits the customer's needs. Sometimes, that can even mean making a website slower. I've had that request before because end users were surprised that the site loaded so fast. We made stuff slow on purpose so that the user thinks we are crunching data hardcore and giving their request some real thought before presenting the results. Sure, if the customer asks for ultimate speed and explicitly does not care about image metadata availability, then removing that metadata is fine. But otherwise, removing those few bytes probably won't change how fast your website loads by a significant amount. You're better off working on caching, reducing TTFB, automatically adapting image size to screen size, spriting icons with http1, server push with http2, gzipping, reducing the size of Javascript/CSS and working on perceived speed. This will probably be orders of magnitude more useful to users than removing image metadata. And it won't remove that useful information from images.

ShirsenduK 9y ago
Wow! I primarily work on consumer facing web products where speed does play a big part but glad to know where you are coming from. I have not had such request or perspective. :) Thanks for sharing your experience. Agree, that its not the first thing you should focus on. But saying you should not do it is what I was protesting. When you run your site through speed analysis tools like the site posted or WebPageTest(my favourite), you do get a set of tasks based on priority and removing exif data is generally low and I am not advocating against that.
dmd 9y ago
I've had such requests too. We had a system that returned query results in a few ms, and people rated it as untrustworthy, not valuable, etc etc. We added a fancy "computing... thinking... validating..." interstitial, and suddenly everyone loved it. It was literally just an animated gif with a meta refresh redirect.
warrenm 9y ago
>I disagree that as web engineers, our goal is to make websites faster. Our goal is to make a website that suits the customer's needs. The overwhelming majority of the time, to "make a website that suits the customer's needs" == make it faster

syrrim 9y ago

Recall that EXIF data is textual, and therefore no larger than kilobytes in contrast to the megabytes that JPEGs otherwise take up. While this may eventually add up to gigabytes of bandwidth, it will only be after downloading terabytes of JPEGs. One can imagine a variety of small things that are only useful to a minority of visitors, and go unnoticed by the rest. "alt" attributes on images are one example, that are often used by the blind, but are mostly unused by anyone else. Do you think provisions for the blind should be removed, due to wasting (tiny amounts of) data?

ShirsenduK 9y ago
When I spoke about bandwidth it was about the server. I should have made it more clear. Those costs add up over months. The alt tags are VERY important for SEO purposes.
- tolien 9y ago
  The same applies whether it’s the server or user bandwidth, the volume used by EXIF data is going to be tiny compared to the relatively incompressible image data you’re shifting.