Seitenreport Seitenreport
Performance in Shopware

Fix INP too high in Shopware

Name the slow interaction concretely. In Shopware, you check Storefront theme, extensions and dynamic product view.

Storefront theme, extensions and dynamic product view

Measure filters, variant selection and off-canvas shopping cart individually. The cause can lie in a storefront plugin and only occur after an interaction.

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: A click on the variant filter waits for a long JavaScript task before a visible reaction appears. The delay concerns a concrete interaction.

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.

Repeat the problematic interaction in the performance trace, split up long tasks and reduce unnecessary work. Then measure the same interaction again.

Derogations and scope

INP is not a pure charging time code. A fast first side structure does not preclude slow later operation.

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: Name the slow interaction concretely

Configuration and test signal documentation

web.dev: Examining charging performance and interaction

Related performance errors in Shopware