Magento 2 Audit
A technical Magento audit in 5 business days. We rebuild your store on our server from an anonymized copy, check what it actually uses and tell you what to do with every module. After the Magento store audit, you know what to remove, what to keep and where to start.
Magento stores collect unnecessary modules over the years
The bill arrives with the next update. Magento security patches have to be installed regularly, and each one goes through all of that code. The more modules and vendors, the higher the chance that something breaks, and the more expensive it is to fix.
When the store starts slowing down and something stops working after an update, it's a good moment for an audit. Before you add another module or a bigger server, check what the store actually uses. That's where we start.
How a technical Magento audit works
Three stages, 5 business days. We work on a copy, so your store runs as usual the whole time.
1. Server review
We check the PHP, MySQL and nginx versions, the configuration of services such as Varnish or RabbitMQ, cron jobs, error logs and whether the store has current security patches. This is where you see what is really installed, not just what the documentation says.2. Trial installation on our side
We move the code to our repository, anonymize the database and set the store up on our server. It doubles as a test of restoring from backup on a different machine. This is where things you can't see in production come out: missing licenses, a slow build, modules that block the installation.3. Configuration and module analysis
A Magento expert maps the store architecture and goes through module by module: is it configured, does it have data in the database, does it need a license, and doesn't Magento already do this on its own. We finish by walking you through the results.What you get after a Magento store audit
A faster, more stable and more secure store starts with a plan: what to remove, what to update and what to keep.
A decision on every module
Remove, replace, migrate or keep. Every decision comes with the reason.Architecture diagram
How the store connects to ERP, payments, shipping and other systems. On a single diagram.A tested backup
You know the store can be restored on another server, because we just did it. The installers stay with you in case you ever need to migrate.A list of licenses and keys
Which modules need paid licenses and access keys, and what happens when one of them expires.Server and security status
Versions with known vulnerabilities, missing security patches, errors that keep coming back in the logs and cron jobs that don't run.Walkthrough and plan
A meeting where we go through the results and agree where to start. The report stays with you.Magento audit in practice
Case: Magento audit of an electronics store
88 modules, of which about 18 were needed
- 41 from the previous vendor, with no documentation or support. 28 of them had not a single database entry or any configuration.
- 28 from one vendor's paid package. The store used one option template on 7 products and two SEO templates from it.
- 19 other third-party modules, some of them never configured.
Fix the old store or build a new one on a ready base
| Fixing the old store | New store on a ready base | |
|---|---|---|
| Modules to maintain | 88 | about 18 |
| Maintenance work | baseline | about 3× less |
| Risk when updating | high, someone else's undocumented code | low, our modules and 4 proven third-party ones |
| Speed | theme from 2019 | Breeze, 2-3× faster |
Bringing the old store into shape would have cost more than rebuilding it. We recommended a new store on Magento 2.4.8 with the Breeze theme, built on our ready-made starter kit, with a look close to the current one. Native Magento options were to replace the paid product options package. Every one of the 88 modules got a decision: 56 to remove, 14 to replace with our solutions, 4 to migrate, 4 to keep as they are. We planned the rebuild on the ready base at 6-8 business weeks.
Case: Magento audit of a store with a PWA front end
The two biggest problems came out before we looked at the code
Both problems came out during the trial installation. First, licenses were missing for one payment provider's modules, so the store couldn't be installed until we removed them. Second, generating static files took 4 hours. In a healthy Magento it takes a few minutes, and this step runs on every deployment, production included.
On the test environment it was also impossible to place an order, because a paid shipping module required a separate license key.
Most of the problems came down to excess
We recommended slimming the store down in a safe order:
- automated tests of the purchase paths,
- switching modules off one by one and running the tests after each,
- whatever passes the tests goes out of the code.
What Magento store audits teach us
Both audits lead to the same conclusions.
Dead weight slows things down and breaks them
28 dead modules in one store, a whole unused front end in the other, a build that took 4 hours. Before you speed up your store with new code, check what you can throw out of it. Often that's enough.A simple store costs less
Out of 88 modules, about 18 remain, and there is about 3× less maintenance work. An ERP connected through the standard API needs no module in the store. Fewer parts means fewer things that can break during an update.Every vendor is another risk
A paid package of 28 modules served 7 products. One missing license blocked the installation, another one blocked orders. Every extra vendor means their code, their license and their update schedule.Add-ons
Review of your code
We review the code written for your store, such as a PWA front end or custom modules: quality, alignment with Magento best practices and how easy it is to keep developing.
Integration review
ERP, PIM, payments, carriers. We check how data flows between systems and where an integration can get stuck.
UX review
We walk the purchase path through the customer's eyes: from the product page through the cart to payment.
QA audit and performance audit
Automated tests of critical paths (registration, cart, checkout) and load tests on recorded sessions. They show where the store slows down under heavier traffic.
See the results
Explore selected projects and read case studies in a concise format.
JKB / FairyTrees
Bielenda / MiyaCosmetics
Bioderma / Esthederm
LaMania
References that speak for themselves
Dynamics, changing circumstances, and our approach to work - our clients will tell you themselves. See what it's like to work with us.
The e-com.house Team helped us with a comprehensive implementation of the ecommerce business model. Despite the difficult conditions related to the coronavirus pandemic, as well as the number of parties involved and the complexity of the project, within a few months we managed to add a strong online presence to our current business. E-com.house was a real support for us in the entire process and in various areas – from technology, through UX, to growth marketing.
Daniel Biegaj
Ecommerce & Marketing Director w Benefit Systems
sklep.yes2move.com
We've been working with e-com.house on all things ecommerce since may 2018. Apart from being 100 percent professional and reliable, they are also really nice people 🙂 Their expertise allows us to make decisions quicker while helping us to avoid mistakes that are easy to make when you're getting started with your own ecommerce business. e-com.house also acts as our technological partner as their team supports and adjusts our entire IT infrastructure to the demands of our quickly developing online store.
Alina Sztoch
Co-founder Kubota Store
KubotaStore.pl
What sets the e-com.house team apart from the competition is their focus on the client and their ability to see a bigger picture when analyzing client's needs. At the same time they pay great attention to detail. Thanks to their comprehensive knowledge, the team can not only help you in creating your digital strategy, but also make it easy for you to implement and execute it. They have a holistic approach to the digital brand building process - they appreciate both the importance of content and the need to monetize it. Working with them has been a great pleasure.
Hanna Rydlewska
Digital Director 'Vogue Polska'
Vogue.pl
E-com.house took over the maintenance and development of our online bookstore Literia.pl in November 2018. During that time their team has proven to be very competent in using Magento - the engine that our store has been built on. Moreover, our cooperation runs in a relaxed atmosphere – the e-com.house team members I've met are simply very nice and helpful people.
Piotr Kubiszewski
Product Owner Literia.pl, Grupa Onet-RASP
Literia.pl
We've been working with e-com.house for over 2 years. During that time we've successfully migrated 6 of our online stores from Magento 1 to Magento 2, while refreshing their UX/UI with the mobile device users in mind. This has improved the overall efficiency and security of our online stores. Merging 6 separate platforms into 1 multistore has also lowered our costs. Overall, our conversion rate has increasd by 47%!
Izabela Pańkowska
UK Market Manager
LiveOutside.co.uk
E-com.house supported us during the entire process of developing and implementing our new online store. Their continuous support, regular status updates and consultations allowed us to efficiently solve current issues and ensure that the platform is compliant with the rest of our IT ecosystem. In practice, we have become one team that works together to achieve the set goal.
Daria Leśniewska
Sales & Communications Director
RISKmadeinWarsaw.com
Having cooperated with a number of companies, we were looking for a business partner and not an inflexible contractor. E-com.house has proved to be such a partner. They helped us create an online store that meets all our requirements. Their enormous knowledge, professionalism and a very high level of culture made our cooperation a very interesting experience. The product they delivered has been equipped with many features that exceed our expectations.
Piotr Jóźwik
Kierownik działu ecommerce w PCE
PartnerElectronic.eu
