# Drupal Performance Tip – removing unused modules — Liran Tal

This entry is part 2 of 2 in the series Drupal Performance Tips

Canonical: https://lirantal.com/blog/2014-11-12

In the spirit of the computer video game [Doom](http://doom.wikia.com/wiki/Doom) and its [skill levels](http://doom.wikia.com/wiki/Skill_level), we’ll review a few ways you can improve your [Drupal](http://drupal.org/) speed performance and optimize for better results and server response time. These tips that we’ll cover may be at times specific to Drupal 6 versions, although you can always learn the best practices from these examples and apply them on your own code base.

![Doom](https://web.archive.org/web/20141116001643im_/http://adamatomic.com/pics/blog/doom/doom2.jpg)

If you’re using a [Drupal](http://drupal.org/) [distribution](https://www.drupal.org/documentation/build/distributions) which is great for kick-starting a project with many features built-in, you should still review added modules which are managed through the [installation profile](https://www.drupal.org/node/306267) as they might prove un-necessary for your product as time goes and your product evolves and matures. Remember that even if you’re not using a distribution, you might have added some modules to meet a functionality, which you no longer use and you disabled through CSS, through the menus, through the theme, but you forgot all about removing the actual module. These un-used modules account for memory footprint as they are loaded through PHP and they can also account for Drupal hooks, which is even worse in terms of performance for you.

Remember to **review your installed modules base on Drupal** and remove any un-used functionality:

[![drupal\_perf-2](https://web.archive.org/web/20141116001643im_/http://enginx.com/wp-content/uploads/2014/11/drupal_perf-2.png)](http://enginx.com/wp-content/uploads/2014/11/drupal_perf-2.png)

## More writing

[All writing →](/blog)

*   Sep 5, 2026

    ### [Self-Hosting Hermes Agent with Matrix E2EE on Proxmox](/blog/self-host-hermes-agent-matrix-e2ee-proxmox)

*   Aug 2, 2026

    ### [The Practical Second Brain: Building an LLM-Operated Markdown Knowledge Graph](/blog/practical-second-brain-llm-markdown-knowledge-graph)

*   Aug 1, 2026

    ### [Building a Second Brain with LLMs and AI Agents](/blog/building-second-brain-llms-ai-agents)


* * *

Liran Tal is the author of the book [Node.js Secure Coding: Defending Against Command Injection Vulnerabilities](https://www.nodejs-security.com/)

[Start Building Secure Node.js Applications ↗](https://www.nodejs-security.com/)

 [![](/_astro/nodejs-secure-coding-book-3d-style.DiTWpzFs_Z3c7s1.png)](https://www.nodejs-security.com/)