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
Working with Magento?
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.
What it is
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.
The honest version
No technology is all upside. This is where Magento (Adobe Commerce) earns its place and where it tends to cause trouble.
Sound familiar?
The Magento (Adobe Commerce) problems that bring people to us, and what you have once each one is fixed.
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
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
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 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
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
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
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
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
Ring us for one urgent fix, or let us run the whole stack for you.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
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
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: