Aurora Creation
PLEN

An e‑commerce audit and an analysis of your online store

Check what your e‑commerce needs: a pre-implementation analysis, a CRO and CX audit, a technical audit, a performance audit or a WCAG accessibility audit. Each of those scopes answers a different decision and leads to a separate service.

If you don't know where the source of the problem lies, start from the situation you want to solve. We will help you choose the right direction for the analysis.

Choose an audit or an analysisLet's talk
  • Manufacturers
  • Private-label brands
  • B2C sales
  • B2B sales

Areas of diagnosis

  • CRO and CX
  • Preparing an implementation
  • Technology
  • Performance
  • Accessibility

One scope of analysismatched to the decision you have to make

The same symptom can have several different causes

A drop in sales can come from barriers in the purchase path, a slow store, technical errors or trouble with the integrations. Before a migration or a new implementation, in turn, the requirements, the processes and the dependencies between systems have to be checked.

Which is why the scope is not worth choosing by the name of the audit alone. First state the situation and the decision the analysis has to support.

When it is worth starting with an analysis

  1. 01The team has several hypotheses but no single diagnosis grounded in data.
  2. 02The backlog keeps growing and each fix fails to remove the source of the errors.
  3. 03The company is planning a migration or a new platform, but the requirements are scattered across departments.
  4. 04The store runs slowly or loses stability under heavier traffic.
  5. 05Digital accessibility has so far been assessed in fragments, or not at all.

A drop in salesone symptom visible in the report

Possible causes

  • Customer path
  • Store speed
  • Technical errors
  • Product data
  • Integrations

Which e‑commerce audit should you choose?

Five services, five different situations. Each one says when it is the right choice; the service page then covers its scope, how the work runs and what it produces.

01CRO and CX auditFor stores that have traffic but want to improve conversion, the purchase path and the user experience. It points to what makes it harder to find a product, reach a decision and complete a purchase.CRO and CX e‑commerce audit02Pre-implementation analysisFor new implementations, migrations and large rebuilds that need the requirements, the technology, the scope, the budget and the schedule settled. It puts processes, integrations and areas of risk in order before the project starts.pre-implementation e‑commerce analysis03WCAG accessibility auditFor stores and services that need their digital accessibility verified against the accessibility criteria. It covers the barriers that make the interface harder to use with a keyboard, a screen reader or other assistive technology.WCAG accessibility audit04Technical e‑commerce auditFor existing platforms that need their code, architecture, integrations, security and technical debt assessed. It helps judge whether the current store can be grown further, stabilised or taken over from another supplier.technical e‑commerce audit05E‑commerce performance auditFor stores that need an analysis of speed, responsiveness, Core Web Vitals and the problems affecting user experience. It shows what lengthens loading and what limits how much traffic the store can serve.e‑commerce performance audit

CRO, technology, performance or accessibility — what do we check?

Every service in one row: what we analyse, its main result and when that scope is the right one. If you do not know where to start, read the last column.

ServiceWhat we analyseMain resultWhen to choose it
CRO and CX auditconversion, UX, user behaviour and the purchase pathpriorities for conversion and customer-experience optimisationwhen the store has traffic but sales do not use its potential
Pre-implementation analysisgoals, processes, features, technology, data and integrationsthe scope, architecture, budget and schedule of the projectbefore an implementation, a migration or a large rebuild
WCAG auditthe accessibility of the interface and the purchase processa list of non-conformances and remedial recommendationswhen digital accessibility has to be verified
Technical auditcode, architecture, integrations, security and infrastructurea list of technical risks and a plan of fixesbefore taking over or growing an existing platform
Performance auditCore Web Vitals and frontend performancea list of performance problems and optimisation prioritieswhen the store is slow or its performance metrics are poor
CRO and CX audit

What we analyse

conversion, UX, user behaviour and the purchase path

Main result

priorities for conversion and customer-experience optimisation

When to choose it

when the store has traffic but sales do not use its potential

Pre-implementation analysis

What we analyse

goals, processes, features, technology, data and integrations

Main result

the scope, architecture, budget and schedule of the project

When to choose it

before an implementation, a migration or a large rebuild

WCAG audit

What we analyse

the accessibility of the interface and the purchase process

Main result

a list of non-conformances and remedial recommendations

When to choose it

when digital accessibility has to be verified

Technical audit

What we analyse

code, architecture, integrations, security and infrastructure

Main result

a list of technical risks and a plan of fixes

When to choose it

before taking over or growing an existing platform

Performance audit

What we analyse

Core Web Vitals and frontend performance

Main result

a list of performance problems and optimisation priorities

When to choose it

when the store is slow or its performance metrics are poor

I don't know which direction to choose

First we establish what actually has to be checked

The scope depends on the problem and on the kind of service chosen. Which is why, before the analysis starts, we settle its goal, the material needed and the areas that are to be verified.

  1. 01

    Situation and decision

    We establish what is going on in the e‑commerce, what problem the team wants to solve and which decision it needs the data for.

  2. 02

    Choosing the scope

    We settle the right kind of audit or analysis and the boundaries of the area that needs checking.

  3. 03

    Material and access

    We establish which data, documents, environments and credentials are needed. The list depends on the kind of service and on the e‑commerce architecture.

  4. 04

    Analysis and findings

    We verify the agreed scope, put the findings in order and name the areas that call for further work.

How long it takes, the format of the final material and how the findings are discussed depend on the service chosen. We state them at the offer stage, once the scope is settled.

Let's talk

What do you get after an e‑commerce audit?

The problems identified, an assessment of their impact, priorities, concrete recommendations and a plan of the next steps. A recommendation is only useful once it is known what it follows from and which problem it concerns — which is why every finding has the same, separated structure.

Findings ordered this way add up to a roadmap of changes rather than a document that goes into a drawer once read: it is clear what is urgent, what depends on what, and where to start. An estimate of the cost or time of the fixes is not a standard part of every audit — we give one only in the services where it genuinely belongs to the scope, and we say so before the work begins.

Once the scope is settled we can show an anonymised fragment of sample material, so that before the work starts it is clear what level of detail to expect.

See selected projects

What one finding is made of

  1. 01The problem identifiedWhat exactly was noticed: a specific view, process, database query or interface element.
  2. 02Source or evidenceHow we know: analytics data, a measurement, a log, a fragment of code, a session recording or a test with a keyboard and a screen reader.
  3. 03ImpactWhat the problem bears on: sales, customer service, the cost of maintenance or the pace of further growth.
  4. 04PriorityHow urgent the change is next to the other findings, and what carrying it out depends on.
  5. 05Recommendation and next stepWhat to do next: take a decision, gather extra data, apply a fix or carve out a separate piece of work.

How much does an e‑commerce audit cost, and how long does it take?

We do not give one price for every audit — a performance audit of a single store and a pre-implementation analysis before a migration across several markets are different work. Below are the seven things that decide the estimate and the schedule; each service's own terms are on its page.

What decides the estimate and the date

The kind of audit
Each of the five services has its own method and its own effort. A performance audit rests on measurements, a pre-implementation analysis on workshops and documentation.
The size of the store
The number of products, categories, markets and language versions decides how much has to be checked for a finding to hold for the whole store rather than one case.
The number of views and processes analysed
The scope is agreed upfront: the main purchase paths alone are a different effort from the full set of views, the customer account and post-purchase processes.
The number of integrations
ERP, PIM, WMS, payments, couriers and marketing automation — every connection is an area of its own to check, and a question of its own about who owns the data.
The technology
Magento 2, Shopify, Pimcore or a custom solution differ in where problems usually arise and in how much work it takes to reach the data.
How much data is available for the analysis
Existing analytics, logs, documentation and change history shorten the work. Without them, part of the time goes into building the basis before the first finding exists.
The scope of the report
A list of risks with priorities is a different document from material describing solutions, examples and a plan of stages. The format is agreed together with the scope.

Each service's own terms

We confirm the estimate and the date once the scope is settled — that is, after a conversation about the situation and about what has to be checked. Any figure before that would be the price of an unknown scope.

E‑commerce audits and analyses in practice

The Diablo Chairs store on Magento 2, shown on a laptop

Pre-implementation analysis

Diablo Chairs

Before the new platform was built we ran a three-month pre-implementation analysis: the current situation and the brands' existing sites, the business requirements, the market and the competition, and the growth plans. It ended with a document recommending the direction of the work, and on its findings Domator24 decided to build a D2C platform on Magento 2.

  • an analysis of the current situation and the existing sites,
  • business requirements gathered from the teams,
  • an analysis of the market and the competition,
  • a plan for the brand's future growth,
  • a document setting out the next steps,
  • the later implementation of a D2C platform on Magento 2.
See the Diablo Chairs pre-implementation analysis case study

FAQ — e‑commerce audits and analysis

You do not need to know the name of the right service before the first contact. What matters most is naming the problem, or the decision the analysis has to support.

The starting point is the decision the company has to make, together with the symptoms visible in the store now: traffic without sales leads to a CRO and CX audit, slow operation to a performance audit, recurring errors to a technical one, accessibility obligations to WCAG, and a planned migration or a new platform to a pre-implementation analysis. All five scopes are set side by side in the section on what we check.

We do not give one price for every audit. The estimate is driven by the kind of audit, the size of the store, the number of views and processes analysed, the number of integrations, the technology, how much data is available and the scope of the report — all seven are set out in the section on cost and time. Each service's own terms are on its own page.

We do not give a date before the scope is settled, because the scope is what decides the time: an audit of one area is shorter than a pre-implementation analysis, which covers workshops, documentation and agreement across several teams. After a conversation about the situation we give the date together with the scope and the format of the final material.

Yes, and sometimes it is necessary, because one problem joins several areas — performance, architecture and integrations, for example. The scope is then split so that every finding has a clear basis and an owner on the business or the technical side, rather than ending up in one bag with the rest.

The problems identified, an assessment of their impact, priorities, concrete recommendations and a plan of the next steps — in a form that adds up to a roadmap of changes rather than a document for a drawer. How a single finding is built is described in the section on the result of an audit. An estimate of the cost of the fixes is not a standard part of every audit; we say before the start whether it belongs to the scope of the service chosen.

Yes, but an audit does not commit you to that — the material is written so that it can also be carried out in-house or with another supplier. If the changes are to be delivered by us, we estimate them separately, once it is settled which recommendations go into the first stage.

Yes, and for Pimcore and custom solutions too. The platform changes less the scope itself than where problems usually arise and how the data is reached: in Magento 2 we have access to the code and the configuration, while in Shopify part of the stack is closed, so the analysis rests on the theme, the apps, the data and measurements.

They are two different things. A pre-implementation analysis serves to plan the target project: it settles the requirements, the processes, the technology, the scope and the schedule, which makes it the right starting point before a migration. An audit serves to assess a specific area of the existing solution — the code, performance, accessibility or the purchase path — and complements the analysis when you need to know the state of what is being moved.

A technical audit concentrates on the code, the architecture, the integrations and the technical debt. A performance audit deals with the speed and stability of the store and the sources of delay. The scopes can touch, but they answer different questions.

The list depends on the kind of analysis. It can call for analytics data, documentation, access to an environment, the repository, information about integrations or a description of business processes. We settle the exact set during qualification.

Let's establish what diagnosis your situation needs

Describe the problem, the change you are planning and the decision the team has to make. On that basis we'll point to the right direction for the conversation and the material needed to assess the scope.

If the kind of subject isn't clear yet, pick the qualification option in the form — we'll settle it in the call.

Małgorzata Gudalewska, Head of Sales at Aurora Creation

Małgorzata Gudalewska

Head of Sales

+48 664 531 867[email protected]
[email protected]ul. Jana Henryka Dąbrowskiego 28, 15-872 Białystok, Poland
Go to the full contact details
No files chosen
Thank you, we'll get back to you within 1 business day.

Once we've read your description we'll route the subject to the right person and come back with a possible next step. Sending the form does not order the service.