{"id":25686,"date":"2020-10-01T11:55:00","date_gmt":"2020-10-01T07:55:00","guid":{"rendered":"https:\/\/www.cs-cart.com\/blog\/?p=25686"},"modified":"2026-06-10T12:58:09","modified_gmt":"2026-06-10T08:58:09","slug":"performance-issues","status":"publish","type":"post","link":"https:\/\/www.cs-cart.com\/blog\/performance-issues\/","title":{"rendered":"How to Fix Performance Issues with CS-Cart and Multi-Vendor On Your Own?"},"content":{"rendered":"\n

Performance issues can significantly deteriorate your store perception with customers. You can sell the best-in-the-world goods and have a lucrative and a well-thought UX\/UI design, but problems with the webpage loading speed, odd add-ons behavior, or image distortion would nullify all your efforts to make your business profitable. Of course, your IT team helps you to find and fix bugs before it\u2019s too late. However, online retailers and eCommerce brand owners should have a guide to be able to quickly adopt all the rescue measures and fix bugs on their own. Our developer team gathered the most common causes of CS-Cart\u2019s poor performance and low-speed operation. With this guide, you\u2019ll be able to improve your website performance without paying a cent.<\/p>\n\n\n\n

Cache<\/strong><\/h2>\n\n\n\n

Reason<\/strong>: \u2018Rebuild cache automatically\u2019 is on.
How to check:<\/strong> Administration Panel (Top Menu) \u2192 Design \u2192 Themes<\/p>\n\n\n\n

\"Rebuild
Rebuild Cache Automatically<\/figcaption><\/figure>\n\n\n\n

This setting allows you to enable an automatic clear cache in CS-Cart. It\u2019s an important setting when you make changes to your website. However, it may affect the speed of loading pages. You should turn it off if no development is done on your website.
If you have access to the store\u2019s root directory, it is recommended to check if the local_conf.php <\/strong>file has the following line:<\/p>\n\n\n\n

$config['tweaks']['disable_block_cache'] = true<\/strong>;<\/pre>\n\n\n\n
CS-Cart caches blocks to reduce page loading time. However, the code that disables block caching could have been left by the developer by accident. Here is the way to fix it:<\/p>\n\n\n\n
$config['tweaks']['disable_block_cache'] = false<\/strong>;<\/pre>\n\n\n\n
or
\/\/ $config['tweaks']['disable_block_cache'] = true<\/strong>;<\/pre>\n\n\n\n
Images<\/h2>\n\n\n\n
Reason<\/strong>: <\/em>big-size images
How to check<\/strong>: test your website with the Google Page Speed service or right-click the picture in the browser and select \u2018Inspect Element\u2019.<\/p>\n\n\n\n
\"Inspect
The Image Link Is Highlighted in the HTML Console<\/figcaption><\/figure>\n\n\n\n
A console with the HTML code opens. The required image link will be highlighted on it. Mouse hover over the image link shows its actual size.
Images should be optimized for the web. Heavy images can affect the page loading time. It is critical for pages with lots of images.
There are services that allow you to reduce the size of the image without any visible loss of quality.<\/p>\n\n\n\n
Add-Ons<\/strong><\/h2>\n\n\n\n

Reason<\/strong>: Add-ons are not designed for a large number of entities (like products, brands, etc.). Custom themes may be unoptimized and run slow.
How to check<\/strong>: Use the debugger to check the page load speed and the number of database queries.<\/p>\n\n\n\n
\"Debugger\n\"
Add-Ons as a Reason of Poor Site Performance<\/figcaption><\/figure>\n\n\n\n
Enable debugger <\/h3>\n\n\n\n
CS-Cart has an in-built developer tool that allows you to estimate the number of queries to the database for that page.<\/p>\n\n\n\n
The root administrator of the website can activate the debugger by adding the debug parameter to the address line:
<\/code>
or
<\/code><\/p>\n\n\n\n
The debugger will be active both for the admin panel and the storefront. At this, for storefronts<\/a> using another domain name, you will need to extend the storefront URL with debug=*debugger_id*<\/p>\n\n\n\n
When you open the debugger using this way, it will display temporarily in the browser for the administrator only.<\/p>\n\n\n\n
Where to find debugger: <\/strong>Find it in the top right corner of the page with the \u2018bug\u2019 icon. <\/p>\n\n\n\n
\"Debugger\"
Debugger Is in the Top Right Corner of the Page with the \u2018Bug\u2019 Icon<\/figcaption><\/figure>\n\n\n\n
The page generation time is shown at the bottom of the page together with debugger_id
The SQL tab specifies the number of queries to the database and the query runtime. The Blocks tab shows the loading time for particular blocks on the page.<\/p>\n\n\n\n
Acceptable values may differ depending on a project. We recommend doing these checks regularly to track the state over time.<\/p>\n\n\n\n
\"Blocks\"
\u2018Blocks\u2019 Shows the Loading Time and the Memory Consumption<\/figcaption><\/figure>\n\n\n\n
Isolate the problem<\/strong><\/h3>\n\n\n\n
If the page loading time and\/or the number of database queries exceeds the desirable value, try to find the root cause.<\/p>\n\n\n\n
This can be due to an add-on that sends many queries to the database.
In projects with fewer instances to be processed, such an add-on won\u2019t significantly affect the performance and will go unnoticed. But if there are tens or even hundreds of thousands of them, the processing time may become unreasonably long, reducing the website performance.<\/p>\n\n\n\n