inShare Maintaining swell performance as well as scalability is not an easy task with almost any large Drupal site. Such activities require quite a lot of time and effort. As an unpleasant addition to all of that is seems that speed gains are becoming smaller as more work is being done. The goal, of course, is worth it, yet is but natural for humans to be looking for easier roads. So here are several tricks that may assist you quite well in the optimization field. The load times will be decreased noticeably. Try integrating a memory based caching system like the Memcached. Positive sides: It is fairly faster than the DB based caching of Drupal There are two modules available for you to choose: Cache Router or Memcache No patching is required for Drupal versions 6 and higher Negative sides: Patching is required for lower versions (hardly a negative side as for me) Additionally: You will certainly an installed and running Memcached Both of the modules available work and are fully operational, yet Cache Router is a bit more flexible. And is capable of using different tools than Memcache is. You’ll need to configure the Memcached settings (you can do so in settings.php) while performing a multi-server setup. This is needed for usage of an IP address rather than a ‘localhost’ for the servers to have the ability of sharing Memcached bib(s) and of increasing cache hit rates In order to cache URL aliases you can use the Path Cache module. Positive sides: Great reduction in the URL lookup queries Negative sides: It is quite useless without the Memcached integration. Without it this module can actually make things worse It requires patching The Boost module may help you with caching entire pages into files Positive sides: Serving the pages which have been cached is lightning-fast. Nothing will be significantly hit to the database or stack of Drupal You can choose which pages you want to cache The negative sides: It is sad, yet this one is beneficial to anonymous users only. However the speed up is massive, so use it if you have any anonymous ones. Other notes: It is of high priority to modify the .htaccess as directed. And don’t forget that the cache directory in the root of the Drupal directory needs to be writable. If the page is not looking properly after reload – try excluding the path Move your Java Script to the bottom of the page. The good it does: The page will be visible even if the JS component is not quite loaded yet. The bad: You may get some Java Script errors if you do have an in-line JS code. The reason to those is the dependency issues related to libraries like JQuery. Additional notes: Do cut the line from the top of your page.tpl.php template file and paste it into the bottom before you close the body tag. I hope you will find this usefull.