performance-budget

Validating EDS LCP performance requires measuring HTML, eager CSS/JS, preloaded fonts, and above-fold images that load before the LCP element. You compare these byte-level resource measurements against the 100KB budget limit to identify what causes regressions.

Checking E-L-D loading phases involves verifying resource compliance with Eager, Lazy, and Delayed expectations for EDS. You validate that third-party scripts are moved into the delayed phase to prevent them from blocking the Largest Contentful Paint.

The LCP performance budget for AEM Edge Delivery Services pages limits total transfer size of critical-path resources to 100KB. This includes HTML, eager CSS/JS, preloaded fonts, and above-fold images required before the LCP element renders.

To get optimization recommendations for resources exceeding the 100KB budget, you analyze a graded budget breakdown. This outputs targeted per-resource fixes including image format changes, font preloading limits, and moving third-party scripts into the delayed phase.

Yes, you can use this performance budgeting approach for pre-launch audits. It checks whether third-party or block assets are loading in the wrong E-L-D phase and provides a defensible, resource-level explanation of what pushes pages over budget.