The module aim to give you a clear, centralize way to audit your Drupal site.
The analyze give you a good overview of the state of art of your site.
If you want to improve the overall quality of your project this module is for you.
The module has 28 checks distributed on theses 6 criterial :
This module will make your ajax-enabled Views, use GET instead of POST.
Why?
Because GET is much better for caching. If you're using something like Varnish, or Boost, these will not store POST requests.
Views uses the Drupal Ajax framework. This by default uses POST.
While a lot of Ajax inside of Drupal requires POST (the Views admin UI, for example), a view itself doesn't. If you disable Ajax on a View, it will use GET anyway.
A filesystem based authcache backend. Set it up using a configuration similar to the following one (settings.php).
In order to configure the backend, install and enable it into your modules directory. Then add the htaccess rules shipping with this module to your .htaccess file in between the rewrite-base directive and the actual query rewriting rules.
This module requires a *nix based server with working symlink support. Windows is untested.
Idea : This module will address the performance needs of the Drupal site by analyzing various performance aspects of the site and provide the detailed performance report.
Tool will have following features
This module enables to create the cached wrapper of any block. It can be used where standard block caching is disabled if node access modules are installed.
Caching of block panel panes is supported also. Just add a block pane and configure the block (not the pane) to turn on caching.
This module is aimed at providing a powerful yet lightweight caching option for sites that use views and panels. It can be considered as a faster and more advanced alternative to the standard caching provided by views/panels (also when they are combined with rules and cache_actions contribs).
Extends Acquia Purge to allow for placing a block on a page for "purge this page" functionality. Addresses the situation of when you want to grant permissions to a content edit who doesn't have administrative privileges so that they can purge the Varnish cache of any given page if they notice any content (node, block, views) is stale.
Dependent on versions of Acquia Purge with the acquia_purge_purge_path() function, introduced in 1.0-beta2.
In the Acquia Cloud platform, you can redirect site visitors in the Varnish layer, based on the devices they are using, as determined by the user-agent HTTP header in the request. You can do this by using your web site's .htaccess file to set HTTP headers in the response.
However, when you configure Acquia Cloud to use PHP-FPM, the .htaccess file is no longer able set http headers and these redirects stop working. To get the redirect headers to output again, you'll need to generate them in PHP code instead.
Note: Ajax Include Pattern 1.4+ requires jQuery 1.7+. The easiest way to do this is jquery_update but this is not a dependency as users may wish to update jQuery in other ways. Alternatively, download and use v1.3 of the library.
