Beaver Builder Setup: Custom Modules & Optimization for WordPress

Beaver Builder Setup: Custom Modules & Optimization for WordPress

When working with page builders, bloated code and slow loading are common issues. Elementor, despite its popularity, generates tons of unnecessary wrappers and scripts that hurt LCP and TTFB. Beaver Builder solves this: its code is clean, predictable, and performance is 30% higher. We use it in projects with strict Core Web Vitals requirements — over 5 years of experience and 30+ successful implementations.

Beaver Builder isn't just 'another builder.' Its architecture delivers three key benefits: clean HTML (each module outputs exactly the markup you defined, no clutter), update stability (the plugin rarely breaks existing content, unlike competitors), and an API for development (you can extend functionality with custom modules without hacks). Compare with Elementor: a typical Beaver Builder page weighs 40% less, and LCP drops by 0.8–1.2 seconds on average. These are results from our measurements on dozens of projects. We guarantee clean code and documentation after every project.

How Beaver Builder Affects Core Web Vitals

Builders like WPBakery generate tons of nested divs. Beaver Builder does the opposite: minimal wrappers, only semantic tags. This directly improves LCP (the heaviest block loads faster) and reduces TTFB due to smaller HTML size. Moreover, Beaver Builder doesn't load its scripts on pages without its blocks, unlike Elementor, reducing total page weight and speeding up INP. If your project is on WordPress and you focus on Core Web Vitals, setting up Beaver Builder is the right choice.

Why Order Custom Modules?

Without programming skills, you can't add specific functionality — sliders, calculators, interactive maps. We develop modules for your task using the standard API. Here's a simple module with an icon and heading:

// my-module/my-module.php
class MyTextIconModule extends FLBuilderModule {
    public function __construct() {
        parent::__construct( [
            'name'            => 'Text + Icon',
            'description'     => 'Text with icon',
            'category'        => 'My Modules',
            'partial_refresh' => true,
            'dir'             => __DIR__,
            'url'             => plugins_url( '', __FILE__ ),
        ] );
    }
}

FLBuilder::register_module( 'MyTextIconModule', [
    'general' => [
        'title'    => 'General',
        'sections' => [
            'content' => [
                'title'  => 'Content',
                'fields' => [
                    'title' => [
                        'type'  => 'text',
                        'label' => 'Heading',
                    ],
                    'icon' => [
                        'type'  => 'icon',
                        'label' => 'Icon',
                    ],
                ],
            ],
        ],
    ],
] );

The module template (frontend.php) receives data via $settings:

// my-module/includes/frontend.php
<div class="my-text-icon">
    <?php if ( $settings->icon ) : ?>
        <i class="<?php echo esc_attr( $settings->icon ); ?>"></i>
    <?php endif; ?>
    <h3><?php echo esc_html( $settings->title ); ?></h3>
</div>

What Problems Does Beaver Builder Setup Solve?

How We Set Up Beaver Builder for Your Project

The process consists of 5 stages:

Step 1. Installation and Global Settings

We activate the appropriate version (Lite free, Standard/Pro/Agency paid). In Global Settings we set breakpoints (Medium ≤ 992px, Small ≤ 768px), module margin 20px, fonts. This is the foundation for all layouts.

Step 2. Creating Saved Templates

Beaver Builder allows saving rows, columns, modules, and entire layouts as templates. They are stored as fl-builder-template posts. This is convenient for reusing blocks across pages.

Step 3. Custom Module Development

If built-in modules are insufficient, we write our own. The API is well-documented: extend FLBuilderModule, describe fields in register_module(), create frontend.php. See example above.

Step 4. Integration with Beaver Themer and ACF

Beaver Themer is a separate plugin for creating header/footer templates, archives, 404 pages, etc. Display conditions are set like in Elementor Pro. Using field connections (the lightning button), we link ACF fields to modules — this allows dynamic content without programming.

Step 5. Performance Optimization

Beaver Builder caches CSS in wp-content/uploads/fl-builder/cache/. After changes we clear cache via Settings → Tools → Clear Cache or programmatically:

FLBuilderModel::delete_asset_cache_for_all_posts();

Plus: Beaver Builder does not load its scripts on pages without its blocks, unlike Elementor. This reduces total page weight.

What's Included in Beaver Builder Setup (Deliverables)

• Installation and activation of the required plugin edition
• Global style configuration (fonts, margins, breakpoints)
• Creation of saved templates for rows, modules, layouts
• Development of up to 5 custom modules (more discussed separately)
• Integration with ACF and Beaver Themer (up to 3 templates)
• Cache setup and asset purging
• Documentation for created modules (field list, settings description)
• Access transfer and editing instructions

Typical Mistakes When Working with Beaver Builder

Cache conflict: if the page doesn't update after changes, clear the plugin cache and server cache. Incorrect CSS in custom modules: use class prefixes to avoid theme conflicts. Template loss when switching themes: templates are stored in the database as fl-builder-template posts, not tied to the theme, but may display incorrectly. Test on staging.

Timelines and Cost

Estimated timelines: basic setup + 5–8 pages — 1 to 2 days; custom modules, Beaver Themer, ACF — 2 to 4 days. Cost is determined individually after analyzing your project. Get a consultation — we'll assess the scope and give you a price within 1 day.

Beaver Builder is a mature product with an open architecture, recommended by the WordPress community. Order a turnkey setup: we guarantee clean code, performance, and documentation. Just contact us — we'll discuss the details.

WordPress Development: Custom Themes, Plugins, and WooCommerce

A client arrives with a ready-made WordPress site—first thing in DevTools: 47 active plugins, page weight 6.8 MB, TTFB 2.4 s, five conflicting jQuery versions in the console. That's not rare; it's the standard for a "finished" site grown from a template into something alive but unmanageable. We solve such problems end-to-end—from audit to deployment. Get in touch—we evaluate your project in one business day.

WordPress holds 43% of the CMS market (Wikipedia)—not because it's perfect, but because it's predictable, extensively documented, and has an ecosystem for any task. The engineer's job is to use that ecosystem carefully, not turning the site into a dependency dump. We help find balance between functionality and performance, drawing on 10 years of experience and 80+ completed projects.

What are common architectural problems in WordPress?

Render-blocking from plugins

Plugin A loads jQuery 3.6, Plugin B loads jQuery 1.12, the theme has its own jQuery Migrate. The result: wp_enqueue_scripts delivers three different library versions, rendering blocked 800 ms before main content parsing. Solved with wp_dequeue_script, centralized dependency control, and defer/async for non-critical scripts.

N+1 queries and their solution

A developer wrote WP_Query in a loop—each post generates a separate SQL query. On a page with 20 posts, that's 21+ database queries. MySQL lags, server heats. Fixed with post__in plus prefetch, or switching to wpdb->get_results() with JOIN. Query Monitor is the first diagnostic tool.

WooCommerce under load

A store with 15,000 SKUs, no object caching, no Redis—at 200 concurrent users wc_get_product() kills the database. WordPress transients don't help: they write to DB, increasing load. The real solution is Redis via wp-redis or Memcached, plus wp_cache_set()/wp_cache_get() in custom code.

How to choose architecture: headless or monolithic?

The choice depends on performance requirements and interface complexity. Headless (REST API / WPGraphQL + Next.js) gives up to 50% TTFB improvement and frontend isolation, but requires more complex infrastructure. Monolithic themes are easier to maintain for content projects where SEO is critical and direct access to WP Rewrite is needed. We help determine the optimal option during audit. Switching to headless improves LCP by 2.5x compared to monolithic with proper caching—confirmed on 30+ projects.

How do we push LCP under 2.5s for production WordPress sites?

Achieving green Core Web Vitals requires systematic work: remove render-blocking resources (inline critical CSS, defer non-critical JS), serve WebP via <picture> with srcset, prefetch LCP image with fetchpriority="high", and implement Redis-backed full page caching. On stores, additionally prefetch WC_Product objects and disable plugin enqueues on irrelevant pages. Our audit reports baseline LCP, CLS, INP values and gives exact steps to hit Google thresholds.

Stack and approaches in WordPress development

Theme development. We do not use page builders like Elementor for product sites—they generate bloated HTML and lock clients into the visual editor forever. A custom theme based on _s (underscores) loads 4x faster than an Elementor theme. Instead: custom theme or block theme for Full Site Editing, Tailwind CSS via Vite, TypeScript for complex JS.

Gutenberg and block development. Since WordPress 5.0, Gutenberg is not just an editor—it's a platform. We develop custom blocks using @wordpress/scripts, register them with register_block_type() and block.json. Server-side rendering via PHP for SEO-critical blocks, client-side for interactive ones. Inner Blocks for composite components.

REST API and headless. WordPress as headless CMS via WP REST API v2 or WPGraphQL. Typical setup: WordPress on subdomain cms.example.com, Next.js frontend on main domain. ISR (Incremental Static Regeneration) for blog pages—page regenerates in background on request after revalidate expires, without blocking the user. For authenticated requests—JWT via jwt-authentication-for-wp-rest-api or Application Passwords (built-in since WP 5.6). More about REST API—Wikipedia.

WooCommerce. Extend via hooks and filters—never modify core files. Custom product types via WC_Product extension. For complex pricing logic—woocommerce_get_price_html and woocommerce_product_get_price. Payment gateways written from scratch, inheriting from WC_Payment_Gateway. Integration with 1C via CommerceML or custom REST endpoint.

Performance. Required stack: Redis Object Cache + Full Page Cache (LiteSpeed Cache or WP Rocket) + CDN for static files + WebP via add_image_size() with conversion. Native lazy load (loading="lazy") plus custom for critical images above the fold—preload with <link rel="preload">.

Case study: WooCommerce store, LCP 9.2s → 1.8s

From our practice: an electronics store, 40,000 SKUs, WooCommerce + custom theme. PageSpeed Insights: LCP 9.2s, CLS 0.41, INP 680ms.

Diagnosis:

• Hero image 3.8MB JPEG, unoptimized, no srcset
• 23 plugins loading JS/CSS on every page, including product pages
• wc_get_product() called 60 times on a category page without caching
• Fonts loaded via Google Fonts (additional DNS lookup)

What we did:

• Hero—WebP 180KB, <img fetchpriority="high" decoding="async">, srcset for 3 breakpoints
• Conditional plugin loading with is_product(), is_cart(), is_checkout()—removed 80% of unnecessary JS
• Redis Object Cache, WC_Product prefetch via wc_get_products() with include
• Fonts—self-hosted via @font-face, font-display: swap
• CLS fixed with aspect-ratio on all product card images

Result: LCP 1.8s, CLS 0.04, INP 140ms. Core Web Vitals—green. Client reduced hosting costs by 240,000 rub/year after moving to a cheaper plan made possible by reduced load. Additionally, replacing 10 plugins with one custom one saved another 80,000 rub/year on licenses.

Work process

1. Audit and analytics. Analyze existing codebase, competitors, technical requirements. For new sites—semantic core, UX prototyping.
2. Architecture. Decide: monolithic or headless. Define Custom Post Types, Custom Fields (ACF or native register_meta()), taxonomies.
3. Development. Local environment: Docker (nginx + php-fpm + MariaDB). Git with pre-commit hooks for PHP CS Fixer and ESLint. Deployment via WP-CLI + SSH or Buddy.works CI/CD.
4. Testing. PHPUnit for custom plugins. Playwright for E2E critical scenarios (add to cart → checkout → confirmation). Lighthouse CI in pipeline—fail if Performance Score < 85.
5. Deploy and support. Staging via WP Stagecoach or manual clone. Monitoring—UptimeRobot + Sentry for PHP errors. Plugin updates—via WP-CLI in test environment first.

What you get as a result

• Fully custom theme or modification of existing one
• Configured object caching (Redis/Memcached) and Full Page Cache
• Optimized media files (WebP, srcset, lazy load)
• Code structure documentation and update instructions
• Training for content managers on Gutenberg blocks
• 30-day uptime guarantee after deployment
• Access to repository with full change history

Timeline benchmarks

Pricing is calculated individually after requirements audit. Contact us for a preliminary estimate.

Common mistakes in WordPress development

• Directly editing theme files—all changes lost on theme update. Use a child theme or fully custom theme.
• update_post_meta() in a loop—each call is a separate UPDATE. For bulk operations use $wpdb->update() or update_metadata_by_mid().
• Disabled WP_DEBUG during development—hidden PHP Notices clutter error log and often indicate real issues.
• Storing media in Git—wp-content/uploads in .gitignore, sync via WP-CLI media import or rsync.
• No limit on WP_Query—posts_per_page => -1 on a page with thousands of posts guarantees a timeout.

Why trust WordPress development to professionals?

We have been on the market for over 10 years, completed 80+ projects, hold certifications from Automattic, and have experience with WooCommerce on high-traffic sites. Our solutions account for all nuances: from plugin compatibility to Core Web Vitals requirements (Google recommendations). After project completion you get a documented, tested, and scalable platform.

For a consultation and evaluation of your project—contact us. We respond within one hour during business hours. Get a free preliminary audit today.