The Usual Suspects: Five Configuration Solutions to Maximize Peak Sales

The Usual Suspects: Five Configuration Solutions to Maximize Peak Sales

How to fix and prevent the five most common configuration problems for Adobe Commerce Sites

As we explained in this recent post, regular maintenance is the unsung hero of ecommerce site performance. Site maintenance should include checking for potential configuration problems. This is often overlooked. Configuration issues can develop even after you have made site changes or installed a patch.

Although configuration problems are usually easy to fix they can have a significant impact on site performance and security. You could experience a site crash during holidays or when you have a large amount of traffic to your storefront. Poor customer service can lead to abandon carts or other lost sales opportunities. It could also take more time for your team members to complete routine maintenance tasks.

It’s good to know that five of the most common configuration problems are easily identified and addressed, especially if you know what you’re looking at. It is possible to prevent downtime and lost sales by addressing them quickly. Learn how to quickly fix the common Adobe Commerce configuration problems.


Issue 1: Default CAPTCHAs

Impact: Less cart abandonment.

Standard CAPTCHAs require that shoppers fill out a form in order to prove they’re human shoppers. These forms are added to the checkout page and increase the likelihood that buyers will abandon their carts. Additionally, shoppers who have to complete multiple CAPTCHAs (such as login and account information) may not return to your store.

We recommend that you enable Google reCAPTCHA to make your site more user-friendly and protect against spammers. Google reCAPTCHA allows shoppers validate their identity by simply clicking one checkbox. This documentation explains how to enable it on your sites.

Issue #2: Cacheable variable set “false”.

Impact: Performance reduction due to the failure to cache your webstore pages.

Adobe Commerce recommends caching pages in order to improve site performance. The best improvement comes from using a CDN. What if your website’s pages are not caching correctly? Your storefront’s performance will drop dramatically if this happens.

If pages don’t cache, it is likely that the problem is a configuration issue. The entire page cannot be cached if any block is not designated as uncacheable. This means that you can’t add any blocks to a layout.cacheable=”false”)Indefault.xmlYour entire store will be without cache. This configuration can be tested and verified that all CMS, Catalog List and Product View pages are cacheable. Find out moreSetting up caching in Adobe Commerce.

Issue #3: No need to reindex

Impact: Your website is slowing down and seems to be constantly reindexing.

Your web storefront may slow down if it is constantly rebuilding and flushing its index. Poor performance can also be caused by constant reindexing, which can lock tables and add locks to them. Your site may be constantly reindexing due to common admin functions such as:

  • Product attributes saved
  • Site/store/store save
  • Configure your store

Reindexing can cause performance problems. This can be avoided by performing these actions outside of normal business hours. If that doesn’t solve the problem, you might want to check your third-party extensions to see if they are causing full indexing. This article can help you troubleshoot slow performance due to full reindexing; and this documentation can help you set up indexing so that it runs only when necessary.

Issue 4: End of service for minor publications

Impact: Your site may experience performance and quality problems, security breaches, and other issues.

Adobe Commerce’s development team is constantly working to ensure that Adobe Commerce provides the best security and performance possible for your customers and employees. We offer regular updates to fix any new vulnerabilities. You can also access new features quickly and easily without waiting for a new version. It is important to keep up with the patches and use the supported version of Adobe Commerce. This will allow you to secure your site and enjoy the latest functionality and performance enhancements.

If you’re unable to access the latest patches–and your site is experiencing performance issues–your version of Adobe Commerce may have passed its end-of-service deadline.

This issue can be fixed easily. It is as easy as upgrading your commerce application to the latest supported release. You will always have the most recent features, functions and security patches if you keep up to date with new releases. Learn more about Adobe’s software lifecycle policy.

Issue #5: Outdated Magento Quality Patches

Impact: Your Magento Quality Patches package doesn’t contain the latest Adobe Commerce patches or fixes.

MQP is a self-service tool that delivers individual patches and lets you easily apply, revert, and find information about all individual patches that are available for your version of Adobe Commerce. However, to install the latest patches, you must first update your MQP package. You could miss security or functional updates.

This issue can be addressed easily, once again. Make sure you have the latest MQP package installed before installing patches. Adobe strongly suggests that you test any new patches before releasing them to your production environment.

Problems can be quickly fixed

Each of the issues discussed in this post can cause “symptoms” which can lead to a technical investigation. Adobe is trying to make it easier for customers and business users to spot them. If your site is running Adobe Commerce 2.4.1 or higher, you can see warnings about these issues and nearly 100 more in the Site-Wide Analysis Tool.

The Site-Wide Analysis Tool is easy-to-use, and we recommend reviewing the reports generated by the tool as a regular part of your ongoing site maintenance program.