NL EN

IT management
Microsoft 365
Network & security
Who for
Hosting & cloud
Magento
Websites & online shops
Managed applications

All services at a glance

A Magento audit: know what you have.

Before you change agency, plan an upgrade or buy a shop. Look first, then decide.

Drawing of a loading waterfall: first waiting for the server, then HTML, styles, scripts, fonts and images.ServerHTMLStylesScriptsFontsImagesLargest element visible

Short answer

A Magento audit is a review of an existing shop: the version and missing patches, changes to the core, the quality of modules and custom work, speed, the set-up of the server and security. Jevana delivers a report in plain language, with the risk of each finding and the order in which to tackle it. The audit is separate from who does the work afterwards.

What we go through

Version and patches

  • Which release, and until when it gets patches
  • Which security patches are missing
  • PHP, database and search engine on a maintained version

Code

  • Changes to the Magento core
  • Third-party modules, where they come from and whether they are still maintained
  • Custom work judged against Magento's rules
  • Whether there is a repository, and whether production matches it

Speed

  • Whether the page cache works, and for which pages it does not
  • Cron and indexers
  • Load time per page type, server and browser separately

Server and security

  • Who can get in, and how
  • Backups, and whether one was ever restored
  • Traces of an earlier break-in

When an audit makes sense

  • You are considering another agency and want to know what you are handing over
  • The agency says an upgrade is a new project, and you want a second opinion
  • You are taking over a company that comes with a Magento shop
  • The shop gets slower every year and nobody can explain why

A report you can pass on

The report is written for the owner of the shop, not for the developer. Each finding says what is wrong, what it can cost if left alone and what it takes to fix.

You can take it to your current agency, to another one or to us. We give no quote in the audit. If you then ask for a proposal, that is a separate step.

Questions

What does a Magento audit deliver?

An audit delivers a report on the state of the shop: what is good, what is a risk and in which order to tackle it. Afterwards you know whether the shop is safe, whether an upgrade is feasible without a rebuild and what maintenance realistically needs. The audit itself changes nothing in the shop; we only need read access.

Can I use the audit to change agency?

Yes, that is often what it is used for. A new agency can use the report to judge what it is taking over, without spending weeks in the code itself. It also avoids the argument afterwards about what was already wrong. We write the report so that another agency can work with it as well as we can.

Do you need access to the live shop?

We need read access to the code, the server and the back office. We do not write anything. If no access to production can be given, we work with a copy of the code and an anonymised database. To measure speed and the page cache, the live shop itself is enough; it is public.

What is the difference between an audit and a code audit?

A code audit looks only at the software: modules, custom work and changes to the core. A full audit also covers the server, speed, backups and security. If your doubts are mainly about a developer's work, a code audit is enough. If you want to know whether the shop as a whole is healthy, choose the full one.

Tell us what you run.

An introduction costs nothing. You talk straight away to one of the two people who will actually do the work.