Magento 2 Performance Boost: Safely Removing Unused Payment Modules (Braintree, Mollie)

Optimizing Magento 2: Shedding Unwanted Payment Modules for Better Performance

In the competitive landscape of e-commerce, a fast and lean Magento store isn't just a luxury; it's a necessity. Every millisecond counts for site speed, user experience, and ultimately, your bottom line. However, a common challenge faced by Magento 2 merchants and developers alike is the presence of default modules that, while potentially useful for some, can become unnecessary bloat for others.

This issue was vividly highlighted in a recent Magento GitHub discussion (#41060), where user 'fabotha' brought to light a pertinent problem: the default installation of payment gateways like Braintree and, in some cases, Mollie, even when they are not actively used. As e-commerce migration experts at Shopping Mover, we understand the critical impact such seemingly minor details can have on your store's overall health and performance.

The Hidden Costs of Unused Modules: Bloat, Errors, and SEO Impact

The GitHub issue detailed how Braintree and Mollie, when not in use, consume valuable system resources, inflate the static file size, and even spam the system.log with recurring error messages. Let's break down these hidden costs:

• Log Bloat and Debugging Nightmares: Specifically, Braintree was reported to generate 'Braintree\Configuration::merchantId needs to be set' errors every few seconds. Imagine trying to debug a critical issue when your log file is filled with hundreds, if not thousands, of irrelevant Braintree messages. This log bloat makes identifying genuine problems significantly harder and consumes disk space.
• Inflated Static File Size and Slower Load Times: The presence of unused module assets (JavaScript, CSS, images) directly contributes to a larger static content footprint. This means more data needs to be downloaded by the user's browser, leading to slower page load times. In an era where Google prioritizes Core Web Vitals and site speed for search rankings, this can directly impact your SEO and conversion rates.
• Resource Consumption: Even if a module is disabled, its presence in the codebase can still contribute to compilation times, dependency checks, and overall server load, however minimal. A leaner system is always a more efficient system.

The core request from the community was clear: an installation option to exclude these modules by default, aiming for a leaner, faster Magento instance with fewer resources consumed and cleaner logs.

Why Are These Modules Bundled by Default?

Understanding why these modules are present helps in finding the right solution. It was clarified in the GitHub thread that:

• Braintree: This payment gateway is typically bundled within the adobe-commerce/os-extensions-metapackage. This meta-package is designed to pull in several other modules that Adobe/Magento deems essential or beneficial for a standard installation.
• Mollie: Interestingly, Mollie is generally not a core Magento Open Source module. However, it's often bundled with popular third-party themes like Hyvä (e.g., hyva-themes/magento2-mollie-theme-bundle). This bundling can sometimes be due to strategic partnerships or sponsorships, where the theme or platform provider includes certain integrations by default.

Regardless of the reason, the impact on performance remains the same if these modules are not utilized.

The Magento Community's Elegant Solution: Leveraging Composer's 'Replace' Directive

While the initial request was for a core Magento installation option, the community, particularly 'hostep', quickly provided an actionable workaround using Composer – Magento's powerful dependency manager. This method allows you to effectively tell Composer that you are providing the functionality of a specific package yourself (even if you're just removing it), thus preventing it from being installed or updating it.

Step-by-Step Guide to Removing Unused Modules:

Before you begin: Always back up your Magento instance (codebase and database) before making any significant changes to your composer.json file or running Composer commands. If you're not comfortable with command-line operations or Composer, we highly recommend seeking assistance from an experienced Magento developer.

1. Access your composer.json file: This file is located in the root directory of your Magento installation.

2. Add the 'replace' directive: Locate the "replace": {} section in your composer.json file. If it doesn't exist, you can add it. Then, add the packages you wish to remove:

    "replace": {
        "adobe-commerce/os-extensions-metapackage": "*",
        "hyva-themes/magento2-mollie-theme-bundle": "*" 
    },

Note: The "*" tells Composer to replace any version of these packages. Only include the Mollie line if you are using a theme like Hyvä that bundles it.

3. Run Composer Update: Execute the following command in your Magento root directory. This will instruct Composer to remove the specified packages and update your dependencies.

composer update adobe-commerce/os-extensions-metapackage hyva-themes/magento2-mollie-theme-bundle --with-dependencies

Tip: You can specify individual packages or run `composer update` without arguments to update all, but specifying helps focus the change.

4. Update Magento Setup: After Composer has finished, you need to update your Magento installation to reflect the changes in your module configuration.

bin/magento setup:upgrade

5. Clean Cache and Deploy Static Content: Finally, clear your cache and redeploy static content to ensure all changes are reflected on your storefront.

bin/magento cache:clean
bin/magento static-content:deploy -f

Beyond Performance: Cleaner Logs and Easier Debugging

The immediate benefits of this optimization are tangible: a smaller static file size, faster page load times, and a noticeable improvement in your Google Lighthouse scores. But equally important is the benefit of cleaner system logs. Without the constant stream of Braintree error messages, your developers can more easily identify and address critical issues, leading to a more stable and maintainable Magento environment.

When to Seek Expert Help

While the Composer `replace` directive is a powerful tool, it requires a certain level of technical proficiency. As 'fabotha' noted in the GitHub thread, if you're not a Magento/Linux tech, or if the thought of modifying your composer.json gives you pause, it's always best to consult with experienced Magento developers. Incorrectly modifying your Composer dependencies can lead to a broken installation.

At Shopping Mover, we specialize in Magento migrations, performance optimization, and custom development. Our team of experts can help you audit your Magento instance, identify areas for improvement, and implement solutions like module removal safely and efficiently, ensuring your store runs at peak performance.

Conclusion: A Leaner, Faster Magento is Within Reach

The GitHub issue #41060 serves as a valuable reminder that even seemingly minor default installations can have a significant impact on your Magento 2 store's performance and maintainability. By proactively shedding unused modules like Braintree and Mollie using Composer's `replace` directive, you can achieve a leaner, faster, and more efficient e-commerce platform. This not only enhances user experience and boosts your SEO but also streamlines development and debugging processes.

Don't let unnecessary bloat hold your Magento store back. Take control of your performance today!