volkorn / case studies / torresol
development magento 1 → 2 optimization roadmap nl + de ongoing
torresol.
hello summer · goodbye legacy

torresol — from a stalled magento 1 to a fast, maintained magento 2

A Dutch market leader in fly curtains, in business since 1990. They came to us with one complaint: the store was painfully slow. We looked under the hood, found Magento 1 — and shipped the fastest, cheapest wins first.

client
Torresol Nederland
industry
Fly curtains, B2C · NL + DE
stack
Magento 2 · migrated from M1
status
Ongoing maintenance
part the curtain ↓
// the brief "the site is slow" — a diagnosis, not a spec

a symptom, a root cause, and a tight budget

Torresol arrived with a simple problem: the store was slow. Pages took forever, conversions suffered, and search rankings were slipping. They didn't ask for a migration — they asked for speed.

The audit told a bigger story. The store was still on Magento 1 — end-of-life, unsupported, security-frozen — and no amount of caching would fix that. The right answer was a migration to Magento 2, plus a real optimization pass on top.

But budgets were tight. So we didn't sell a big-bang rebuild. We built a priority-driven roadmap: every implementation was scored by impact vs effort, and we shipped the highest-impact, lowest-cost items first — so speed and revenue improved while the migration was still in motion.

Post-launch, we stayed on as their maintenance partner — patching, monitoring, and continuing to work through the backlog one prioritized ticket at a time.

// how we work when budgets are tight
  • Diagnose, don't guess — the reported symptom is rarely the full story
  • Score every ticket — impact vs effort, in the open, with the client
  • Ship the top of the list first — value compounds while the rest is built
  • Keep the roadmap live — reprioritize as data comes in, not once a quarter
  • Stay after launch — maintenance is where the compounding really happens
// the diagnosis why the store felt slow

magento 1, stalled. magento 2, moving.

The reported symptom was speed. The real cause was a legacy platform. Same needles, two very different dashboards.

// before

magento 1 — end of life

0
Unsupported since June 2020 · no security patches · slow admin · brittle to any change
migration
// after

magento 2 — fresh & fast

0
Actively supported · modern stack · faster storefront · room to grow
// pagespeed values illustrative of the platform shift; real numbers available on a call
// how tight budgets ship the actual backlog, sorted by impact ÷ effort

the roadmap, priced honestly

Not a slide deck. Not a big bang. A live, ranked backlog — the top items ship first because that's where speed and revenue live. Everything else waits its turn.

#
implementation
impact
effort
status
P1
Full-page & block cache tune-upthe fastest measurable win — before migration even starts
95
S
shipped
P2
Image pipeline & lazy loadingcatalog imagery slimmed and served on demand
90
S
shipped
P3
Magento 1 → 2 migrationdata, catalog, orders, redirects — the platform jump
98
L
shipped
P4
Frontend performance passcritical CSS, JS trimming, third-party audit
82
M
shipped
P5
Checkout hardening & PSP tunefewer drop-offs at the money moment
76
M
shipped
P6
SEO recovery & redirect mappreserve rankings across the platform jump
68
M
shipped
P7
Made-to-measure configurator polishfly curtains are sold by dimension — the config is the store
60
M
in progress
P8
DE storefront parity refreshkeeping the German storefront lock-step with NL
48
S
queued
P1–P3 shipped in the first phase — biggest impact per euro
impact = expected lift · effort = dev-days
reprioritized monthly, not once a quarter
// the live storefront torresol.nl, on magento 2

the storefront today

NL is the flagship, DE runs in parallel — same catalog, localized where it needs to be.

torresol.nlmagento 2
torresol.nl — Magento 2 storefront rebuilt and maintained by Volkorn
torresol.nl homepage migrated & maintained by volkorn
// the delivery track value first, migration second

how the roadmap actually ran

phase 01 · audit

diagnosis

Frontend and backend audit, admin walkthrough, hosting review. Confirmed Magento 1 as the root cause and mapped every quick win that could ship before migration.

phase 02 · scoring

the priority list

Every implementation scored on impact vs effort with the client in the room. The top of the list became the plan; the rest became the backlog.

phase 03 · quick wins

value before migration

Cache tuning, image pipeline, third-party diet — measurable speed improvements shipped while the M2 build was still being scoped.

phase 04 · migration

magento 1 → magento 2

Data, catalog, customers, orders and redirects moved to a fresh Magento 2 build with the storefront rebuilt on a modern theme foundation.

phase 05 · optimization

post-launch performance pass

Critical CSS, JS trimming, checkout hardening, SEO recovery — each ticket pulled from the ranked backlog in order.

phase 06 · now

maintenance & roadmap

We stayed on as their maintenance partner. The backlog is still live, still reprioritized monthly, still shipping.

// what the engagement delivered platform, speed, and a working backlog

what changed for torresol

M1 → M2

platform brought back to life

Off end-of-life Magento 1 and onto a supported, security-patched Magento 2 stack — the change nothing else could substitute for.

faster

speed as a first-class feature

Caching, image strategy, critical CSS and a lean third-party stack — the original complaint, resolved and monitored.

P1 first

priority-first delivery

Every ticket scored, ranked, and shipped in order — so the highest-value work landed inside the budget the client actually had.

ongoing partnership

Continuous maintenance and a live backlog — reprioritized monthly, so the store keeps improving between big projects.

// representative engagement scope; commercial figures are confidential to the client

every project has a wishlist. good ones ship a roadmap.// score every ticket · ship the top of the list first · keep the list alive

// your turn stuck on a legacy platform or a slow storefront?

let's discuss your project

Magento migrations, roadmap-driven optimization, long-term maintenance — send us the symptom, we'll do the diagnosis. Free estimate included.