How to enable ionCube loader from your WHM using easyapache

ionCube was founded in 2002, and introduced tools to protect software written using the PHP programming language from being viewed, changed, and run on unlicensed computers. The tools use the technique of compiling to bytecode prior to encoding so that source code is eliminated, and runtime overheads are reduced. A PHP extension called the ionCube Loader handles the reading and execution of encoded files at run time.

PHP scripts can be easily read, changed and run on any PHP enabled system. Encoding PHP offers important benefits.

Product Developers: protect and license your code before distribution. Time restricting is ideal for protecting evaluation copies, and server/domain based locking helps secure revenue from multiple domain deployments.

Website Designers: protect your creative work and a revenue stream from future script updates.

Enterprise Customers: successfully enforce internal change control policies by avoiding untracked software tweaks that may get lost on a site reinstall or server move.

Website Owners: hide sensitive data and protect scripts from unauthorised changes that may go unnoticed indefinitely, and be a serious security and data protection risk.

You can easily enable ionCube loader on your machine in you have a cPanel licence by following these next steps:

Login into your WHM account.

Go to easyspache.


Customize the Currently Installed Packages

Go to PHP Extensions and search for ionCube

You will find the module for all available PHP versions (in my case, 5.5 and 5.6).


Install the version of the loader you need (I have installed ionCube5)

Click Next to Review, then press Provision.


Now Apache will rebuild, so it may take a few minutes.

After completion, you will receive the confirmation message.


You can now restart Apache server¬†just to make sure and that’s it.

How to disable mod_pagespeed from your .htaccess file

PageSpeed mod_pagespeed is a module for Apache server which is just like a plugin, and since Apache is different from IIS, it cannot be installed on IIS servers.

As for what it does, it does multiple things:

  • Minifies (removes whitespace, comments, etc) or in other words compresses external CSS and JavaScript
  • In addition to minifying JS, it combines multiple external JS files into one JS file which causes less http requests or round trips so the page loads faster
  • Optimizes the cache for the files. Every http header has a cache information, or in other words, for how long should the browser keep the resource, mod_pagespeed optimizes this number
  • Uses the idea of URL fingerprinting for the new JS files. Basically when the mod_pagespeed optimizes and combines multiple JS files into one file, this temporary file is stored somewhere on the server, however, its filename is generated from the content of the JS files using checksum algorithms such as MD5. What this allows to do is that mod_pagespeed tells the browser to store the JS file for a long time (sets a long cache time), however as soon, as the developer will change the content even in one of the JS files, since the checksum of all the files will change, mod_pagespeed will generate a new temp JS file which will have a different URL compared to the old one. So, when the user who has saved the old combined JS file will try to reload the page, since the URL of the new JS file will be new, it will force the browser to download it again. So essentially this is one way to do cache control.
  • Minifies HTML

One downside however is that it uses much more CPU resources on the servers.

Another downside is that it’s incorrectly optimising the css and also constantly caching so testing updates is painful.


To disable it,  you need to add this lines in your .htaccess file:

<IfModule pagespeed_module>
ModPagespeed off

This will do the trick and disable mod_pagespeed for your hosting account.