This project is not covered by Drupal’s security advisory policy.

Whenever the cache is cleared (or "flushed" in Drupal parlance), whether from new content creation of a volundary flush, the burden of caching is moved to the users: files are not actively rebuilt and put in the cache until a visitor chances upon the page to be rebuilt. This causes two problems:

1) it gives your users an impression of sluggishness about your site, and sluggish sites are bad sites;

2) Google now considers your page load speeds as part of its ranking algorithms; everything else being equal, faster pages rank higher -- precaching gives your site the edge, especially when, in the worst possible case, Googlebot is the user burdened with a first visit on a page.

Smart Flush lets you configure URLs that must be rebuilt after any type of cache clearing, or can be set to recache all pages that account for a certain percentage of traffic (it is often said that 20% of your pages account for 80% of your traffic for example, so Smart Flush can be configured to regenerate those 20% of all of your pages, of you can go all-out and request that all of your pages be recached).

Project information

Releases