Optimising performance to reduce environmental and financial impact

Half as many servers, and a better Valentine's Day than Christmas.
Optim perf Sylius

18 Nov 2026

Cadeaux.com saw its Valentine's Day outperform Christmas with half as many servers. A look back at the hunt for milliseconds, from audit to optimisation.

In short: after a rebuild, an audit and then profiling with Blackfire, the Cadeaux.com website had a better Valentine's Day than Christmas with half as many servers. Using fewer resources also means spending less energy and paying less for infrastructure.

The context

Cadeaux.com rebuilt its website from scratch on Sylius. To test it in real conditions, the client first launched it on the German market. Once that site was in production, they asked us for an audit so they could use it for the French market too.

The audit showed that the customisations made to Sylius did not follow its best practices. The work therefore focused first on internationalisation. The French site went live in November.

The problem

The Christmas period was very good commercially, but it exposed the site's weaknesses. Google reported performance issues on the listing pages and product pages, despite 10 web servers and the Fasterize cache. At the start of the year, the goal was clear: turn these pages "green" for Google.

The diagnosis: Blackfire

To track down every millisecond, I used Blackfire. This tool profiles a page and details what happens while it is generated: SQL queries (and how many), external API calls, cache calls, total time, CPU, network and memory.

Here is the profile of a page before optimisation, showing the use of the ORM.

Sylius ORM page listing produits

These resources are linked: less wasted time means less CPU, less memory and fewer servers under load. For example, the profile revealed several identical HTTP requests to the same third-party provider.

The optimisations

  • Cache: a one-day cache for external API calls (5 minutes on error), and caching of many pieces of data, each with a suitable lifetime.
  • Database: fewer SQL queries, and faster ones. Some go through Doctrine DBAL rather than the ORM.
  • Code: loop-based processing replaced with indexed arrays.
  • Front end: add-to-cart form loaded in JavaScript, images and product reviews lazy-loaded.

The result

These optimisations went live just before Valentine's Day. The before/after comparison of ORM usage shows the improvement:

Sylius ORM page listing produits - comparaison après optimisation

And here is the performance gain measured after all the optimisations:

Cadeaux.com amélioration temps de réponse suite aux optimisations.png

In the end, the site did better than at Christmas, with half as many servers.

What about your site?

Every project has its own hot spots, and the only way to find them is to measure. That is what an audit does: a report with examples taken from your code, a prioritised action plan and a high-level estimate. Our packages and prices are detailed on our dedicated page.

Discover our audits and their prices

If your site's performance does not meet your expectations, contact us to talk it over.