WPBakery Setup: Performance, Custom Elements, Migration

A client comes with a premium theme already purchased, which includes WPBakery Page Builder. The requirement is to configure the builder so that content managers can independently edit pages without breaking the layout. Without proper setup, the plugin loads hundreds of kilobytes of CSS and JS on every page, and custom elements have to be written from scratch. We solve these problems comprehensively. Request a WPBakery audit — it takes one day.

Problems We Solve

Performance. By default, WPBakery enqueues about 130 KB of CSS and 200 KB of JS on all pages, even if the builder is not used. For a site with 10,000+ visits per day, this adds 0.5s to TTFB. Asset optimization is the first step toward Core Web Vitals.

Custom Elements. The standard widget set does not cover business logic. For example, you need a testimonial carousel with filtering or a booking form. We have to write custom elements using vc_map and shortcodes.

Access Control. When 5+ content managers work on the site, it's important to restrict who can use raw HTML or change global styles. Role Manager handles this, but fine-tuning requires code.

Migration Trap. WPBakery stores content as shortcodes in post_content. When the plugin is deactivated, pages become unreadable text. Migration to Gutenberg or Elementor is manual work that we perform without data loss.

How We Configured WPBakery for an Online Store: A Case Study from Our Practice

In our practice, we had a case: configure WPBakery for a WordPress + WooCommerce store in three days. Needed custom product cards, fast frontend, and editable by three managers.

Stack: latest stable WordPress, PHP 8.x, WPBakery, Redis for object cache.

Steps:

1. Dequeue unnecessary assets using wp_dequeue_style only on pages with shortcodes.
2. Created three custom elements: "Product of the Day" (extended block), "Category Filter", and "Testimonial Block with Stars". Each element was described via vc_map, with icons and fields.
3. Configured Role Manager: managers can only use specific elements, administrators have full access.
4. Wrote custom CSS for grid layout, applied in Custom CSS in plugin settings.
5. Conducted load test: page load time dropped from 3.2s to 1.1s, saving the client about 30,000 rubles per year on hosting. LCP improved from 4.2s to 1.8s, and CLS decreased by 60%.

Why Migration from WPBakery to Gutenberg Is Problematic?

WPBakery encodes content in shortcodes, while Gutenberg uses blocks with JSON comments. No automatic converter preserves all styles. We apply a hybrid approach: first export content via do_shortcode to clean HTML, then manually split into Gutenberg blocks. For large projects (100+ pages), this takes at least two weeks, but the result is predictable.

How to Optimize WPBakery Assets?

The main issue is that WPBakery enqueues its styles and scripts on all pages, even if the builder is not used. Solution: use wp_dequeue_style and wp_dequeue_script to disable assets on pages without shortcodes. Additionally, enable caching via Redis or CDN. This reduces TTFB by 30–50%.

Process of Work

1. Analysis. Review current WPBakery configuration, installed add-ons, page types. Map shortcode usage.
2. Design. Design custom elements, plan grids and styles. Approve layouts with client.
3. Implementation. Write element code, configure Role Manager, optimize assets. Integrate with themes and plugins.
4. Testing. Check on different devices, measure Core Web Vitals, test access rights.
5. Deployment and Handover. Deploy to production, train editors, deliver documentation.

What's Included

• Full audit of current WPBakery configuration
• Frontend asset optimization (CSS/JS)
• Development of up to 5 custom elements
• Role Manager setup
• Content conversion during migration (up to 50 pages)
• Documentation on editor usage
• One-hour consultation for editors

Estimated Timeline

From 2 to 10 working days depending on page count and custom element complexity. Cost is calculated individually after audit.

Comparison Table: Editing Modes

Backend Editor loads 5–10 times faster than Frontend Editor, critical for frequent editing.

Comparison Table: Migration Approaches

Typical Mistakes and Checklist

• [ ] Assets not dequeued on pages without shortcodes
• [ ] Role Manager not configured — all have access to raw HTML
• [ ] Outdated add-ons used, slowing down the site
• [ ] Content not backed up before migration

function vc_map_custom_product_of_day() {
    vc_map(array(
        'name' => 'Товар дня',
        'base' => 'product_of_day',
        'category' => 'Кастомные',
        'params' => array(
            array(
                'type' => 'textfield',
                'heading' => 'ID товара',
                'param_name' => 'product_id',
            ),
        ),
    ));
}
add_action('vc_before_init', 'vc_map_custom_product_of_day');

Our team has extensive experience with WPBakery and has completed over 50 projects on this builder. We guarantee that after WPBakery setup, your site will run stably, and editors will comfortably manage content. Contact us for a consultation — we will assess your project in one day.

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.