By shulemj - Thu 6 Jul 2017
|
Google is telling me that my site is over-bloated, mostly because of image compression. Anything we can do within the Cartis settings to remedy?
|
By Tiggywiggler - Sat 8 Jul 2017
|
Shulem,
The subject is discussed here:
https://stackoverflow.com/questions/5451597/how-does-googles-page-speed-lossless-image-compression-work
|
By shulemj - Sun 9 Jul 2017
|
I've seen plenty discussions online in this regard, but I am not familiar with all the methods in image.aspx and its controls. How difficult would integration be?
|
By Supermac - Mon 10 Jul 2017
|
I use to optimize images before to upload them to a webserver. I do that using a free tool named Riot you can download from web. It can deflate filesize dramatically removing meta information and other unuseful data and managing the compression of common web image file format. You could try a threatment of your images with Riot to see if that makes Google happy.
|
By shulemj - Mon 10 Jul 2017
|
Thank you Supermac, but I was hoping that since Kartris applies modification on the fly (resizing), it could also apply the optimization.
|
By Supermac - Tue 11 Jul 2017
|
Impossible is nothing, but consider that image compression is a further work for webserver and it surely will takes time to be executed every time an image is requested. A batch threatment of an images' folder is matter of few seconds and is forever.
|
By Tiggywiggler - Sat 28 Oct 2017
|
Hello Shulem,
I know this is an old post, but in the Google Insights (Speedtest) page you will find a link at the bottom of the page to the resources that Google thinks are bloated. These are the corrected files.
If the files are static files (ones not delivered by Kartris) you can simply replace your existing static files with the ones that the Google Insights (Speedtest) page has produced for you for a quick improvement.
If the issue is with the dynamically created files, then the issue is a bit harder to fix as that lies within the kartris engine. Do you have an exact example (you can link Google Insights results pages), and then we could take a look?
|
By shulemj - Sun 29 Oct 2017
|
Thanks for the info. I will look into it.
|