Store diagnosis

La Carnicería Virtual

I reviewed an online butcher shop top to bottom to find why people came in and did not buy. I delivered a list of fixes ordered by how much each one helps sales.

La Carnicería Virtual home page
Real screenshot of the project
Work for a brand
type of project
Shopify · Liquid
main tools
3
real screenshots of the project

01 · The challenge

What was going on

Context

La Carnicería Virtual had a large catalog and a good offer. What was failing was elsewhere: the site loaded slowly, finding the cut you wanted was hard, and it lacked the signals that make you comfortable buying meat online.

The problem

Say what to fix first without proposing a redesign nobody asked for, and without mistaking an ugly-looking technical number for something actually costing sales.

My part

I reviewed the experience, the speed, Google search, the measurement, and how the store is put together, and turned it into an ordered list of work.

02 · How I solved it

How I decided to solve it

  1. 01

    Walk the store the way a customer would: homepage, category, product, and cart, skipping no steps.

  2. 02

    Compare what you can see with what the tools measure and with how the site is built underneath.

  3. 03

    Rank every finding by how much it moves sales, how much it costs to fix, and who it depends on.

03 · What I made

What got built

  • A map of everything I found, by area.
  • Each item scored: how much it adds and how much it costs.
  • A 30, 60, and 90-day plan: the cheap and fast things first, the deeper ones after.

04 · Charts

The numbers as charts

LCV-PRI

Published finding priority

Distribution of annotations shown in this case, not the full audit inventory.

  • Critical1

    PERF-01 · mobile LCP.

  • High4

    UX-02 (×2), UX-01, SEO-02.

  • Medium2

    UX-04, UX-05.

Editorial count of published markers; no sales-loss estimate.

LCV-LCP

Mobile LCP: field vs lab

Keeping CrUX and Lighthouse separate avoids treating lab as a field substitute.

  • 3.6sCrUX (field)May 19–June 15, 2026.
  • 16sLighthouse (lab)Lab condition on June 16, 2026.
Both signals are public in this case; no commercial figures are published.

LCV-RDM

30 / 60 / 90 roadmap

Work sequence proposed from impact and effort.

  • 0–30 days35%

    Quick wins: widgets, PDP trust, schema.

  • 30–60 days35%

    Collection discovery and homepage weight.

  • 60–90 days30%

    Theme debt, tracking, and structural performance.

Relative roadmap emphasis; not approved spend.

06 · How it turned out

What changed in the end

  • A concrete plan on three fronts: load fast on a phone, make products findable, and make paying feel safe.

  • The team ended up with a clear order instead of a pile of loose problems.

What I would not compromise on

  • Understand first, redesign after.
  • A technical number only matters if it costs the business money.
  • An analysis that does not end in decisions is useless.

07 · Technology

What it is made with

  • ShopifyShopify
  • ShopifyLiquid
  • ChromeChrome DevTools
  • PageSpeed InsightsPageSpeed Insights
  • ChromeChrome UX Report
  • ChromeLighthouse
  • Google Analytics 4GA4
  • Google Tag ManagerGTM
  • Meta AdsMeta Ads
  • Google AdsGoogle Ads

Want something like this for your business?

If you feel your store is losing sales and cannot tell where, that can be found out. I start by walking through it as a customer.

Write to me