https://www.arscommunity.com/wiki/ 2026-06-14T07:35:07+00:00 https://www.arscommunity.com/wiki/ https://www.arscommunity.com/wiki/lib/images/favicon.ico text/html 2015-11-28T23:25:54+00:00 https://www.arscommunity.com/wiki/x-cart/speed-up/Layout_changes_for_better_perfomance?rev=1448753154 text/html 2015-11-28T23:25:53+00:00 https://www.arscommunity.com/wiki/x-cart/speed-up/is-this-required?rev=1448753153 If you are the store owner and your store is growing, you will meet the speed issue. It doesn't matter by which reason - it can be a big products database or the visitors amount. It's good if you are checking the store speed from time to time - for example by this service. But in any case you will start to receive the customer complains. text/html 2015-11-28T23:25:53+00:00 https://www.arscommunity.com/wiki/x-cart/speed-up/layout-changes?rev=1448753153 On this stage you should change your X-Cart layout fully. As you know the x-cart was mostly based on the tables (old version), what is not good. If you owner the new version, which is based on the divs - it's not possible to say that it's good too (it's too overloaded by different things). text/html 2015-11-28T23:25:54+00:00 https://www.arscommunity.com/wiki/x-cart/speed-up/server_changes?rev=1448753154 The last step is the server configuration. Since you have follow the previous steps - you site should be pretty fast now and the server configuration will allow to improve it a little. The first step is caching, it will allow to left the loaded things on the customer computer. It's good since the css/js (and may be some other general for all of the pages things) won't be loaded each time the new page is loading. It's possible to make by the following in the .htaccess (or in the apache config): … text/html 2015-11-28T23:25:55+00:00 https://www.arscommunity.com/wiki/x-cart/speed-up/small-changes?rev=1448753155 On this stage it's required to look if it's possible to speed up the X-Cart without big changes. And it's better to check the sql queries on this stage. we need to know how much and how much time it's executed. We can check in here, by the following code: