JS & CSS Compressor + Image Optimization

Image Optimization features

• Optimize JPEG, PNG and GIF images
• Merge images (new and unique feature)
• Lazy load of images
• Set image dimension
• Serve scaled images
• Advanced management of image optimization
• Automatic backups of images
• Check image optimization status

Merge of Javascript and CSS files

When a user opens a page of your website, his browser downloads many page resources: HTML document, Javascript and CSS files, images, fonts and so on. The more files a page has, the slower it loads.

The Merge functionality of the extension allows combining all Javascript and CSS files from the page into one single JS/CSS file. When files are merged, a browser performs only one request to a server to download JS or CSS file of the page, instead of making hundreds of requests. Surely, such optimization significantly accelerate full page loading time.

Minify Javascript and CSS

Time spent on loading JS/CSS files depends on file size: the less the file size is, the faster page load becomes. Compression allows reducing JS and CSS file sizes by eliminating comments, line breaks, tabulation and space symbols which are not necessary for a browser to ‘read’ the code. Thereby, page loading time decreases without affecting code quality and logic.

Defer Parsing of Javascript and CSS

While rendering HTML document, a browser is downloading resources (JS, CSS and images) the way they appear in the HTML DOM.
Google PageSpeed service recommends moving declaration of JS/CSS to the end of the body, which is called Defer Parsing of Javascript/CSS. As a result, a user will see page content faster. However, we don’t recommend providing defer parsing of CSS (moving them to the end), as a visitor will see a blank page without stylesheets first, and only then a browser will apply CSS code to the HTML document

Inline small CSS

Loading of CSS or JS file has 3 stages:

• Send a request to server;
• Wait for the request to be processed at server;
• Receive response from the server;

It’s better to insert content of small CSS/JS files right into HTML document as they start working only on the 3rd stage. As a result, a page will load faster.

Questions & Answers

Is Compressor compatible with Redis and Full Page Cache?

Yes, our extension works with Redis for Magento which is used to accelerate work of Magento stores with different types of cache.
Full Page Cache is used to prepare generated cached content and thus, decrease Time to First Byte (TTF). Full Page Cache is a perfect supplement for any store and works with Compressor like a charm.

Is Compressor compatible with CDN?

Our “JS/CSS Compressor + Image Optimization” extension does not work directly with CDN. However, the extension can work with CDN the following way: after the extension have optimized images, you just need to Flush CDN Cache (or upload images to CDN manually if your CDN does not support automatic synchronization).

If you are using Amazon S3 CDN provider, then we recommend you to use our CDN Synchronizer Magento extension which keeps images up-to-date on CDN service.

I have a question about the usage of Compressoor extension

Please check the extension documentation. It has changelog, FAQ and installation guide.

Is installation free? What are the terms for support, license and refund?

Installation service is included in the license price. Support is free and lifetime. Extension updates are free and lifetime either. Refund is available within 30 days. License is per one Magento installation. Learn more: Customer Service, EULA.

I have a question about the usage of Compressoor extension

Please check the extension documentation. It has changelog, FAQ and installation guide.
You can also contact us to recieve email support.

Installation Guide

1. We recommend you to backup your store before installation
2. Go to Magento Admin and disable compilation (Systems > Tools > Compilation > 'Disable' button) and flush store cache (System > Cache Management > 'Flush Magento Cache' button)
3. Download the extension package from your account and extract the downloaded archive.
4. Copy the content of extracted folder to your store's root directory
5. Set 755 permissions on all files in lib/PotatoCommerce/ImageOptimization/tools folder. Important! Otherwise, image optimization will not work.
6. Flush store cache again
7. Log out from the backend and log in again. Important!
8. If you use compilation, then you should run compilation process (Systems > Tools > Compilation > 'Run Compilation Process' button).
9. Go to extension configuration (System > Configuration > PotatoCommerce Extensions > JS / CSS Compressor), enable and configure the extension
10. Disable native CSS and JS merge at System > Configuration > Developer.
11. Flush store cache again

To make the extension working properly on your web-server, please make sure that the following requirements are met:

JS and CSS optimization

1. All javascript errors should be eliminated before merging javascript files. Otherwise, a script with errors can break proper work of other scripts in the merged javascript file
2. If you use Apache, then mod_deflate and gzip should be enabled on your server.

Image optimization

1. exec function should be enabled
2. gdlib library should be installed
3. All files in folder lib/PotatoCommerce/ImageOptimization/tools must have '755' permissions
4. Media and Skin folders must be readable and writable by webserver user.

FAQ

After installing "Compressor" extension my store gives 404 error or a blank page.

Go to Magento Backend, Flush Store Cache (System > Cache Management> 'Flush Magento Cache' button), Logout and Login again.

After enabling "Enable Defer parsing of JavaScript" option my frontend is broken or some script doesn't work.

Go to Magento Backend, Flush Store Cache (System > Cache Management> 'Flush Magento Cache' button). Contact us if the problem persists.

How do I exclude specific scripts or CSS files from being deferred, compressed and minified?

To add an exception just add "po_cmp_ignore" attribute this way: <script type="text/javascript" po_cmp_ignore>. It will force Compressor to ignore this script.
Example of excluding file that included in layout:

skin_js
js/smartheader.js
po_cmp_ignore

Effective from 2.0.0 version of the extension, you can also use flags po_cmp_ignore_move and po_cmp_ignore_minify.
po_cmp_ignore_move ignores only merge and defer (it does not allow to move the node).
po_cmp_ignore_minify does not allow to compress content.
There is also a textarea added to the extension settings, which works same was as po_cmp_ignore flag does - it does not allow to move and compress the node. Strings which are added to the textarea, are being searched within URLs of scripts/styles, or in content if the nodes are inline (<script>...</script>, <style>...</style>).

How can I test my store performance? Can I check that your extension actually works?

We recommend using GTMetrix service. For example, you can test our demo store.

Image Optimization does not work. Why?

If image optimization does not work on your website, then we recommend you to check:

1. Please make sure that exec function is enabled
2. Make sure that Media and Skin folders are readable and writable by webserver user.
3. Make sure that all files in folder lib/PotatoCommerce/ImageOptimization/tools have 755 permissions. If it’s not, then set 755 permissions and try to start image optimization again.
4. If your server is on Ubuntu OS and previos steps did not help you, then please contact us so that we can investigate the issue on the ground.
   If your server is not on Ubuntu OS, then you should check if the applications are installed properly. To make this please do the following:
5. • Go to folder lib/PotatoCommerce/ImageOptimization/tools/unix (go to ‘64’ subfolder as well if you have 64-bit OS)
   • Run the following commands:
       ./optipng -v
       ./jpegoptim --version
       ./gifsicle --version
   • If you receive an error (for example, “segmentation fault (core dumped)”), then please refer to this article to fix this issue.

Which issues in the Google Page Speed / GTMetrix report does the extension fix?

Compressor extension is designed to fix the following issues:

• Defer parsing of JavaScript
• Enable gzip compression (for apache webserver)
• Inline small CSS
• Inline small JavaScript
• Minify CSS
• Minify JavaScript
• Minify HTML
• Leverage browser caching (partially fixed)
• Serve scaled images
• Eliminate render-blocking JavaScript
• Eliminate render-blocking CSS
• Specify Image Dimensions

Other problems can not be fixed automatically and thus can not be fixed by the extension (or by any other competitor's extension). It can be fixed only via web-server configuration and website theme improvement.

Can Compressor minify HTML?

Yes! 1.6.0 version of the Compressor extension was improved with simple HTML minification.

After extension installation there is Fatal error: Class ‘Potato_Compressor_Helper_Data’ not found in /home/www/public_html/app/Mage.php on line 547

It looks like you forgot to disable compilation before installation. If you can't go to Backend > Tools > Compilation and re-run compilation process (because of the fatal error), then you need to disable compilation manually. To do this please open config.php file in 'includes' folder. Find these:
define('COMPILER_INCLUDE_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'src');
define('COMPILER_COLLECT_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'stat');
you should comment lines like that:
#define('COMPILER_INCLUDE_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'src');
#define('COMPILER_COLLECT_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'stat');
Admin panel will be alive then. Now you need to go to Backend > Tools > Compilation and re-run compilation process. After that, everything should work fine.

Should I disable native Magento CSS and JS merge at System > Configuration > Developer?

Yes, we recommend to disable native CSS and JS merge. We don't expect any conflicts here, but native merge can slightly slow down the work of our extension. You can disable native merge of files at System > Configuration > Developer.

I need to edit a CSS/JS file. Which file should I edit - original or merged and compessed?

You need to edit original files at 'skin' folder. Do not forget to flush JS/CSS cache after all your changes of CSS files: System > Cache Management > 'Flush JavaScript/CSS Cache' button.
If you use our Full Page Cache extension, then you would need to flush cache of Full Page Cache extension as well.

How to disable Compressor Extension?

Do not disable this module at 'disable module output'! Just go to Compressor settings and set "Enable" option to "No". If you can't access the Magento backend, then you can disable the extension this way - rename file app/etc/modules/Potato_Compressor.xml to Potato_Compressor.xml.OFF

How to unistall the extension?

• Disable compilation (Tools > Compliation) if it's enabled
• Delete file app/etc/modules/Potato_Compressor.xml
• Fluch cache storage (System > Cache Management)
• Delete the following folders and files if they exist:
  • app/code/local/Potato/Compressor
  • app/design/adminhtml/default/default/layout/po_compressor.xml
  • app/design/frontend/base/default/layout/po_compressor.xml
  • app/design/frontend/base/default/template/po_compressor
  • app/locale/en_US/Potato_Compressor.csv
  • lib/Compressor
  • adminhtml/default/default/po_compressor
  • media/po_cmp_image <- do not delete this folder if your want to retain the backup of images!
  • skin/po_cmp_image <- do not delete this folder if your want to retain the backup of images!
  • media/po_compressor <- do not delete this folder if your want to retain the backup of images!
• Remove `table po_compressor_image` from the database
• Run compilation again if necessary.

JS/CSS/HTML Compressor - 2.3.1 (27 March 2018)

Image Optimizer - 2.2.0 (27 March 2018)

JS/CSS/HTML Compressor - 2.3.0 (25 December 2017)

JS/CSS/HTML Compressor - 2.2.2 (12 October 2017)

JS/CSS/HTML Compressor - 2.2.1 (06 October 2017)

JS/CSS/HTML Compressor - 2.2.0 (12 Septemer 2017)

Image Optimizer - 2.1.1 (12 Septemer 2017)

JS/CSS/HTML Compressor 2.1.0 (10 August 2017)

Image Optimizer 2.1.0 (10 August 2017)

JS/CSS/HTML Compressor 2.0.2 (11 July 2017)

Image Optimizer 2.0.1 (11 July 2017)

JS/CSS/HTML Compressor 2.0.1 (14 June 2017)

2.0.0 (06 June 2017)

1.6.1 (05 May 2017)

1.6.0 (24 Feb 2017)

1.5.1 (01 Dec 2016)

1.5.0 (13 Oct 2016)

1.4.2 (02 Aug 2016)

1.4.1 (14 Jul 2016)

1.4.0 (13 Jul 2016)

1.3.0 (09 Nov 2015)

1.2.0 (02 Jun 2015)

1.1.1 (29 Apr2015)

1.1.0 (17 Mar 2015)

1.0.3 (17 Sep2014)

1.0.2 (26 Jun 2014)

1.0.1 (28 May 2014)

1.0.0 (17 Mar 2014)