It’s quite different in that you can have dynamic pieces in the cache (see holepunching below). This makes it much more flexible to work with your needs by combining static and dynamic pieces. It’s methods in creating these cache pages is totally different from the HTML catalog. You do not use the files directly like you do with the HTML catalog.

It’s also different in that you can use things like CDSEO or it’s own SEO friendly URL’s without using the HTML catalog way which isn’t ideal. You can even set the URL’s for even more ideal SEO.

Our caching module has the ability to ‘holepunch’ certain parts of the cache to make only those pieces dynamic. For example, you may have a minicart that you want to keep dynamic (you want it to update when products are added to the cart). This X-cart Speed Booster module allows this! All you have to do is follow the holepunching instructions when installing the module and it will know to keep that part dynamic and always updated. Your site will still be faster though because the categories, products, and other data will be cached.

It takes about 150 milliseconds to initialize X-cart. So you would add that much time plus what ever query you need. If it’s something like asking for the current inventory amount for a product, that time is pretty negligible as it’s a simple query to the database. So to holepunch the inventory would only add around 150 milliseconds.

The module takes a compiled ‘snap shot’ of your pages when it runs. What this means is that there is little to no processing needed to be done when displaying your website. It’s like viewing an HTML website. X-cart’s template caching just caches the compiled templates. There is still a lot of processing done at this point. The Demo links above show this speed increase pretty clearly.

You have currently three options if you have inventory that changes frequently. You can have the cron run more frequently to update your cache more often, you can ‘holepunch’ the inventory or our best option is you can do a few optional install steps for Automatic Page updates! Even if you run out of stock on an item, if someone tries to add it to their cart, X-cart will check before adding it to their cart and will not allow them if you are out of stock. See the cron section below for more details.

The Auto Page updates is a few extra install steps you can do when installing to make the cache update when needed. For example, if you modify a product in the admin, these optional install steps will refresh that product’s cache as well as any category pages that product shows up on with no interaction from you required! There are options for having auto updates for products, categories, manufacturers and static pages! These optional install steps are also run as a background task so you won’t see any slowdown by adding it in.

The demo sites are running on a small VM server. There is only 2Gb of Ram and 2Ghz CPU.

The demo’s cached vs non-cached sites are running on the exact same copy of X-cart sharing the same database. The non-cached site has all the cache files deleted so it’s doing direct calls to X-cart

Yes a Responsive template will still operate normally. Think of it this way, X-cart gives you an HTML page in the end after it does all it’s processing and calculations. What this module does is store that HTML page for quick retrieval. No processing involved (or minimal if you holepunch). So the HTML result is the same, it’s just a snapshot and all the processing is done when you run the cache to generate these snap shot pages.

Not a problem. We have an import script to import the information into our module (URL’s and meta data). From then on you can use our module to manage your URL’s. You should find it easier and a more centralized place to manage URL’s

Not a problem. We also support CDSEO. CDSEO will operate as it normally does and our module picks that up for you for the caching!

Yes it sure does! We have a 2nd language installed on our smaller demo.

There are many options for the cron. These options are great for tweaking the refresh to your needs. So if you don’t add/remove products often but your inventory does change often, you can simply run the Product update more frequently than a full update. So you in this example would set up 2 crons. One to do products hourly and one to do the full site nightly.

• You can have the cron update all pages.
• Update the home page only
• Update Products only
• Update Categories only
• Update Manufacturers only
• Update Static Pages only
• OR any combination of the above!

The page limit options are the number of pages the module will cache. The more products and categories you have, the more beneficial this module is! Just view the demo with 100k products to see how much faster the cached vs non-cached pages are on a small VM server!

Not a problem if you run over your page limit! The module will keep working. It just won’t cache any extra pages past your limit but your site will still function like nothing happened!

Yes! You can always upgrade your page limit. We’ll create a link soon for that upgrade option. You’ll pay only the difference between what you purchased and the new page limit you need!