[TYPO3-dev] Speed up your Typo3 website by optimizing images

[Fabien Udriot]

 > Maybe also this helps:
 > -trim          Drop non-transformable edge blocks

 From the man: Rather than having a strange-looking strip along the right and/or bottom edges of a 
transformed image, discard any untransformable edge pixels.

I run the script without -trim and re-run it with -trim afterward. No difference in term of size. I 
need maybe a bigger sample of images to find a "non-transformable edge blocks" specimen. :)

Btw, jpegtran is for "jpeg transformation" - a lossless transformation of JPEG files which is not 
always the case e.g. -trim (strip edges)

Have a nice day.

Fab.


Daniel Bruessler a écrit :
> Hello,
> 
> == convert -strip ==
> how much meta-data is it, what is stored in each of the files? (wc -c)
> 
> == jpegtran -optimize ==
> I see -optimize stands for "Optimize Huffman table". the
> Huffman-algorithm ;-)
> 
> This does really help much, doesn't it?
> 
> Maybe also this helps:
> -trim          Drop non-transformable edge blocks
> 
> Cheers!
> Daniel
> 
>> Hi,
>>
>> I tried to run the script but faced some compatibility problems on
>> NetBSD / FreeBSD system. This is due to some little nuance between Linux
>> and *BSD command. I brought changes with the hope it is more Unix
>> compliant.
>>
>> For example this line does not work and makes the script crash.
>> size1=$(stat -c%s "$i")
>>
>> I changed to:
>> size1=$(ls -al "$i" | awk '{ print $5 }')
>>
>> Btw, I have improved a little bit the script by adding a recursive
>> handling of the images.
>>
>> It works now like a charm for me. I have notice a big difference size on
>> some images.
>>
>> My version is uploaded on the bugtracker
>> http://bugs.typo3.org/view.php?id=10032
>>
>> Usage:
>>
>> ./strip_image_headers2.sh test typo3temp (for testing)
>> ./strip_image_headers2.sh typo3temp (for real life!)
>>
>> Regards,
>>
>> Fabien
>>
>>
>>
>> ben van 't ende [netcreators] a écrit :
>>> Franz Koch wrote:
>>>> Hi,
>>>>> John Angel wrote:
>>>>>> What if I tell you that you can significantly speed up your Typo3
>>>>>> sites by optimizing images WITHOUT losing their quality?
>>>>> I would say it is fantastic! :) I host one site, which has over $GB of
>>>>> images. It is a pain in you-know-where to backup it. I should
>>>>> definitekly try your way ;)
>>>> adding "params = -strip" to every image processing done with TS (like
>>>> tt_content.image.20.1.file.params = -strip" is already helping a lot.
>>>>
>>>> I don't think that profiles and meta data should automatically get
>>>> removed when uploading a image to fileadmin or with DAM. Only images
>>>> directly uploaded to the uploads folder should get stripped. If you f.e.
>>>> have some kind of photo community where you would like to display the
>>>> exposure, lens, shutter settings etc. you will need the meta data
>>>> (EXIF).
>>>>
>>> Hey Guys,
>>>
>>> Uhhhh when using DAM this behaviour should automagically be overridden
>>> ofcourse.
>>> Metadata is what DAM is about.
>>>
>>> gRTz
>>>
>>> ben