Skip to main content

Page Builder LCP Problems in Magento 2

1 min read Feb 25, 2026
Magento 2 Performance Core Web Vitals LCP

The Problem

Magento 2 Page Builder is powerful but introduces significant Largest Contentful Paint (LCP) delays.

Typical LCP scores:

  • Without Page Builder: 1.5-2.5s ✅
  • With Page Builder: 4.5-6.5s ❌

This hurts both user experience and SEO rankings.

Why Page Builder Hurts LCP

1. Render-Blocking CSS

Page Builder loads heavy CSS files:

<link rel="stylesheet" href="styles/pagebuilder.css">

This blocks rendering until downloaded.

2. Large Image Sliders

Hero sections with unoptimized images:

<img src="hero-banner.jpg" width="2400" height="1200">

Often 500KB+ per image.

3. JavaScript Dependency

Page Builder requires JavaScript to initialize, delaying render.

Fixes

1. Optimize Images

Convert to WebP or AVIF:

cwebp hero-banner.jpg -o hero-banner.webp

Add responsive images:

<img 
    src="hero-banner-mobile.webp" 
    srcset="hero-banner-mobile.webp 768w, 
            hero-banner-desktop.webp 1920w"
    width="1920" 
    height="600"
    loading="eager"
>

2. Inline Critical CSS

Extract Page Builder critical CSS and inline it:

<style>
    .pagebuilder-row { display: flex; }
    .pagebuilder-column { flex: 1; }
</style>

Defer the rest:

<link rel="preload" href="pagebuilder.css" as="style" onload="this.rel='stylesheet'">

3. Remove Unused Page Builder Modules

In di.xml:

<type name="Magento\PageBuilder\Model\Config">
    <arguments>
        <argument name="widgets" xsi:type="array">
            <item name="slider" xsi:type="string">false</item>
        </argument>
    </arguments>
</type>

4. Use Static Blocks Instead

For simple content, avoid Page Builder. Use static blocks with plain HTML.

Monitoring

Use Google PageSpeed Insights:

https://pagespeed.web.dev/

Track LCP improvements after each optimization.

Results

After optimizations:

  • Before: LCP 5.2s
  • After: LCP 2.1s ✅

This brings you into the "Good" range for Core Web Vitals.

Conclusion

Page Builder is convenient but expensive for performance. Use it strategically and optimize aggressively.