[wp-trac] [WordPress Trac] #21668: WordPress still does not save jpeg as progressive jpeg

[WordPress Trac]

#21668: WordPress still does not save jpeg as progressive jpeg
-------------------------------------+------------------------------
 Reporter:  _ck_                     |       Owner:
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Media                    |     Version:  3.4.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |
-------------------------------------+------------------------------

Comment (by pmeenan):

 I updated the patch to only encode JPEGs progressively.

 Progressive JPEGs are nearly always smaller than baseline in addition to
 the improved user experience and since the largest images are usually
 photos we will get most of the bang for our buck there anyway.

 PNG's and GIF's tend to inflate the size so I don't recommend touching
 them.

 There are quite a few studies on the benefits of progressive JPEGs from
 well respected developers and companies:
 [http://www.yuiblog.com/blog/2008/12/05/imageopt-4/ Yahoo's image
 optimization post from 2008] (Stoyan is now at Facebook)
 [http://calendar.perfplanet.com/2012/progressive-jpegs-a-new-best-
 practice/ Ann Roboson's article for the 2012 web performance calendar]
 [http://blog.patrickmeenan.com/2013/06/progressive-jpegs-ftw.html My work
 at Google and WebPagetest on it]
 [http://www.slideshare.net/guypod/a-picture-costs-a-thousand-words18062013
 Akamai's image optimization presentation from Velocity 2013]

 Other than the patch itself, let me know if there is anything I can do to
 help make this happen (more data, research, testing, whatever).

--
Ticket URL: <http://core.trac.wordpress.org/ticket/21668#comment:14>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software