Seitenreport Seitenreport
Performance in Shopware

Fix LCP too slowly in Shopware

Determine the largest visible element. In Shopware, you check Storefront theme, extensions and dynamic product view.

Storefront theme, extensions and dynamic product view

Determine whether a category banner or product image plays the main role. Check the actual thumbnail size shipped and the start time of the request.

Limit slow resource or interaction to theme, extension, or external engagement. An extensive experience world can have other bottlenecks than a simple product page.

Where to check the setting in Shopware

In the network protocol, check the Storefront bundles, product images and additional loaded app resources. Compare the active theme in a test environment without the suspicious extension. Document sales channel and device context for re-measurement.

Example of this specific finding

Illustrative control case: The performance trace identifies the hero photo as an LCP element. His request starts only after a script, although the image should be visible immediately.

follow-up audit in Shopware

After a targeted change variant selection, filter and shopping cart test. Measure response time, download and browser work separately, instead of just looking at the server cache.

Examine request start time, download time and render delay separately. Make image source findable early and check the selected size and prioritization.

Derogations and scope

The LCP element can change per device or view. Once measured, a value is not a complete picture of the field data.

Related: Shopware 6 with Storefront. Self-hosted and SaaS offer different access and configuration options; view your own headless frontends separately.

Classify the general error

Definition, system-independent causes and further correction examples: Determining the Largest Visible Element

Configuration and test signal documentation

web.dev: Examining charging performance and interaction

Related performance errors in Shopware