Apps, animations and embedded resources
First, identify the largest visible element. A background video, gallery, or third-party app each requires a different correction than a simple image.
Limit the bottleneck to a specific element, such as a large gallery or an external app. Platform-internal resources cannot be exchanged freely like their own server files.
Where to check the setting in Wix
Compare a simple page with the affected gallery, video or app page. Test-wise reduce the suspicious integration and measure again under the same conditions. Platform resources cannot be configured like files on your own web server.
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 Wix
Compare a reduced test page or controlled element change under the same conditions. Check central forms and app functions after removing an integration.
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.
Reference: published Wix/Wix Studio websites. SEO settings differ by static page, dynamic page type and installed app; do not require a freely managed server configuration.
Classify the general error
Definition, system-independent causes and further correction examples: Determining the Largest Visible Element