Core Web Vitals
Improve LCP, CLS and INP — the speed metrics Google ranks on.
// Growth · Performance
Speed up a slow Shopware shop — better Core Web Vitals, caching, database and template tuning for higher rankings and conversion.
// What you get
Improve LCP, CLS and INP — the speed metrics Google ranks on.
HTTP cache, Redis and Varnish tuning for instant repeat loads.
Find and fix slow queries and indexes that drag the shop down.
Compress and lazy-load images, CSS and JS for lighter pages.
Remove render-blocking and heavy template logic that slows pages.
Advise on hosting and set up a CDN for fast global delivery.
// Why it matters
Every extra second of load time costs conversions, and Google ranks slow shops lower. Codewerk Solutions runs a full Shopware performance audit — Core Web Vitals, caching, database queries, template logic, images and hosting — then fixes the bottlenecks that actually matter. We measure before and after, so you can see the improvement in real numbers.
The result is a shop that loads fast, ranks better and converts more visitors into buyers — one of the highest-return investments you can make in an existing store.
// In detail
What we actually do under the hood — so you can judge the work, not just the promise.
We start by measuring, not guessing: TTFB, the query profiler on a production-sized catalogue, and the real field data from the Chrome UX Report. Then we fix causes in order — HTTP cache, N+1 queries in plugins, missing indexes, synchronous ERP calls during render, and shared hosting CPU.
HTTP cache and reverse proxy in front, Redis for sessions and object cache behind, Elasticsearch when the catalogue justifies it. Cache invalidation is tagged, so a price change invalidates exactly what it should — and you never have to flush everything at 10 a.m. on a Monday.
Core Web Vitals are the overlap between performance and SEO. We target LCP under 2.5s, CLS under 0.1 and INP under 200ms on the pages that actually carry revenue — the category listing, the product page and the cart, not the homepage everyone benchmarks.
// FAQ
On an unoptimised Shopware shop, a 2–4× improvement in TTFB is common and largely comes from caching and fixing a handful of bad queries. We tell you the expected range after a paid audit, not before.
Below roughly 10,000 simple products, usually not — the database is fine and Elasticsearch is a second system to operate for nothing. Above that, or with heavy faceting and typo tolerance, it pays for itself quickly.
Caching is where it can, which is why prices and stock are never cached for minutes. Everything is rehearsed on staging with real data, and we agree in writing what must always be live rather than cached.
Send a short brief — we reply within one business day.