Working with Magento?

Magento slow, stuck on 1, or mid-upgrade? We fix it.

Most Magento stores that reach us are either still running on Magento 1 years after end of life, or sitting on a Magento 2 install that has been tuned for everything except the parts that are actually slow. We find the real bottleneck and fix that, without rebuilding a store that is otherwise earning its keep.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

var/log/system.log

still failing

What it is

Magento (Adobe Commerce) at a glance

Magento is an open-source ecommerce platform first released in 2008 by a company called Varien. It was bought by eBay, then by Adobe in 2018, and now ships in two forms: the free open-source edition and the paid Adobe Commerce release, which adds cloud hosting, B2B features and support.

A typical Magento stack is PHP and MySQL with Elasticsearch for catalog search, Redis for sessions and cache, and Varnish in front for page caching. Magento 1 reached end of life in June 2020 and stopped receiving security patches, but a surprising number of stores are still running it in production today.

Type
Ecommerce platform
First released
2008
License
Open Source edition, and Adobe Commerce under a commercial licence
Built on
PHP with MySQL or MariaDB, Elasticsearch and Redis
Maintained by
Adobe
Typically used for
Mid-market and B2B stores with complex catalogs or heavy customisation

The honest version

Magento (Adobe Commerce) pros and cons

No technology is all upside. This is where Magento (Adobe Commerce) earns its place and where it tends to cause trouble.

Where Magento (Adobe Commerce) is strong

  • A proper catalogConfigurable products, custom attributes, attribute sets and tier pricing are built in from the start, not bolted on later as a plugin.
  • Multi-store and multi-currency built inOne install can serve several storefronts, languages and currencies from a single admin, which saves running parallel sites for each market.
  • Strong B2B featuresAdobe Commerce adds company accounts, quotes, shared catalogs and negotiated pricing, which are the parts wholesale buyers actually need.
  • Customisable at every layerTemplates, layouts, modules and the service layer are all open to change, so unusual business rules can be modelled directly in the store.

Where Magento (Adobe Commerce) bites

  • Expensive to hostMagento wants plenty of memory and will not run well without Elasticsearch, Redis and ideally Varnish. Shared hosting is not an option for anything busy.
  • Steep learning curveThe framework has its own patterns for dependency injection, plugins and layout XML. Developers coming from other PHP stacks need weeks before they are productive.
  • Major upgrades are rewritesThe move from Magento 1 to Magento 2 is a migration, not an upgrade. Themes and custom modules have to be rebuilt against a different architecture.
  • Old Magento 1 stores everywhereYears after end of life, many stores are still on Magento 1 with no security patches, running on PHP versions that are themselves out of support.
  • Specialist developer ratesBecause the learning curve is steep and the pool of qualified people is small, Magento developers charge noticeably more than general PHP or WordPress ones.
  • Adobe Commerce is priceyThe commercial licence runs into five figures a year before hosting and implementation, which rules it out for smaller stores.

Sound familiar?

Common Magento (Adobe Commerce) problems we fix

The Magento (Adobe Commerce) problems that bring people to us, and what you have once each one is fixed.

report.CRITICAL exception

Checkout is painfully slow

Usually a mix of missing full-page cache, Elasticsearch running on the same box as PHP, a slow payment call made during the final step, and third-party modules doing work on every request.

Checkout back under two seconds

Magento 1 reached end of life

The store is still on Magento 1

No security patches since June 2020, an old PHP version underneath, and payment providers starting to refuse the integration. Carrying on is a risk, and a rebuild is a project.

Patched today, migrated on a plan

bin/magento setup:upgrade failed

The Magento 2 upgrade stalled

A major version bump that broke a custom module, a theme built against an older API, or a database patch that half applied and left the install in a mixed state.

Upgrade finished and verified

ElasticSearch is not alive

Search and category pages are empty

Elasticsearch is down, on the wrong version, or pointed at the wrong index name after a server move. Customers see no products and nobody notices until sales drop.

Search serving results again

Reindex all stuck at 40%

Prices and stock go out of date

Indexers that silently fail or deadlock, so the admin shows one price and the storefront shows another. Cron is running but half the jobs never finish.

Indexers green and on schedule

Payment failed: Braintree gateway rejected

Orders fail at payment

Expired API credentials, a gateway module that was never updated, or a checkout extension clashing with the payment one, which quietly loses you orders every day.

Payments through on the first try

static content deploy failed

Deploys break the storefront

A static content deploy that fails in production, missing CSS and JavaScript, and a site that looks unstyled until someone clears generated directories by hand.

Deploys that finish cleanly

last verified backup: unknown

There is no tested backup

Nightly dumps that may or may not be complete, media stored only on the live server, and no record of a restore ever being rehearsed.

Backups taken and restored on a schedule

What we do

Magento help, from rescue to upkeep

Ring us for one urgent fix, or let us run the whole stack for you.

Rescue
Down, defaced, or broken after a deploy. We get it taking orders again first and find the cause second.
Speed
Full-page cache, Elasticsearch and Redis tuning, checkout profiling and hosting that fits, measured before and after.
Magento 1 to 2 migration
Catalog, customers and orders moved across, custom modules rebuilt against the Magento 2 architecture, cut over on a planned window.
Adobe Commerce upgrades
Major version upgrades rehearsed on a copy first, so the production one is uneventful and the store is open again by morning.
Custom modules and integrations
Payment gateways, ERP and shipping integrations written for the way your business actually runs, not forced into a generic extension.
Managed Tech
Patches, backups, monitoring and a team to call, on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Magento (Adobe Commerce) alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Magento (Adobe Commerce) questions

Something else? Call+1 737 727 7327

Is Magento 1 still safe to run?

The honest answer is no, not safely any more in 2026. It has had no official security patches since June 2020, the PHP version it runs on is itself out of support, and the payment providers are gradually tightening up on integrations that will connect to it. Community patches exist and we apply them where they help, but the honest answer is that you are living on borrowed time and planning a move is cheaper than being forced into one.

How much does it cost to upgrade from Magento 1 to Magento 2?

It depends on how much has been customised and how much of that is still earning its keep. A small, mostly default Magento 1 store can move across in a few weeks. A heavily customised one with bespoke modules and a custom theme is closer to a rebuild. We scope it on a fixed estimate before any work begins, and we tell you plainly if any part would be cheaper to drop than to port.

Why is Magento so slow?

Almost always a combination of missing or misconfigured full-page cache, Elasticsearch and Redis on the wrong hardware, a checkout that makes live calls to a payment or tax service on every keystroke, and third-party modules doing database work on pages that should be cached. Throwing a bigger server at it rarely helps; fixing those four things nearly always does.

Should I move off Magento to Shopify?

Only if your catalog and business rules actually fit what Shopify does well. For a straightforward store with a few hundred products and standard checkout, Shopify is usually the lower-stress choice. For B2B, complex pricing, multi-store setups or deep ERP integration, staying on Magento or Adobe Commerce is often still the right call. We will tell you honestly which side of that line you are on.

Can you take over a Magento store from a previous agency?

Yes, that is a routine piece of work for us. We audit what is actually installed, document the customisations, get logins and hosting into your name, and pick up patches and improvements from there. You do not need the old agency's cooperation for any of this, only access to the server and the code.

How much does Magento help cost?

Our estimates are free of charge and fixed before work begins. Describe the store and the problem, and you will have a written price and timeline before anyone touches the code.

Free estimate

Magento giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.