Store Intelligence Report
& CRO Roadmap

A data-driven response to the concerns raised about conversion rate performance, a clear diagnosis of what is actually happening, and a restructured execution plan designed to deliver the fastest possible revenue impact.

The Problem

In our recent conversation, the team raised a serious concern: the store's conversion rate has dropped sharply. Over the past 7 days, Shopify shows a conversion rate of 0.19%. Over the past 30 days, 0.61%. These numbers are dramatically lower than the historical 1.6-2.3% range the store has maintained. The concern is understandable: if the store is converting at a fraction of what it used to, that directly impacts revenue, cash flow, and the ability to sustain operations.

We took this concern seriously and performed an immediate deep dive into the store's Shopify analytics. We pulled data across multiple time windows, compared against prior periods and year-over-year benchmarks, analyzed traffic sources by device and geography, and examined every stage of the conversion funnel.

What we found changes the picture significantly. The conversion rate drop is real in the numbers, but it is not caused by the website converting worse. It is caused by a massive influx of non-human (bot) traffic that is artificially inflating session counts and making every percentage metric look worse than reality. Orders and revenue are actually up year-over-year.

This report presents the full evidence, explains what is happening and why, and lays out a restructured execution plan that directly addresses the team's priorities: increase conversion rate, increase revenue, and do it as fast as possible.

Current Performance Snapshot

Last 30 days (Mar 21 to Apr 20, 2026) compared to the prior 30 days and the same period last year.

Diagnosis: What Is Happening

The conversion rate collapse is caused by bot/synthetic traffic inflating session counts. Here is the evidence.

Traffic Sources Point to Data Centers

One Area That Does Need Attention: AOV

Average order value has declined 8% (30d) and 23% (7d) year-over-year. This is independent of bot traffic. Possible causes: product mix shift, increased discounting, or loss of higher-ticket items. CRO execution can address this through upsell tactics, bundle promotion, and strategic pricing presentation.

The Restructured Execution Plan

We have reshuffled the original project timeline to respond directly to the team's priorities. The original plan sequenced Performance Optimization (Epic 2) before CRO Execution (Epic 3). We are now pulling the highest-impact tasks from both epics, re-ordering everything by expected revenue impact, and adding a new Phase 0 that did not exist in the original plan.

The goal is simple: deliver the fastest possible conversion rate improvement with the resources we have. Every task below is sequenced by how quickly it can generate measurable revenue lift, not by which epic it originally belonged to. Infrastructure fixes that directly affect conversion (Apple Pay, checkout friction, shipping bugs) are pulled into Phase 0 alongside the bot traffic fix. CRO quick wins that the original plan scheduled for weeks 5-8 are brought forward to weeks 2-5. Tasks that are important but slower to show results (positioning, About page, performance optimization) stay in later phases.

Expected Impact

Projections based on ~20,000 legitimate sessions/month and current AOV of £65.55.

Our Approach: Why We Restructured the Plan

The original Web Project Plan had three epics in sequence: Technical Foundation Audit (complete), Performance Optimization, then CRO Execution. That sequence made sense when we built it. Performance optimization improves page speed, which reduces bounce rate. CRO execution improves what visitors see and do, which increases purchases. The logical order was to make the site faster first, then make it more persuasive.

But the situation has changed. The team has told us directly that cash flow is tight and that results need to come faster. We listened. And when we dug into the data, we found that the conversion rate alarm is largely a false signal caused by bot traffic. That means the real opportunity is not about fixing a broken site. It is about making a working site convert even better, and doing it quickly enough to impact revenue within weeks, not months.

That is why we restructured the plan. We pulled the highest-impact CRO tasks forward. We combined them with critical audit fixes that directly affect checkout conversion (Apple Pay, GDPR compliance, shipping friction). We added Phase 0 to clean up the bot traffic so we can measure results accurately. And we moved performance optimization to a later phase, because while it matters, it does not generate the same immediate revenue lift as CRO changes do.

The CRO report we delivered in January scored the store's "Decision" stage at 14/25 and "Action" stage at 17/25. Those are the two weakest points in the conversion funnel. Every task in Phases 1, 2, and 3 targets one of those two stages. The changes we are making are not speculative. They are proven, high-ROI interventions that are widely used by top-performing ecommerce stores: headline rewrites, CTA redesigns, bestseller badges, scarcity messaging, testimonial deployment, and checkout friction reduction.

Performance optimization is not being dropped. It will run as the next phase after CRO execution completes. The 17 tasks originally planned for Epic 2 (image compression, script cleanup, lazy loading, font optimization) remain in the project plan and will be executed on the same timeline structure.