The fixes that follow the audit, quoted per item, so you never buy an open-ended optimisation project.
Wij bouwen en beheren onder meer Gripzakjes.nl, Pharmaprofit.be en Modernemeubels.com.
Magento 2 has a reputation for being heavy. It is a large application, but the stores we are asked to rescue are rarely slow because of the framework. They are slow because of decisions made around it over the years.
The pattern repeats. Someone switched off a cache to debug a problem in 2022 and never switched it back on. An extension runs a query on every page load. The catalogue grew from 2,000 to 40,000 products and indexing was never revisited. Product images are uploaded at 3000 pixels wide and scaled down in the browser. None of these are exotic, and all of them are fixable.
We work through them in order of impact, verify each change against the baseline from the audit, and stop when the numbers say the remaining work is not worth what it costs.
Scope comes from your audit, so no two sprints are identical. These are the areas the work usually falls into.
The layer where most of the time is lost.
What the browser has to do before anything appears.
The most common single cause we find.
We compare against the baseline after each batch. If a change does not move the number, we say so instead of adding it to a list of things we did.
You see what each fix costs and what it is expected to return, so you can stop at the point where the maths stops working. No open-ended retainer.
We run Magento stores in production, including a catalogue of more than 40,000 products. We recognise these patterns because we have had to solve them for ourselves.
Nothing goes to your live store without being verified on a copy. Performance work touches caching and indexing, which is exactly where a careless change takes a shop offline.
Fixed phases with a fixed price per phase. No open ending.
Lab and field data per page type, so we compare what real visitors experience against what a test tool reports.
Week 1Where the milliseconds go: server, cache, database, theme or third-party script. You get the findings ranked by impact and effort.
Week 1The fixes that pay off immediately, applied on staging first and verified before they go live.
Week 2The heavier items from the diagnosis, quoted separately so you decide what is worth doing.
Week 3 to 4The same measurements again, side by side with the starting point, plus what to watch from here.
Week 5We do not only tune other people’s Magento stores. We build and maintain them, which is why we recognise the patterns quickly.
Magento webshop, hosting en doorlopend onderhoud
Magento webshop voor de apothekersmarkt met ruim 40.000 producten, automatische categorisering en afgeschermde toegang voor vakgenoten
Een toekomstvaste Magento 2-webshop met een fris design en betrouwbare, gespecialiseerde hosting.
The questions we get most about this.
Quick wins usually land within two weeks of the audit. Structural work runs three to four weeks depending on what came out, and we agree the scope before we start.
Yes, and often that is the cheapest arrangement. We diagnose and specify, your team implements, we verify. We are happy to work either way.
Then the version is part of the conversation. Releases that have reached end of life miss performance features and no longer receive security patches, so tuning them is often money spent twice. We will tell you plainly whether upgrading first is the better use of your budget.
Not in a performance sprint. If the theme itself is the ceiling, that becomes a separate conversation about a frontend rebuild, quoted separately.
It decays, honestly. Updates, new extensions and catalogue growth all pull it back. That is why we offer monitoring, so you find out before your customers do.
One partner for your entire store. See what else we build and run.
Tell us your challenge. Within one working day we schedule a free 30-minute online consult, no sales talk, just concrete insights.