The measurements
Profiles the templates, the server side and the checkout paths, then writes the fix list and prices it.
Services
Page
Lazy Ants · eCommerce · Fixed-price audit
eCommerce Performance AuditWhat slows the store, and what fixing it costs. Answered in one week.
The eCommerce Performance Audit costs $2,250 and ends with a fixed price for the fix.
- $2,250
- Fixed price
- 1 week
- From day zero
- 1 price
- For the whole fix
Systems we have built and maintained
When this is worth doing
The store is slow, and nobody can say what it costs or what fixing it takes:
Conversion
Page speed and Core Web Vitals are costing conversion, and nobody can say which fixes pay back first.
Search
Core Web Vitals are failing in Search Console on the templates that bring organic traffic.
After a release
The store got slower after a release or a new app, and nobody can point to the change.
Peak season
A sale or a peak season is coming, and the store slowed down under the last one.
Before a new platform
Someone proposes a new platform to fix speed, and you want to know whether the current one can be fixed first.
If the platform itself is the question, start with the eCommerce Architecture Review instead.
The real failure mode
Most slowdowns sit away from what the score measures
A lab score measures one page on one connection. Revenue runs through three places it does not see:
Server side
Queries and data access on category and search pages, once the full catalog and real filters are loaded.
Cache
Caches that clear too often, or never, so the store either serves nothing from cache under load or serves stale prices.
Checkout
Payment callbacks and third-party calls that stall the path that carries money.
Each of these is cheap to fix once it is found and expensive to find during a sale weekend, when every slow second is lost orders.
Finding them takes access to the running store and its real data, which is most of what the week is spent on.
This is what the audit produces
Two pages from it. The structure is what every audit produces; the figures here are illustrative.
Every item carries where it is, what causes it, what it costs you now and what fixing it takes. The list ends in one price.
The measurement that matters is the one staging cannot show, because staging does not have your catalog.
What you get
Measurements
Field data from your analytics and Search Console, and five or six revenue templates profiled on your real catalog: category, product, search, cart and checkout.
Fix list
Every item with what it costs you, what fixing it takes, and where it sits, ranked by what it pays back.
Fixed price
One price for the whole fix, so the next step has a number before it has a contract.
Walkthrough
A call where we take your team through the findings and answer what the report does not.
The fix list is written to be handed to any team. We would like to do the fix, and it does not have to be us.
One week, from day zero
Day zero is the day access is granted and one person on your side is named as the owner. The week starts then, so waiting for access does not come out of it.
What day zero requires
- Admin access to the platform
- Analytics and Search Console access
- Read access to the systems behind checkout: payments, ERP, whatever carries your order data
- One named person who can answer a question within a working day
How the week runs
Days 1 to 2
Field data, and the revenue templates profiled on your real catalog.
Days 3 to 4
The server side, the cache and the checkout paths.
Day 5
The fix list, the price for the fix, and the walkthrough with your team.
Who runs the audit
Our CTO does the measurements and prices the fix, and leads the senior engineers who do it if you go ahead. The person who measured your store is the person on the call.
Day zero and next steps
Sets up access with your side, runs the walkthrough, and scopes whatever the fix list points to.
What it costs
$2,250, fixed. No hourly billing. If you go ahead with the fix, from $7,500, the full fee credits toward it within 60 days of delivery. If the audit shows the platform is the constraint, half the fee, $1,125, credits toward the eCommerce Architecture Review instead.
If you go ahead with the fix
Fix at a fixed price$14,600
Audit credited−$2,250
You pay$12,350
If the platform is the constraint
eCommerce Architecture Review$3,850
Audit credited, half−$1,125
You pay$2,725
Half goes into the review because the two overlap only in part. The review still reads the whole platform and its integrations; only the speed part is already done. Below $7,500 there is no credit on the fix.
How it ends
Three endings, and we commit to all three.
Fix it
A fixed price for the fix, ranked by what it pays back. The list works with any team. We would like it to be us, and it does not have to be.
Move
The platform itself is the constraint. We say so, and half the audit fee goes toward the eCommerce Architecture Review.
Leave it
The store is slower than it could be, and fixing it would not pay back yet. We say that too, and you keep the measurements.
You are buying a number and a decision. What you do with them is yours.
Where the evidence comes from
Performance stabilised as a system outcomeRegressions on high-traffic templates caught by gates before they reach all users.Read the caseCheckout stabilised under loadCheckout fixed while revenue kept running through it.Read the caseThese are delivery cases, not audits. The audit is new and we will not pretend otherwise. What they show is that the measurements and the price come from people who have done the fixing.
Questions we get before booking
The questions teams ask before the first call. If yours is not here, ask it on the call.
How is this different from a Core Web Vitals audit?
A Core Web Vitals audit reports on the front end. This one also reads the server side, the cache and the checkout paths, and it ends with a fixed price for the fix.
How is it different from the eCommerce Architecture Review?
The audit answers why the store is slow and what fixing it costs, in one week. The review answers whether to migrate, optimise or wait, in two weeks, across the whole platform and its integrations. If you already suspect the platform, start with the review.
How much does it cost, and how does the credit work?
$2,250, fixed. If the fix comes to $7,500 or more and starts within 60 days, the full fee credits toward it. If the audit shows the platform is the constraint, half the fee credits toward the eCommerce Architecture Review. Below $7,500 there is no credit on the fix.
What access do you need?
Admin access to the platform, analytics and Search Console, and read access to the systems behind checkout. If admin access is not possible, tell us on the first call: we will say what can still be measured, and the report will name what it could not.
Which platforms do you cover?
Magento and Adobe Commerce, Shopify Plus, Sylius, Shopware, BigCommerce and WooCommerce. If you run something else, ask on the first call.
Do you do the fix?
If you want us to. Senior engineers do it, led by the CTO who ran the audit, and most fixes take from two to three weeks. It is priced in the audit, and the fee credits toward it. The fix list works with any team.
Do you do conversion optimisation?
No. This is engineering on the stack: templates under load, caching, checkout state and payment paths. Testing button colours is someone else's job, and we are not good at it.
How soon can you start?
Start dates are booked in order of request. Tell us when the slowdown started costing you money, and we will say honestly how soon the audit week can start.
Request the audit
Tell us which pages are slow and what it is costing you. If the audit would not earn its price for you right now, we will say so on the first call.