Sylius

Web performance consultant for Sylius

Optimize performance on Sylius stores

Sylius is modern Symfony-based, modular and headless-ready e-commerce. Its flexibility opens advanced Doctrine and HTTP cache optimizations. I work on the Symfony angle of Sylius for stable Core Web Vitals on enterprise stacks.

100% satisfied clients Data 2023-2026 8+ years XP 35+ clients partnered
View my client cases

They trust me

CHANEL
DIOR
Decathlon
April Moto
SiriusXM
Make Up Forever
Camif
RIMOWA
Jimmy Fairly
Wecasa
Chronovet
CHANEL
DIOR
Decathlon
April Moto
SiriusXM
Make Up Forever
Camif
RIMOWA
Jimmy Fairly
Wecasa
Chronovet

Sylius symptoms calling for an audit

Sylius inherits Symfony's characteristic bottlenecks, amplified by e-commerce model richness.

🔁 TTFB drifting on cart, checkout and order

Doctrine N+1 on Order items, adjustments, addresses. Symfony Profiler profiling exposes the pattern, refactoring drops TTFB 40 to 70%.

📦 Slow category listings with many attributes and variants

Object hydration on listings consumes memory and CPU. Moving to scalar queries (getArrayResult()) or array hydration divides consumption and accelerates rendering.

💾 Doctrine Result Cache unused

Channels, Currencies, Locales, Taxonomies re-queried on every page. Doctrine second-level cache (via Redis or APCu) serves them from memory — systematic TTFB gain.

📡 No HTTP cache nor ESI on public pages

Product pages, categories, home regenerated on every visit. Set up Symfony HttpCache or Varnish + ESI on header (cart, user). Perceived TTFB collapses.

🖼️ Product images without next-gen formats nor fetchpriority

Native Sylius doesn't generate WebP/AVIF by default. LiipImagineBundle integration with WebP/AVIF filters + fetchpriority on LCP image gains 200 to 500ms.

⚙️ PHP 7.x or misconfigured opcache

PHP 8.x + opcache + JIT divides Sylius execution time by 2 to 4. PHP upgrade and proper activation (memory_consumption, max_accelerated_files) is mandatory.

Sylius optimization methodology

4 steps to transform your performance

1
Step 1

1. Symfony Profiler or Blackfire profiling

Identify Doctrine N+1, slow queries, costly Twig templates. Map LCP-critical pages.

2
Step 2

2. Doctrine optimization

Explicit eager loading on Order, scalar queries on listings, second-level cache on Channels/Taxonomies/Currencies, missing SQL indexes.

3
Step 3

3. HTTP cache + ESI

Set up Symfony HttpCache or frontal Varnish, ESI on header (cart, user info), disciplined Cache-Control on public pages.

4
Step 4

4. Frontend and monitoring

Twig optimization (pre-compiled cache, defer JS), modern image formats via LiipImagine, fetchpriority on LCP. Install Core Web Vitals monitoring.

Mission commitments

-50% typical Sylius TTFB
Doctrine hydration optimized
HTTP cache + ESI activated
Continuous Sylius stack partnered
FAQ

Frequently asked questions

Sylius vs Magento for a B2C project?
Sylius is more modern, lighter code-side, more flexible for custom integrations. Magento (Adobe Commerce) is more complete by default (B2B, advanced marketing, page builder) but also heavier. For a project with strong customization needs and where the Symfony ecosystem is mastered, Sylius is defensible. For a standard mid-market project, Magento + Hyvä remains relevant.
Is Sylius headless more performant?
Sylius Plus exposes a GraphQL API (ShopAPI) for headless fronts (React, Vue, Astro). Headless doesn't automatically make it faster — performance depends on the front's quality and the cache strategy. For public sites with critical SEO, a well-done SSR front (Next.js, Nuxt) outperforms a monolithic Sylius. To be evaluated project by project.
Does Sylius support green Core Web Vitals?
Yes, provided you apply the usual Symfony optimizations (Doctrine, HTTP cache, opcache) and care for the frontend (image formats, deferred JS, fetchpriority). Several Sylius sites in production hold green Core Web Vitals.
How are your Sylius engagements structured?
My Sylius engagements run long-term. The first sprint frames the stack (Doctrine, HTTP cache, opcache, Twig frontend) and the roadmap. Following sprints work optimizations with continuous measurement and validation. On an active Sylius store, Order and Channels evolve — the engagement protects TTFB against that evolution.

Optimize your Sylius for stable Core Web Vitals

Doctrine optimized
HTTP cache + ESI
Rationalized frontend
100% satisfied clients
Data 2023-2026
Testimonials

What my clients say

Excellent work.
Paul has significantly improved the site's speed and perfectly aligned it with Google's recommendations.
Professional, thorough, and efficient, I highly recommend.

Nicolas - April Moto

Digital & E-commerce Director

We are very satisfied with Paul's work. He is quick, available, and particularly effective. Since his arrival, very good results have been observed, both in terms of performance and responsiveness. A real asset for our team.

Léo - Luxury brand

E-commerce Product Owner

I don't know if we've said it enough.
But if you want to improve your loading speed,
Make Google happy and get your Core Web Vitals in the green,
Contact Paul Delcloy.

Florian Darroman - Les Makers

Co-founder

Sylius, modern and flexible Symfony e-commerce

Sylius is an open source e-commerce built on Symfony, popular for B2C and B2B mid-market projects with strong customization needs. Its modularity (Resource, State Machines, Promotions, Channels) lets you model complex marketing stacks. Technically, Sylius inherits Symfony's strengths and traps: powerful but N+1-exposed Doctrine ORM, available but to-be-configured HTTP cache, Twig frontend to master.

The e-commerce web performance optimization angle on Sylius is essentially Symfony: Doctrine profiling, second-level cache, HTTP cache + ESI on dynamic fragments (cart, user), opcache + PHP 8.x JIT, and Twig frontend optimization (defer JS, image formats, fetchpriority).

Sylius Doctrine, first work-stream

The Sylius Order entity accumulates numerous relations: items, adjustments, customer, payments, shipments, channel, currency. Without Doctrine optimization (explicit eager loading, scalar queries for listings, second-level cache on stable references), a cart or order page can trigger 30 to 80 SQL queries.

Symfony Profiler or Blackfire diagnosis exposes these patterns. Refactoring (createQueryBuilder with targeted joins, setHydrationMode(Query::HYDRATE_ARRAY) on exports, EnableQueryCache on stable references) drops TTFB 40 to 70%.

HTTP cache + ESI on Sylius

Sylius natively benefits from the Symfony HTTP cache ecosystem. For a B2C store where public pages (home, product pages, categories) are identical for all anonymous users, using the Symfony reverse proxy or Varnish + ESI on dynamic fragments (header with cart, user info) typically divides TTFB by 3 to 5.

This architecture demands modeling discipline: disciplined Cache-Control headers, properly scoped ESI tags, invalidation strategy planned. That's what separates fast production Sylius sites from sophisticated-but-slow ones.