en Jump to content
JPresta.com

[Module] Page Cache - speed up your shop

Recommended Posts

Your shop is slow, you want to speed it up? So read the following...

 

Description of Page Cache module

Reduce your page loading time by avoiding Prestashop to regenerate pages again and again and again... The module saves pages on the server and also configures browser cache to make it as fast as possible.

  • Caches from server side AND browser side
  • Also works for logged in users
  • Satisfied or refunded (30 days to test)
  • Get it now on JPresta.com to speed up your Prestashop (-5%)

How it works?

By default, Prestashop recreates pages of your shop each time a user displays it, yet they do not change except some small part like the cart, the "already seen" block or some others modules you added. Page Cache fixes this fault this way:

  • 1) A user displays a page of your shop
  • 2) Page Cache removes all information about the user
  • 3) Prestashop creates the page "normally"
  • 4) Page Cache saves the page on the server and sends it to the user
  • 5) The page is displayed in the browser
  • 6) Page Cache updates parts of the page that concern the user like his cart and other module set as "dynamic"

When next users display this page, phase 2 (Prestashop creates the page) is skipped, Page Cache sends directly the saved page which is really faster. It uses less CPU, less RAM, and executes less database queries.

 

Even better, when a user goes back on a page he previously displayed the browser cache is used which is almost immediate! Cart and dynamic modules are updated, it's transparent and it works!

 

Server cache timeouts and browser cache duration are configurable. Pages that can be cached are: Home, Categories, Products, CMS, New products, Best sales, Suppliers, Manufacturers, Contact form, Prices drop, Sitemap

 

Cache is automatically updated: when you modify a product, a category, a price, your stock, etc. cache of concerned pages is deleted.

 

It even works with flash sale, multi-store, CloudCache and other proxies

page-cache.jpg

Benefits for you and your users

  • Too slow website discourages buyers
  • Site speed is used by search engines like Google to rank your shop
  • Save money by reducing CPU, RAM and database consumptions

Contact and infos

Get PageCache to speed up your Prestashop on Jpresta.com.

 

Changelogs

  • 4.21 - Fix a conflict with module "Go Reviews (by Lineven)" and maybe other modules using internal cache - Fix a conflict with module "Theme editor (by SUNNYTOO.COM)" to display correct number of products per line - Detects if desktop and mobile site are the same to use the same cache or not - Clear the cache when CSS and JS cache are cleared4.20 Avoid dynamic modules request to be cached by browser - Avoid dynamic modules request to be indexed by search engines - Avoid testing inactive category in speed analysis - Improve cache refreshment when a product is deleted/disabled
  • 4.19 - Enable Prestatrust
  • 4.18 - Improve performance analysis feature - Fix restricted countries detection with geolocalisation by IP - Fix "debug mode" parameter propagation - Fix "no cache for logged in users" parameter propagation - Handle the private shop feature of "Extended Registration for Prestashop" module by modulesmarket.com - Handle 'widget' tag in templates for PS 1.7
  • 4.17 - Little fix on URL of test mode - Don't cache redirected pages (improve detection) - Fix a bug in diagnostic tab template (admin)
  • 4.16 - Improve cache refreshment for suppliers and manufacturers - Handle bad JSON (skip characters before first '{')
  • 4.15 - Fix a bug in CRON job that was cleaning the whole cache when using '&index' - Improve error message during installation - Improve "Page timeouts" tab for PS 1.5 - Prepare for widgets management
  • 4.14 - Use class instead of id to identify dynamic block for PS 1.7 (smarty cache must be cleared) - Fix a bug with SSL redirect detection - Fix a bug with AdminTab
  • 4.13 - Take care of 'prestashop' javascript variable for PS 1.7
  • 4.12 - Assign smarty variables for dynamic modules for PS 1.7
  • 4.11 - Fix a bug in automatic refreshment when modifying images of products
  • 4.10 - Fix a bug in automatic refreshment for multistore - Fix protocol in speed analysis - Fix timeout too short for file_get_content in speed analysis
  • 4.09 - Fix a retro-compatibility issue with old hooks - Swedish translation improvement
  • 4.08 - Use base 64 encoded images for front stats to not degrade YSlow or PageSpeed score - Improve speed analysis - Fix CRON task
  • 4.07 - Fix some log trace in ZipArchive cache system
  • 4.06 - Add details on log when directory cannot be created
  • 4.05 - Do not add CSS file in production mode - Update spanish and swedish translations - Remove Media.php override which is obsolete - Add possibility to ignore backlinks from HTML parts (specific developpement)
  • 4.04 - Compatibility with PHP 5.3 - Move all HTML into templates files - Fix a bug with 1.5 - Improve automatic refreshment
  • 4.02 - Module key for standard edition
  • 4.01 - Compatibility with HHVM - Compatibility with 'Deluxe Private Shop' module from Innovadeluxe - Fix an issue with translations - Fix a cache issue in speed analysis - Update of the swedish translation
  • 4.00 - Compatibility with Prestashop 1.7 - Add auto-configuration system - Add speed test on home, product and category pages - Fix debug URL for multistores - Add prefix to CSS rules to avoid conflict in infos box - Reduce directory creations - Improve algorithms to be faster - Ultimate edition: add caching system 'ZIP archives' - Ultimate edition: add diagnosic feature to help you to configure your prestashop for speed - Media override replaced by hook 'actionAdminPerformanceControllerAfter' - Add header 'application/json' on Ajax requests to avoid search engines to index it - Fix: Preserve baseDir and baseUrl on ajax request
  • 3.17 - Fix cache refreshment when modifying specific prices
  • 3.16 - Avoid loosing the session when redirected to HTTPS protocole
  • 3.15 - Fix a conflict with PopExit module
  • 3.14 - Add hooks for advanced stock management - Add a workaround for a bug in LiteSpeed server
  • 3.12 - Fix permissions of files and directories in '/cache/pagecache' directory
  • 3.11 - Update Media override to avoid the cache to be cleared to many times

  • 3.10 - Fix images URL in info box - Update cccCss prototype to latest one

  • 3.09 - Better check parameters for security reasons (avoid XSS)

  • 3.08 - Remove module's parameters in production mode to avoid them to be referenced in search engines

  • 3.07 - Improvement: do not insert DIV around dynamic modules if current page will not be cached - Fix: native customization is not a module and therefore cannot be refreshed. The workaround is to disable cache for these products.

  • 3.06 - Merge footer and header hook for better compatibility - Fix an SQL problem in hookActionFeature*

  • 3.05 - Fix problem with restricted countries - Fix the issue that was allowing the display of infos box even in production mode

  • 3.04 - Refresh cache when CSS or JS have been changed

  • 3.03 - Now PageCache will not fail on PHP command line call

  • 3.02 - Improve CSS to avoid style problems - Add workaround in case of bad datas in cart rules

  • 3.01 - Fix CSS styles for Prestashop 1.5 - Fix cache refreshment for single language stores

  • 3.00 - Improve infos box - Redesign of configuration page - Step by step configuration feature

  • 2.71 - Fix specific price detection (problem of seconds)

  • 2.70 - Fix country detection (when detected with browser settings)

  • 2.69 - Handle countries with multiple names (Array)

  • 2.68 - Handle modules that have controller named like standard controllers

  • 2.67 - Fix issue with some overrides with version >= 1.6.1.0

  • 2.66 - Improve dynamic modules feature to avoid CSS issues - Fix groups detection with Advanced Top Menu module

  • 2.65 - Fix default group detection

  • 2.64 - Fix SQL query in hookActionProductAttributeUpdate() - Fix the check of overrides activation

  • 2.63 - Add ';' to fix javascript - Modification for Prestashop v1.6.1

  • 2.62 - Fix ProductController hook call

  • 2.61 - Update Hook override - Fix javascript error

  • 2.60 - Fix 'logged out' after SSL redirection - Fix CSS in back office

  • 2.59 - Fix maintenance detection

  • 2.58 - Drop useless column modules

  • 2.57 - Fix javascript order.

  • 2.56 - Fix carriage return in front controllers overrides

  • 2.55 - Fix warning with 1.6.0.1

  • 2.54 - Improve speed and robustness of dynamic modules display - Fix URL with '|' character

  • 2.52 - Fix clear cache for multistore

  • 2.51 - Add Readme.md, move js, css and img to views directory - Avoid bug PSCSX-4773

  • 2.50 - Improve mobile version - Fix products comparison - Fix missing modules when clearing cache

  • 2.49 - Fix PSCSX-4507 (clear cache of null product id)

  • 2.48 - Remove useless StoresController override - Avoid "Invalid argument supplied for foreach()" warning - It's now possible to delete specific pages with CRON URL (controller=comma separated list of ID) - Now handle country when it's based on users's address (delivery or invoice) - Fix a bug when geolocalisation is enabled

  • 2.47 - Handle maintenance mode - Fix problem with blockwishlist (and more generally with Media::addJsDef feature)

  • 2.46 - Fix recursive problem in Hook - Improve forwarding of dbgpagecache parameter

  • 2.45 - Handle cookie encryption - Execute javascript even if there is no dynamic modules (to refresh cart)

  • 2.44 - New functionnality to let dynamic modules bloc empty in cached pages

  • 2.43 - Add option to disable cache for logged in users

  • 2.42 - Handle cookies set by dynamic modules - Fix jquery-cooki(e)-plugins insertion

  • 2.41 - Fix CRC32 column value

  • 2.40 - Workaround for PSCFV-10168 (before 1.5.6.0) - Fix jquery-cookie insertion

  • 2.39 Reduce database size by using CRC32 instead of MD5 hashes - Reduce database size by storing modules's id instead of modules's name - Reduce backlinks count - Forward dbgpagecache parameter so testing is easier, no need to add it on every page - Controls known compatibility issues - Improve infos block: real cache type is displayed (no cache, server cache or browser cache) - Move CSS and JS into pagecache.css and pagecache.js

  • 2.38 - Fix a bug with advanced configuration (javascript executed after dynamic modules) - Fix a bug with Prestashop <= 1.6.0.7 (PS_JS_DEFER)

  • 2.37 - Fix a bug with multi-store - German translation

  • 2.36 - Fix Prestashop addons valitator issues - Optimize isLogged() override - Handle access denied pages for dynamic modules - Do not block store if module is not well uninstalled - Improve uninstallation (removeOverride)

  • 2.35 - Prevent AJAX requests to be cached

  • 2.34 - Fix delpagecache feature - Fix product update reffreshment (on price)
  • 2.33 - Make browser cache private
  • 2.32 - Replace intval() by cast - Fix browser cache min value
  • 2.31 - Add a delpagecache parameter to force the cache be reffreshed - Add link to documentation - A workaround in case overrides have not been well uninstalled
  • 2.30 - Fix country detection
  • 2.29 - Handle enabled modules per device 
  • 2.28 - Fix cookie problem when changing language (found with ajaxfilter module)
  • 2.27 - Workaround for a bug in Prestashop (multiple same JS script when CCC is activated)
  • 2.26 - Now compatible with Duplicate URL Redirect
  • 2.25 - Fix for $context->link not being initialized
  • 2.24 - Handle specific price changes (for flash sales modules)
  • 2.23 - Add 1.6.0.5 compatibility
  • 2.22 - Fix a problem with Mailalerts2.21 - Fix a problem with BlockWishlist, Avoid javascript error if the user clic before the cart is refreshed.
  • 2.20 - Use of Module::isEnabled('pagecache')
  • 2.19 - Handle specific prices feature, Handle module restrictions on groups, Fix problem with URL fragments
  • 2.18 - Fix for user groups dependency
  • 2.17 - Replace _GET and _POST by Tools::getValue(), Fix a bug that will improve cache statistics
  • 2.16 - Add CRON URL
  • 2.15 - Add user groups dependency
  • 2.14 - Add compatibility with ClearURL module, Add compatibility with 1.4 themes
  • 2.13 - Fix auto detect language feature in cookie
  • 2.12 - Multiple shop compatibility
  • 2.11 - Ignore ad tracking parameters to be more efficient, Add log levels to debug faster, Add link to addons forum
  • 2.10 - Add possibility to add javascript to be called after dynamic module have, been displayed (to solve specific theme issues)
  • 2.9  - Disable pagecache footer in debug mode and when it's not needed
  • 2.8  - Improve cache reffreshment speed
  • 2.7  - Add browser cache feature, Add possibility to disable statistics and save some more milliseconds, Check product quantity to know how we should refresh the cache on order validation, Fix a bug with _PS_BASE_URL_ which is not defined in some cases
  • 2.6  - SQL optimisations
  • 2.5  - Fix random number at bottom of cached pages
  • 2.4  - Fix HTTPs issue, Fix mobile version
  • 2.3  - Add a debug mode to be able to test on production site, Add logs possibilities, Fix currency selection
  • 2.2  - Fix a "white page" issue when module is disabled
  • 2.1  - Fix logout feature
  • 2.0  - Hit statistics to know how the cache is efficient, Improve cache management by deleting cache files only when necessary (you can modify how cache is refreshed), Now compatible with CloudCache (do not override same methods anymore), Save cache files in multiple directories to avoid filesystems to slow down, Enable auto-update so you can update your module from your backoffice, New logo, Fix an issue with prices-drop, new-products and best-sales controllers, Fix an issue with default empty cookie name which is now a random name and expires immediately
  • 1.7  - Add default configuration for dynamic modules and a button to go back to this default configuration
  • 1.6  - Hook class updated to merge with version 1.5.4.1, Disable cache and display an error if tokens are enabled
  • 1.5  - Keep 'id_lang' cookie to be compatible with some modules
Edited by JPresta.com

Share this post


Link to post
Share on other sites

It does not work in Prestashop 1.5.5.0

 

I have the following error (IMAGE)

 

Any solutions please, it is urgent

post-109562-0-70136800-1381875962_thumb.jpg

Edited by benja

Share this post


Link to post
Share on other sites

Hello joemartin,

 

Does the module also work on 1.5.6 ?

On Addons it says compatible with 1.4.5.1

 

Seems like a interesting module.

 

Regards,

 

ysco..

Share this post


Link to post
Share on other sites

Hello Joemartin,

 

My mistake i did mean ps version 1.5.4.1 was listed on addons, but I did got the answer I wanted and you confirmed that I orks on ps 1.5.6 ;-)

Yep addons is really slow with validation, everyone complains about it but ps team does not much to improve and shorten the time off validation.

 

I m thinking to buy your module in the next coming weeks.

 

Thanks for the quick reply.

 

Regards,

 

ysco..

Share this post


Link to post
Share on other sites

Yes the module uses overrides. It overrides these methods:

  • FrontController::smartyOutputContent()
  • Dispatcher::dispatch()
  • Hook::exec()

And add some methods in other front end controllers.

There is no other demo site.

Share this post


Link to post
Share on other sites
2.14 is out and available on Prestashop Addons, it brings

    * 1.4 theme retro compatibility

    * ClearURL module compatibility

    * Multi shop compatibility (v2.12)

    * Fix language autodetection issue

    * Ignore ad tracking parameters to be more efficient

    * Add log levels to debug faster

    * Add possibility to add javascript to be called after dynamic module have been displayed (to solve specific theme issues)

Edited by joemartin

Share this post


Link to post
Share on other sites
I don't know Varnish cache but according to there website it's not dedicated to Prestashop, it's more like a proxy that is placed between the internet user and your shop. I think you will have to configure it to make it works (not caching cart, order process, etc.). If anyone know about it feel free to explain how it works here!

 

PageCache is a PrestaShop module so you just have to install it and it's already configured and ready to use! It stores pages on hard disk.

Share this post


Link to post
Share on other sites

I'm using Zend opCache (it's just like APC) in my server. It caches PHP into RAM which makes the first load appear ALOT faster. Very useful for dynamic pages like the shopping cart which Prestasop Full Page Cache can't cache.

 

I love your module and have been using it. It gives great speed! But I think it can be even faster for those Prestashop owner who run Zend opCache or APC on their server which uses the RAM to cache PHP. 

 

Is it possible to provide guides on how to get opCache/APC to cache the cache that Prestashop Full Page Cache module has already cached in the /cache/pagecache/ folder instead of caching the individual PHP that makes up the HTML? That way, it means the the cached page by the module is read from RAM (which is super fast) and sends it out to browser.

Share this post


Link to post
Share on other sites

PageCache does not cache PHP but HTML. Reading HTML from a file is very fast; the part that is still slow is the line

require(dirname(__FILE__).'/config/config.inc.php');

in the index.php (entry point) which load and init PrestaShop engine (all classes).

 

Using Zend opCache will speed up this part but it won't speed up the HTML cache. Did I answer your question?

Share this post


Link to post
Share on other sites

Since the /cache/pagecache/ files are static, can you make them be served by MaxCDN or CloudCache?

 

It could be served by a CDN but you should not set a cache duration longer than 60 minutes because if you modify a price, a description, etc. pages must be reffreshed.

Share this post


Link to post
Share on other sites

So for the caching the PHP, I should use an opcode caching like APC right?

 

If so, after using Full Page Cache and opcode caching, what other things remaining that still can't be cached?

Edited by Pressed0024

Share this post


Link to post
Share on other sites

So for the caching the PHP, I should use an opcode caching like APC right?

Yes

 

If so, after using Full Page Cache and opcode caching, what other things remaining that still can't be cached?

Page cache also configure browser cache so you will have everything set (as far as I know)

Share this post


Link to post
Share on other sites

Thank you! Yes 2.14 is current version. There is no feature in the queue but if you find one that can improve the module let me know!

Would suggest an auto crawler feature button or setting to slowly generate the HTML over a period of time to balance CPU load. This allows almost all cachable pages to be re-cached making no customer suffer non-cached page. This will also work help if the site has dynamic content as part of the html page so that a 1 day cache timeout can be set and the auto crawler feature will regenerate cache for all pages again.

Share this post


Link to post
Share on other sites

@ Pressed0024 

 

I can answer some of your questions. I am going to do them list style since you have asked a lot over this thread.

 

You can get better caching through APC then Zend / OPcache, the reason APC was not chose for php's default cache is that it is not compatible with all php code. That being said, it runs faster than Zend with Prestashop.

 

In theory you could configure varnish to work with the module, in your vcl file you could exclude every resource but what ever extension that the module uses, image files, css files, and js files. The only caveat to this is when the module invalidates a cache file, you will have to invalidate your varnish cache as well. If you make frequent changes to your site this might become cumbersome. I would just cache the image, css, and js files personally. 

 

If you really want to cache the generated files in ram install mod_mem_cache. In the set up of memcache you can specify what file or directory you cache with it. The downside is that memcache does not act like varnish in being a reverse proxy. It will still serve the request from memory using an internal http request. 

 

You might could CDN the files, but doing that would not be advised, just depending on how the module is written. There are 2 ways that the module can be written. It either caches the whole page with all of the data, or it caches the individual portions of the page. Like there is a file for the header, the products page, and the footer ( and modules that are cached). Then from the cache files the actual view-able page is built. If it caches this way, which I suspect it does, then having them stored on a CDN will slow your site down and just plain not work. 

 

The CPU spends time on compiling the code cache. APC, Zend, and others do not store the code as compiled, they store the code converted to OPcode in memory. The file still needs to be compiled into a view-able product. Also your cpu is going to spend time on file requests, sending images, generating cookies, headers, mysql db calls and other things. The module I imagine reduces the mysql requests, but does not eliminate them. It would be impossible for prestashop to work without requests such as the cart, is the user logged, and other ones such as that. 

Share this post


Link to post
Share on other sites

Thanks for the input.  

 

" The file still needs to be compiled into a view-able product"

 

 

So the next major time taken is the compilation of non-cached parts that Page Cache module can't do? What can be done or implemented to speed up this compilation or maybe further cache it?

 

I also addressed the part about delaying js which takes up 1.2secs of the 3 secs first page render time which is huge savings: http://www.prestashop.com/forums/topic/292821-how-to-forcing-js-to-load-the-last/?view=findpost&p=1476673

Share this post


Link to post
Share on other sites

Thank you! Yes 2.14 is current version. There is no feature in the queue but if you find one that can improve the module let me know!

 

For the "Advanced cache management" events trigger, can you add Product comments as one of the trigger? When new comment is inserted or approved (backend), we had to purge the page cache manually. Having this trigger would be useful when we receive new product reviews.

Share this post


Link to post
Share on other sites

can you add Product comments as one of the trigger? When new comment is inserted or approved (backend), we had to purge the page cache manually. Having this trigger would be useful when we receive new product reviews.

 

Ok, I will check that.

Share this post


Link to post
Share on other sites

I saw this at Google page test:

 

http://developers.google.com/speed/pagespeed/insights/

 

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

 

 

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

 

 

When using Page Cache module is page load faster when you enable minify html/js or faster to disable them?

 

When minify html is turned on, is Page Cache module caching the minified version?

 

I already tested on my server but how does it fair for others?

Share this post


Link to post
Share on other sites

When using Page Cache module is page load faster when you enable minify html/js or faster to disable them?

It's better to enable it but it's not dependent to PageCache. The module only cache the generated HTML.

 

When minify html is turned on, is Page Cache module caching the minified version?

PageCache store the generated HTML so yes it will cache the minified version

Share this post


Link to post
Share on other sites

How to refresh the cache for the top-seller block? I have a top seller product that is discontinued and have disabled it but top seller block is still displaying that product.

 

Try to update your product without changing it (you edit and save), this will trigger the cache refreshment for this product.

Share this post


Link to post
Share on other sites

Thank you! Yes 2.14 is current version. There is no feature in the queue but if you find one that can improve the module let me know!

 

Since this module is supposed to boost speed, if there is a feature to cache html where critical js scripts are loaded last, this could significantly boost page render speed.

 

The problem with delaying js at footer is some modules have issue when loaded at footer but if you could make only "safe" prestashop default modules load last, this module can significantly reduce page load speed and is a must get for anyone who wants speed boost.

 

There is a free running project here: http://www.prestashop.com/forums/topic/282343-free-module-move-java-script-to-footer/

Share this post


Link to post
Share on other sites

Try to update your product without changing it (you edit and save), this will trigger the cache refreshment for this product.

I actually tried doing this before coming here to post but it didn't work. The block still contains the disabled product.

Share this post


Link to post
Share on other sites

I actually tried doing this before coming here to post but it didn't work. The block still contains the disabled product.

 

Just to be sure: the product is not in the block if page was not cached?

Workaround: reset the whole cache

I will verify that trigger and see why it's not fired.

Share this post


Link to post
Share on other sites

Since this module is supposed to boost speed, if there is a feature to cache html where critical js scripts are loaded last, this could significantly boost page render speed.

 

The problem with delaying js at footer is some modules have issue when loaded at footer but if you could make only "safe" prestashop default modules load last, this module can significantly reduce page load speed and is a must get for anyone who wants speed boost.

 

There is a free running project here: http://www.prestashop.com/forums/topic/282343-free-module-move-java-script-to-footer/

 

Interesting but hard to implement it since there is a CCC feature that merge and compress all JS.

Share this post


Link to post
Share on other sites

Interesting but hard to implement it since there is a CCC feature that merge and compress all JS.

Worth a try. Throw the "safe" js to the footer and most people should have an issue. Let most of the theme's specific js load first.

 

Throw the js to footer and hand pick those needed to be loaded at header.

Share this post


Link to post
Share on other sites

Just to be sure: the product is not in the block if page was not cached?

Workaround: reset the whole cache

I will verify that trigger and see why it's not fired.

When Best sales page is set to not cache, disabled block still resides in the Top Seller block. 

Share this post


Link to post
Share on other sites

I have installed this module and I must say that I am impressed with the speed the pages are now displayed on my site.  There are more expensive caching modules than this but Page Cache does everything I need.  You can check out the performance on www.galvoshredders.co.uk (based in the UK so there will be a network lag if you are in another country.)

 

The developer has also added a great function whereby you can clear the cache and statistics via a Cron job.  This allows me to clear the cache in the middle of the night before running a cache warming routine so that all my pages are cached and ready for visitors.  You may not want to do this if you have thousands of products, but this is the command I use:

 

wget -r -D www.domain.com -l3 -P temp -x -R "*cart*","*order*","*My Theme Name*" --delete-after --output-file=log.txt --no-verbose http://www.domain.com/

 

This touches all my pages without taking a long time or downloading the site.  You will obviously need to change 'domain' to your address and change 'My Theme Name' to your theme name (or delete this--it was just to stop wget from trawling areas I didn't want it to.)  The '*cart*' and '*order*' was to stop the products from being added to the cart.

 

Anyway, great module and fast response from the developer so I highly recommend it.

Share this post


Link to post
Share on other sites

Would suggest an auto crawler feature button or setting to slowly generate the HTML over a period of time to balance CPU load. This allows almost all cachable pages to be re-cached making no customer suffer non-cached page. This will also work help if the site has dynamic content as part of the html page so that a 1 day cache timeout can be set and the auto crawler feature will regenerate cache for all pages again.

 

See the post of pchapple, it might help: http://www.prestashop.com/forums/topic/281654-module-page-cache-speedup-your-shop/?p=1501898

Share this post


Link to post
Share on other sites

I have installed this module and I must say that I am impressed with the speed the pages are now displayed on my site.  There are more expensive caching modules than this but Page Cache does everything I need.  You can check out the performance on www.galvoshredders.co.uk (based in the UK so there will be a network lag if you are in another country.)

 

The developer has also added a great function whereby you can clear the cache and statistics via a Cron job.  This allows me to clear the cache in the middle of the night before running a cache warming routine so that all my pages are cached and ready for visitors.  You may not want to do this if you have thousands of products, but this is the command I use:

 

wget -r -D www.domain.com -l3 -P temp -x -R "*cart*","*order*","*My Theme Name*" --delete-after --output-file=log.txt --no-verbose http://www.domain.com/

 

This touches all my pages without taking a long time or downloading the site.  You will obviously need to change 'domain' to your address and change 'My Theme Name' to your theme name (or delete this--it was just to stop wget from trawling areas I didn't want it to.)  The '*cart*' and '*order*' was to stop the products from being added to the cart.

 

Anyway, great module and fast response from the developer so I highly recommend it.

 

Where do you use this command? In cron?

 

I'm also assuming this command uses the server's resources for the wget?

Edited by Pressed0024

Share this post


Link to post
Share on other sites

So i would ssh my hosting server which is hosting my store and use that command and it should start pre-generating the page cache?

 

I'm actually currently using http://home.snafu.de/tilman/xenulink.html whenever i need. Only thing is that it chalks up hell lots of resources on my store.

Edited by Pressed0024

Share this post


Link to post
Share on other sites

I will try it when I have the time. I using Xenu for now suggested by you.

 

Since you are into modules that significantly speed up stores, would you consider looking into delaying js scripts?

 

Here's the challenge:

 

http://www.prestashop.com/forums/topic/292821-how-to-forcing-js-to-load-the-last/?do=findComment&comment=1501353

 

Properly delaying the right js to footer can render pages faster by 1 sec.

Share this post


Link to post
Share on other sites

So i would ssh my hosting server which is hosting my store and use that command and it should start pre-generating the page cache?

 

I'm actually currently using http://home.snafu.de/tilman/xenulink.html whenever i need. Only thing is that it chalks up hell lots of resources on my store.

 

It just goes in a shell script or run it directly.  It's fairly fast so hopefully light on your resources.

Share this post


Link to post
Share on other sites

have problem after instal of cache modul i have problem with bazinga top module http://szakla4x4.pl/

any body have some idea?

 

and the same Back to Top stop working :/

 

And http://szakla4x4.pl/148-motocykle-szosowe

cattegories on the left after few seconds there missing

 

how ti fixed?

Edited by imgmind

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More