Web performance consultant for SAP Commerce Cloud
Optimize performance on SAP Commerce Cloud sites
SAP Commerce Cloud (formerly Hybris) powers complex enterprise B2B and B2C e-commerce. Its heavy stack (Java + Spring + JSP or Spartacus) demands multi-layer optimization. I work on OCC backend, response cache, JVM and Spartacus frontend for stable Core Web Vitals.
They trust me
SAP Commerce symptoms calling for an audit
SAP Commerce sites show characteristic bottlenecks on OCC, Solr, JVM and frontend.
🐌 TTFB above 1.5 seconds on product pages
Serial synchronous OCC calls, uncalibrated response cache, slow Solr responses. Diagnosis identifies each contribution, tuning drops TTFB below 400ms.
🔍 Slow category listings with non-optimized Solr
Poorly indexed Solr (faceting, sorting, query parsing) responds in 500ms to 2s on catalogs of several thousand SKUs. Solr tuning + cache fragments drops that time below 200ms.
☕ JVM heap miscalibrated, garbage collection penalizing
Heap too small → frequent GC, latencies. Heap too large → long GC, user freezes. JVM tuning (G1GC, ZGC on Java 17+, heap sizing) stabilizes performance under load.
📦 Spartacus bundle above 1 MB on first load
Undisciplined Angular lazy modules, unused dependencies, incomplete code splitting. An ng build + bundle analyzer audit identifies each contributor.
🖼️ Product image without NgOptimizedImage nor fetchpriority
Spartacus doesn't systematically use NgOptimizedImage. Generalization on strategic pages + fetchpriority on LCP gains 200 to 500ms of LCP.
🔁 Blocking synchronous OCC calls in components
Spartacus components making synchronous OCC calls block rendering. Moving to RxJS observables + Suspense pattern frees rendering and improves INP.
SAP Commerce optimization methodology
4 steps to transform your performance
1. Complete backend audit
OCC diagnosis (latency, parallelism, response cache), Solr audit (indexing, tuning), JVM audit (heap, GC, threads), application code profiling (Java Mission Control where relevant).
2. Response cache and Solr optimization
Cache fragments calibration, OCC response cache configuration, Solr tuning (analyzers, shards, sorting), MySQL/HANA tuning where applicable.
3. Spartacus or JSP frontend
Spartacus optimization (lazy modules, OnPush, NgOptimizedImage, SSR where applicable) or in-place JSP/Accelerator optimization. Angular bundle audit.
4. Continuous monitoring
Install Core Web Vitals monitoring (SpeedCurve, mPulse based on context), APM instrumentation (Dynatrace, Datadog) if not already in place.
1. Complete backend audit
OCC diagnosis (latency, parallelism, response cache), Solr audit (indexing, tuning), JVM audit (heap, GC, threads), application code profiling (Java Mission Control where relevant).
2. Response cache and Solr optimization
Cache fragments calibration, OCC response cache configuration, Solr tuning (analyzers, shards, sorting), MySQL/HANA tuning where applicable.
3. Spartacus or JSP frontend
Spartacus optimization (lazy modules, OnPush, NgOptimizedImage, SSR where applicable) or in-place JSP/Accelerator optimization. Angular bundle audit.
4. Continuous monitoring
Install Core Web Vitals monitoring (SpeedCurve, mPulse based on context), APM instrumentation (Dynatrace, Datadog) if not already in place.
Mission commitments
Frequently asked questions
Should I migrate to Spartacus?
SAP Commerce vs Magento Adobe Commerce for performance?
Composable Storefront vs Spartacus on SAP Commerce?
How are your SAP Commerce engagements structured?
Optimize your SAP Commerce Cloud
Data 2023-2026
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
SAP Commerce, enterprise platform and multi-layer complexity
SAP Commerce Cloud (formerly Hybris) powers complex enterprise e-commerce — industrial B2B, international brands, multi-channel retail. Its Java + Spring + Solr stack is powerful but one of the heaviest on the market. Poorly optimized SAP Commerce sites typically show TTFB above 1.5 seconds, LCP above 4 seconds, and drifting INP.
The e-commerce web performance optimization angle on SAP Commerce is multi-layer: OCC (OmniCommerce Connect) well-used, response cache calibrated, Solr indexation optimized, JVM heap and garbage collection tuned, and modernized frontend (Spartacus instead of legacy JSP).
OCC and response cache, backend levers
OCC is the SAP Commerce REST API, notably used by Spartacus as a front. A good OCC strategy consists of:
- Caching stable responses (catalog, products, taxonomies) in short-term response cache
- Parallelizing OCC calls on rich pages (recommendations, listings, personalized content)
- Limiting OCC calls in loops via batching
Without this discipline, a Spartacus product page can trigger 10 to 20 serial OCC calls, adding latencies. Well-orchestrated, you drop below 200ms of cumulative latency.
Spartacus, the modern frontend
Spartacus is the official open source Angular frontend for SAP Commerce. The recommended evolution by SAP versus the historical JSP frontend. Spartacus enables much more accessible Core Web Vitals, provided you respect Angular best practices (lazy modules, OnPush, SSR, Image component).
For sites still on JSP / Accelerator, in-place optimization remains possible (JSP cache, Solr tuning, JVM, legacy frontend JS) with more modest gains. Migration to Spartacus is an enterprise project (16 to 32 weeks) but often justified over time by performance, SEO and maintenance gains.
Other expertise Technologies
Angular
Angular optimized: lazy modules, OnPush change detection, SSR Universal or Analog, signals, zone.js elimination. Stable Core Web Vitals on enterprise SPAs.
Learn more
Astro
Astro optimized: islands architecture, image optimization, view transitions, content collections. Near-static sites with green Core Web Vitals.
Learn more
Drupal
Drupal optimized: Render API and cache contexts, Dynamic Page Cache + BigPipe, Views performance, MySQL tuning. Core Web Vitals green on strategic templates.
Learn more