X-Cart:Performance tips

From X-Cart 4 Classic
Revision as of 15:59, 21 April 2011 by Vladimir Gurinenko (talk | contribs) (Added Checking MD5 of compiled templates.)
Jump to: navigation, search

If your online store has started getting slow, you can try speeding it up. This article gives an extensive list of tweaks that you can try applying to your store and a tool for measuring the performance optimization results.

Optimization settings

X-Cart 4.4or above

Since version 4.4.2, X-Cart features 9 new options in the Optimization settings section. (To open the Optimization settings section, select Settings -> General on the Administrative menu and then scroll down to Optimization settings.)

If you experience performance problems, you may want to try turning off some or all of these switches.

Be aware that certain options boost the performance by disabling some features. To find out what you get and what you give up, place the mouse pointer over the question mark by an option and read the hint that appears.

The Use speed-up tool for Javascript and Use speed-up tool for CSS check boxes enable the optimization for the operations of assembling and displaying of code for JavaScript and CSS. For more information on using these options, please read CSS and JavaScript optimization.

Use caching frequently used data to speed up future requests for that data. The caching options are self-descriptive, but take a look at the note to see when to use and when to avoid using certain options.

Generate X-Cart cache every N hour(s). The recommended value is 24. To disable using cache, edit config.php and change the value of the USE_DATA_CACHE constant to false.

Use cache for language variables. Use this option if you have a lot of memory dedicated to your PHP engine. This option can slow down your shop pages in some cases. Please, check your pages before keeping this option enabled in the production mode. If you have a multi-language store, make sure all used labels are defined for each language if the option is enabled.

Disable unnecessary logs and checks.

Do not check if templates are changed (Smarty compile_check). Once the application is put into production (i.e. the templates are not going to be changed any more), the compile check step is no longer necessary. Just keep in mind that if you change a template file while this option is enabled, you will not see the change, as the template is not going to be recompiled. Enable this option for maximized performance.

Do not delete empty strings in templates. The recommended value is ON. Prior to showing a compiled Smarty template, you can choose to remove two or more successive empty strings, if there are any. With a large number of templates to be displayed, this can cut the productivity. Disable this option if you have problems with the appearance of your page.

Do not log changes in PHP configuration settings. The recommended value for production mode is ON. Disable this option if you want to track changes in PHP configuration settings. The changes will be logged in files like var/log/x-errors_env-<date>.php. It can be useful during development or during problem research phase.

Check only main category condition for products selection and product search. You may want to enable this option if you have many additional product categories.

Do not check product's category availability and product's category membership on all the product related pages. If you select this check box, you will have to define product availability and product membership individually for each product. This affects the Feature comparison product list, Featured products, Product search, Special offer pages and Manufacturer products. Enable this option if you have many categories and problems with the performance of your store. Please note that the 'Order by' field defined on the category details page will not be used with this option enabled.

Please note that in some cases selecting this option can slow down your shop pages instead of speeding them up, so please check your pages before enabling this option in the production mode.

Use simple sorting by productid on all the product related pages. Enable this option if you have problems with the performance of your store. Please note that with this option enabled the Sort by feature will not be available on all the product pages. This affects the Feature Comparison product list, Featured products, Product search, Special offer pages and Manufacturer products.

Do not use product international descriptions on all the product related pages. The recommended value for a single-language store is ON. Enable this option to search in the default language. Please note that with this option enabled international descriptions will not be used on all the product pages. This affects the Feature Comparison product list, Featured products, Product search, Special offer pages and Manufacturer products.

Caching templates

To further boost the performance of your store, in your templates use {include_cache file="some_template.tpl"} instead of {include file="some_template.tpl"}. This caches the template file and then serves the saved copy instead of generating a new one every time the template is requested in the future.

To ensure the correct appearance of your template, make sure to pass all the variables used in the template as parameters of the include_cache() function.

Checking database integrity

Run this check periodically, as garbage in the database can significantly slow down the operation of the entire store. For more information, please read Checking database integrity.

Checking MD5 of compiled templates

Checking MD5 of compiled templates prevents the use of unauthentic templates, which could be potentially harmful. Nevertheless, you can disable this check and thus boost the overall performance of your store For more information on using this option, please read Security options.

Moving images to file system. For v.3.5.x and 4.0.x

For each image you want to display, a separate connection has to be opened to your database. Even if it's only one image per page, doubling the connections to the database isn't fun to think about.

Each time you do <img src="image.php?imageid=345"> or something similar, that's a separate request to the server, with PHP going to receive that image from the database. Even if you do use scripting to grab images from a non-public branch of your file tree, just using file reading creates very, very little overhead, while hitting the database creates a lot. Just connecting to the database alone, without any queries, is something which already takes a significant amount of server time (more in the sense of processing cycles than actual time).

Storing your images in database tables is not recommended from the performance point of view. Our advice is to place images into the file system. It can easily be done by modifying a single setting in the control panel. For details, study X-Cart:Images Location Management page.

After that modify original .htaccess file (in /files directory) and change the code to:

<FilesMatch "\.(gif|jpe?g|png|GIF|JPE?G|PNG|)$">
Allow from all
Deny from all

Toggling off tracking statistics

It is strongly recommended you disable all the modules and functions that you do not need. If you experience problems with X-Cart performance, one of the first things you should do is disable the module Advanced Statistics. This module significantly slows down X-Cart by storing statistical information in the database.

In X-Cart v3.5.x or later:

Advanced Statistics can be disabled via the 'Modules' section of X-Cart's Admin area.

In X-Cart v3.4.x:

in the customer/auth.php file, make the line

include "../include/atracking.php";

as follow:

#include "../include/atracking.php";
Note: As an alternative to "Advanced Statistics" module, you can enable the "Google Analytics" module to use Google Analytics system with your store.

Cleaning statistics tables

For v.3.5.x and 4.0.x.

In the admin back-end of x-cart: ‘Summary’ page - > ‘Statistics clearing’.

For v.4.1.x: Statistics can be cleared via admin area: 'Summary' page, section 'Tools/Statistics clearing'.

Optimizing SQL tables

X-Cart stores its data in database tables, and over time these tables may become fragmented/less organized. This is especially true if you make changes to the data in your store's database tables directly.

In X-Cart v.4.1.x or later:

X-Cart provides a tool that allows you to defragment the database and reclaim the unused space: 'Optimize tables'. For details on using this tool, see X-Cart: Advanced Tools page.

In X-Cart v.3.5.x and 4.0.x:

Execute the following sql query for each x-cart table

OPTIMIZE TABLE <table_name>;

where replace <table_name> with the name of a table. You will find the list of x-cart tables using the next sql query:


Optimizing CSS

To optimize CSS, you can take advantage of the load_defer and load_defer_code Smarty tags. Both these tags handle the operations of assembling and displaying cached CSS code. For more information on using these tags, please refer to CSS and JavaScript Optimization.

Optimizing JavaScript

To optimize JavaScript, you can also use the load_defer and load_defer_code Smarty tags to enable assembling and displaying cached JavaScript code. For further details on using these tags for JavaScript, please refer to CSS and JavaScript Optimization.

Caching images

When user views the 'Product details' page, X-Cart serves reduced-size copies of the product image until user requests the full-size copy of it. This saves bandwidth and cuts the page load time. Image caching requires GDLib (a GD extension for PHP) installed and properly configured on the server. You can manually generate image cache by clicking Re-generate image cache in the 'Maintenance' section of the admin area. For more information on setting up product images, please refer to Advanced Tools.

Generating HTML catalog

Additionally, it is advisable to create HTML catalog. After generation of HTML catalog, your customer zone is presented as a set of static pages linked together without actual PHP scripts execution and database queries. It may significantly lower loading of your server.

Compressing HTML source

You may try to put the following lines in the php.ini file:

output_handler =
zlib.output_compression = On
zlib.output_compression_level = 1

You can put any figure in the compression level between -1 and 9, just muck around and see what works best for your particular store.

Or if you are using Apache server and .htaccess files are enabled you may try to add

php_flag zlib.output_compression On

to the .htaccess in the store root.

Installing Zend Optimizer

The Zend Optimizer is a free application that runs the files encoded by the Zend Encoder and Zend SafeGuard Suite, while enhancing the running speed of PHP applications. Many scripts require that you have Zend Optimizer installed so you are able to run them on your server while decrypting and running them on-the-fly while increasing runtime performance.

Install additional Apache modules (optional)

The idea behind GZIP-encoding documents is very straightforward. Take a file that is to be transmitted to a Web client, and send a compressed version of the data, rather than the raw file. Depending on the size of the file, the compressed version can run anywhere from 50% to 20% of the original file size.

In Apache, this can be achieved using Content Negotiation, which requires that two separate sets of HTML files be generated: one for clients who can handle GZIP-encoding, and one for those who can't. This solution sends gzip-encoded files to clients who understand them, but does not allow for the compression of dynamically-generated pages.

A more graceful solution is the use of mod_gzip, one of the many additional modules available for Apache. We consider it one of the overlooked gems for designing a high-performance Web server. Using this module, configured file types will be compressed using GZIP-encoding after they've been processed by all of Apache's other modules, and before they're sent to the client. The compressed data that's generated reduces the number of bytes transferred to the client, without any loss in the structure or content of the original, uncompressed document.

You may ask your hosting administrators to install the necessary compression module: mod_deflate (Apache 2.0.x) or mod_gzip (Apache 1.3.x).

Slow down SE crawlers

Search engines may crawl your site and cause a performance degradation. You may slow down the robots crawling your site by adding the following line into robots.txt file (in the root of your web site):

User-Agent: *
Crawl-Delay: 10

Use Content Delivery Networks like MaxCDN

Author: Jon Peters from WebsiteCM.com

(Thank you, Jon, for contributing articles for X-Cart Knowledge Base!)

What is MaxCDN - see here

Setting up a CDN for your medium to large X-Cart site will help improve its loading times across the world by delivering static content from the MaxCDN server located closest to your customer. Google uses site loading times as a factor in search engine ranking so for sites with steady sales and traffic we recommend implementing a CDN like MaxCDN.

Once your CDN has been established, you can integrate x-cart as follows:

Open smarty.php


Replace with: (Be sure to replace CdnUrl.example.com with your CDN Url)

// WCM - MaxCDN Implementation
if ($_SERVER['HTTPS'] != 'on')

Performance improvement patches for X-Cart

Improvement: *PERFORMANCE* Languages cache generation is optimized.

This improvement is aimed to resolve the following issue: Index page (home page) loads slow.

X-Cart 4.3or above

For versions from 4.3 branch, download and apply the following patches:

X-Cart 4.4or above

For versions from 4.4 branch, download and apply the following patches:

Note: This improvement patch is already included into X-Cart 4.4.2 release.


You can further assess the effect made by adjusting certain settings on the page load rate using Firebug, a FireFox extension. For more information on installing and using this tool, please visit Firebug website.