1000 FAQs, 500 tutorials and explanatory videos. Here, there are only solutions!
Setting up a cache engine on a CMS/Optimising a website
When we detect that your site is consuming more resources than the other sites on the same server, we analyse the case and often we find that a simple change of a request or setting will optimise your site and the server as a whole. You will then be contacted by email about it and we will explain the steps to take in order to correct the problem.
In this email, we will ask you to install a cache engine and this guide provides additional guidance on the subject.
WordPress: installing and activating a cache engine
For informational, un-official purposes: http://www.seomix.fr/?s=cache
Joomla 3.x: configuring the cache
Log into the administration of your Joomla CMS, then go to:
- Setup Menu -> System tab -> Cache Settings
- select conservative or progressive Cache (Joomla developers recommend the progressive cache, but you should test the effectiveness of both modes)
- Select the maximum validity time, in minutes, for a cache file before it is refreshed. 60 minutes if your site is changed regularly. 20000 for a static site which changes only once or twice per month...
- Save and purge the cache manually via the System menu if needed
PrestaShop 1.5.x: configuring the cache
Apply CHMOD 777 permissions to your .htaccess file and log into the administration of your PrestaShop CMS:
- Advanced Settings menu -> Performance
- Smarty block -> enable cache
- CCC Block -> enable the 5 options
- Ecryption Block -> leave the first option (Rijndael)
- Cache Block -> "Use cache" -> "File System" value = 1
Restore limited rights (e.g. 755) to your .htaccess file.
Magento 1.7.x: configuring the cache
The cache is automatically turned on. To purge, go into the Magento admin under System -> Cache Management
Contao 3.2.x: configuring the cache
The cache is managed in the back office modules -> System -> Configuration -> Cache Mode -> Use the system cache and browser
Drupal 7.x: configuring the cache
Log into the administration of your CMS then:
- Configuration Menu -> Performance
- "Cache pages for anonymous users" under Caching