Services / 04 — Shopify Performance
A fast Shopify store, without touching the design.
Speed optimization for DTC brands with a heavy visual identity: video on every page, catalog-quality imagery, and a product page that weighs too much. We cut the weight behind engineering gates, so the design stays exactly as it was.
From audit to a fast store in production.
The engagement starts with a Shopify Speed Audit: a full teardown with Lighthouse, GTmetrix and Core Web Vitals across your key page types, a ranked list of what weighs the store down, and an estimate of what each fix moves. Then an optimization sprint, where the fixes get built.
The core is the parity gate: every build has to pass a screenshot-parity check — a pixel comparison, before and after, across page types — before it moves on. One visible difference and the build is rejected. You get the speed with no design change at all, and a rollback path ships with every deliverable.
A typical sprint works on what the visitor never sees:
- Video: re-encoding to adaptive streaming, fewer concurrent decoders, and a lighter payload on mobile.
- Images: a scripted, logged swap to modern formats with a full rollback log.
- Code: a smaller CSS bundle, deferred third-party scripts with fallbacks, and an LCP element made discoverable to the browser.
The flagship case — same tools, before and after.
−94%
page weight: 110 MB → 7 MB
13.8s → 3.2s
LCP, product page
#1 of 21
benchmark, beauty stores (mobile)
31/31
product pages pass LCP audit (was 8/31)
0
CLS — across all 38 builds
Audit → sprint → operate. Fixed entry points.
Fixed price · 1–2 weeks
Shopify Speed Audit
A full teardown with Lighthouse, GTmetrix and CWV against a measured baseline. You get a ranked fix list and projected gains before any code is touched.
DKK 25,000
(≈ EUR 3,350)
Fixed scope · 2–8 weeks
Optimization sprint
The fixes ship in small, reversible builds — each one approved against screenshot parity before it goes live.
from DKK 60,000
(≈ EUR 8,050)
Monthly · by scope
Operate
Speed has to be maintained as the theme changes. A retainer watches CWV and catches regressions before they reach customers.
Monthly fixed price by scope
For DTC brands where the design is the product.
This is written for stores where the visuals carry the brand: beauty, fashion and premium DTC with autoplay video, product film on every page and full-resolution imagery. When the store is heavy, you pay for it on mobile — in bounced traffic and lost conversion.
The usual answer is a relaunch that buys speed by cutting into the look. If that is off the table for you, that is exactly the constraint this engagement is built to resolve.
If the speed needs lifecycle automation on email and SMS behind it, the work connects to ouraudience intelligence.
Fair objections.
Do you change anything in the design?
No. Every build has to pass a screenshot-parity check — a pixel comparison, before and after, across page types — before it moves on. One visible difference and the build is rejected. You get the speed as pure engineering, and the design stays exactly as it was.
Does it work on a theme with heavy autoplay video?
Yes, and that is where the gains are largest. In the flagship case, 249 videos were re-encoded to adaptive streaming, concurrent video decoders were cut from 26 to 7, and the mobile video payload dropped from 23 MB to 1.25 MB — with no video looking any different.
What if the audit doesn't find enough to fix?
Then we say so. A Shopify Speed Audit delivers a ranked fix list with projected gains against a measured baseline. If there is nothing meaningful to win, you get that in plain language instead of a sprint that never moves the numbers.
How long does an engagement take?
The audit takes 1–2 weeks, an optimization sprint 2–8 weeks depending on scope. We measure the baseline before we build, so the effect is readable from day one in production.
Will the speed disappear on the next theme update?
The work ships documented and reversible, so your own team or our retainer can maintain it. The LCP element is made discoverable to the browser and CLS is held at 0 through every build — these are properties of the code, not one-off patches.
Ready for a faster store?
We start with a fixed-price audit — a ranked fix list and projected gains, before we touch the code.