November 20, 2026
Page builders like Breakdance, Bricks and Elementor make it easy to design a beautiful site, and just as easy to fail Google’s Core Web Vitals. If PageSpeed Insights shows red for LCP, INP or CLS, this guide explains what each metric means, why page builder sites fail it, and the fixes that actually move the numbers. These are the steps we use when we fix Core Web Vitals on WordPress sites at WPBuilderPros.
The three Core Web Vitals in plain words
| Metric | What it measures | Good score |
|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content (usually the hero image or headline) appears | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How fast the page reacts when someone taps or clicks | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | 0.1 or less |
Google uses real-user data (the “field data” in PageSpeed Insights and the Core Web Vitals report in Search Console), measured at the 75th percentile of visits.
How to fix LCP
- Optimize the hero image: WebP or AVIF, the right size for each screen, and no lazy loading on the first image.
- Preload the LCP image or give it high fetch priority.
- Use faster hosting and page caching. A slow server delays everything.
- Reduce render-blocking CSS and JavaScript in the head.
- Host fonts locally and preload the main one.
- Avoid sliders and videos as the hero unless you really need them.
How to fix INP
- Delay or remove heavy third-party scripts: chat widgets, trackers, ad scripts and pop-up tools.
- Cut unused plugins and addon features that load JavaScript on every page.
- Avoid heavy animation libraries on mobile.
- Break up long tasks in custom code.
How to fix CLS
- Set width and height (or aspect ratio) on images, videos and embeds.
- Reserve space for ads, cookie banners and anything injected later.
- Use
font-display: swapwith a matching fallback font so text does not jump. - Do not insert content above existing content after the page loads.
Builder-specific tips
- Breakdance: use its performance settings to turn off what you do not use. See our guide to Breakdance performance settings.
- Elementor: switch to containers, turn on its performance experiments and limit global widgets. Read containers vs sections and columns.
- Bricks and Oxygen: keep custom scripts and fonts lean; these builders are fast by default.
- All builders: fewer nested containers, fewer fonts and fewer animations.
How to test your fixes
- Run PageSpeed Insights on your key pages (home, main service, contact) on mobile.
- Check the Core Web Vitals report in Google Search Console.
- After changes, use “Validate fix” in Search Console. Field data takes about 28 days to fully update.
FAQ
Are page builders bad for Core Web Vitals?
No. A well-built Breakdance or Bricks site can pass easily. Problems come from heavy images, too many plugins and third-party scripts.
Why is my PageSpeed score good but Core Web Vitals still fail?
PageSpeed’s score uses a lab test, while Core Web Vitals use real visitors on real devices and networks. Fix for real users first.
How fast can you fix it?
Most sites improve within a few days of work. Search Console then needs about four weeks of new data to confirm.
Want it fixed for you? WPBuilderPros speed optimization includes before and after scores for every key page.




