Full-page cache, catalogue output and browser work
Observe product gallery, pricing areas, and reloaded customer items. Personalized content can only change the space distribution after the initial HTML.
Distinguish slow server responses from extensive theme/extension work in the browser. A warm full-page cache can provide a quick HTML retrieval, although variant selection or filters are slow to respond afterwards.
Where to check the setting in Magento
Compare cache hit and cache miss of the affected storefront page. After that, check the specific browsing work of galleries, filters and third-party scripts. A fast full-page cache does not automatically fix a sluggish interaction after loading.
Example of this specific finding
Illustrative control case: When loading an advertising space, the article slides downwards. The shifted text element is measured, but the missing space reservation is on the banner above it.
follow-up audit in Magento
Test comparable product and category pages under documented cache condition. Price, stock and personal content must not be obsolete or mixed by an optimization.
Track the layout shift recording up to the triggering element. Reserve space in advance and also test consent banners, fonts and reloaded content.
Derogations and scope
A single laboratory measurement does not describe all user states. Classify targeted user interactions and late shifts separately.
Reference: Magento Open Source or Adobe Commerce with classic storefront. Consider store views and extensions; other storefront architectures have their own configurations.
Classify the general error
Definition, system-independent causes and further correction examples: The shifting element is not always the cause