10-02-2018, 06:46 AM
(This post was last modified: 10-02-2018, 06:46 AM by Raccoon Sam.)
(10-01-2018, 10:22 AM)Petie Wrote: For the most part, that's what we're already doing in addition to compressing the output but a site like tSR, with upwards of hundreds of images per page, typically isn't going to be the best performing. tSoR, for instance, most likely responds quite a bit more quickly and you can test tSR in the same way by enabling text mode as well. I do appreciate you running the diagnostics and sharing the results though!
well, i did some local tests and here's some results for the tSR front page assets:
3 628 869 bytes ( 3.628869 MB ) for 177 items
after recursive ImageOptim pass:
Saved 1,3 MB out of 3,2 MB. 42,1 % per file on average and up to 98,6 %
2 368 460 bytes ( 2.36846 MB ) for 177 items
Additionally, none of the CSS appears to be minified so you could shave off a few kb by doing that too I guess.
for a "quick" fix you could do this once for all images on-site (I'd like to see those numbers) during the next server maintenance, but a bit of backend work is needed if you want to integrate CSS minifiers and image optimisers into the pipeline