I am going mad today!

I use wpsmush it.
I did not notice it earlier but today.
I uploaded an optimized image 800×533 sized 17.1 KB and when I published the post a thumbnail (700×357) was made. The new image was 32 KB…

Damn, WTF?

Here are the two:
http://ss-img.styzic.com/2014/09/iPhone-6-Screens-Delay.jpg
http://ss-img.styzic.com/2014/09/iPhone-6-Screens-Delay-700×357.jpg

The code for wordpress default compression by Christopher was somehow not working. The plugin “WP Resized Image Quality” did it and its okay now!

The thumbnails are still not progressive !
Mod_pagespeed does nothing.

You likely have a conflict between the methods being used.

For example when I upload a 745×483 30kb file (size on server; actual size is 24kb); the resize plugin I’m using (to make “larger” images only) along with functions quality setting of “50”, the resulting 700×357 thumb is 23.57kb on server, 1074×483 is 38.25kb; 326×235 is 10.74kb. “Actual” sizes are lower (I’m looking via my ftp tool.)

For example, the orig. 745×483 image is 24.1kb, but 28kb on disk. 30kb on unix server.

I found smushit didn’t help me.

mod_pagespeed does make my images progressive once they are cached (meaning the images seen in the page source have the pagespeed modified file names).

• This reply was modified 11 years by simchris.
• This reply was modified 11 years by simchris.

Also, anecdotal, smushit doesn’t work with SSL/https, so the ewwoptimizer is better choice if you can compile the correct binaries on server. I have not yet tested this, but was told this the other day as part of our overall testing for moving everything to SSL/https starting October 1 (coming up quick).

I can do the optimization part @Chris but I fail when making it compressive. As you told earlier, godaddy supports mod_pagespeed. So I added a line in htacces to convert images to progressive but nothing happens. Even the url of the image doesn’t changes.

Check with GoDaddy support; they may not have that option activated. Remember their servers host thousands of sites PER server, so they have to limit certain features for anything using system resources.

Hmmm… GoDaddy seems to have removed the page in their support “what features from mod_pagespeed does GoDaddy support….” … not helpful.

When you look at your page source do you even see the mod_pagespeed code at bottom, and signal, etc. ?

You should contact GoDaddy, as mod_pagespeed might not work from sub-domain, or you may need to setup domain mapping in the config file which tells mod_pagespeed it can load stuff from subdomain of main domain.

see stack overflow item on this topic
http://stackoverflow.com/questions/21617388/mod-pagespeed-with-multiple-domains-or-subdomains

and RTFM
https://developers.google.com/speed/pagespeed/module/domains#shard

🙂

After playing with sub domains, Amazon CDN, etc., I found it was just simpler to load all the images locally so that things like compression, mod_pagespeed, etc. all actually work. I’d rather have the compression, progressive convert, for faster load than the tiny fraction faster load via subdomain or sub->CDN.

Frankly, a lot of that works if you are CNN or TIME magazine, but for most “small” sites and blogs, not so much.

But, this is the point of testing all the options then evaluating benefits vs drawbacks. I spent the entire month of January this year doing nothing but this kind of thing. Now I’ve gotten a tad cynical about it.

I look forward to all this shite being in the past, as it’s brain numbing. 🙂

• This reply was modified 11 years by simchris.

Thanks @Chris 🙂

Done without mod_pagespeed upto some extent. !