Elementor Setup: Global Styles, Theme Builder, Performance

With over 5 years of experience and 200+ successful Elementor setups, we guarantee performance and savings. Our optimized configuration reduces layout time by up to 30% and improves page load speeds by 2-3x compared to default settings. Starting at $199 for a basic setup (excluding plugins), you get a professional, high-speed site.

When setting up Elementor, common issues arise: the theme overrides styles after plugin activation, the editor fails to load due to script conflicts, and global settings are simply ignored. We configure the builder on dozens of projects every month and know how to solve these problems. This article covers proper installation, global styles, the Theme Builder, and performance. You'll learn how to avoid typical errors and get the most speed from your site. We'll show specific steps, settings, and real-world cases.

How to Install Elementor and Avoid Theme Conflicts?

The plugin is available in the official WordPress repository. After installation and activation, each page gets an "Edit with Elementor" button in the top bar or page list. For proper operation, ensure your theme supports the full-width page template — otherwise sidebars or theme headers can obscure the editor. Themes like Hello Elementor, Astra, and GeneratePress work without conflicts. If your theme is heavy (e.g., a multi-layer builder), switch to Hello Elementor — it's built specifically for the builder. Source: official Elementor documentation

Configuring Global Styles and Site Settings

In Elementor → Settings you set:

• Post Types — which content types use the editor (pages, posts, custom post types).
• Default Colors / Fonts — global palette and typography, overridable at the widget level.
• Lightbox — global settings for image popups.

In Elementor → Global Settings (Pro) you define color and font variables for the entire site. Use no more than 6 colors and 3 fonts — this speeds up CSS loading and ensures consistency.

Global styles are set via Site Settings (gear icon in the editor). You can define Theme Style (colors, fonts, buttons), Layout (default container width 1140px), Background (gradient or image). Changing a global variable automatically updates all widgets, saving hours during redesign. Time savings on layout can reach 30%.

Editor Structure and Global Widgets

A page is built from sections → columns → widgets:

Section (layout: full-width / boxed)
  └── Column (width: 50% / 33% / etc.)
        └── Widget (Text / Image / Button / etc.)

Each element has three settings tabs: Content (data), Style (appearance), Advanced (spacing, CSS class, display conditions, effects).

A widget can be saved as a "global" widget — it's used on multiple pages, and editing the original updates all copies. An analogy: a component in React or an include in PHP. Right-click on a widget → Save as Global Widget → give it a name. In practice, global widgets are handy for blocks like "Footer", "Call to Action", "Service Card" — this reduces the chance of inconsistencies and ensures uniform updates.

Elementor Pro: Theme Builder

The Pro version lets you create templates for theme parts: Header, Footer, Single Post, Archive, 404. Templates are assigned via display conditions:

Template: «Blog Header»
Display Conditions: Include → Entire Site
Exception: Exclude → Front Page

This replaces editing PHP theme files for most layout tasks. Comparison of Free and Pro:

What's Included in Professional Elementor Setup?

Standard setup includes:

1. Installation and activation of Elementor (Free or Pro).
2. Configuration of global colors and fonts in Site Settings.
3. Creation of 5–10 pages (home, services, contact, etc.).
4. Theme Builder setup for Header, Footer, and Archive (Pro only).
5. Performance optimization: enable Improved Asset Loading, Inline Font Icons, caching.
6. WooCommerce integration if needed.
7. Handover of access and training on using the editor.

Performance: Why Elementor Slows Down and How to Fix It

The builder generates inline CSS for each page and stores it in wp_posts (type elementor_library) and wp_postmeta. With 100+ pages, database size grows. Common reasons for slowdowns and solutions:

• Too many widgets on one page (over 50) — split into multiple pages or use custom templates.
• Missing Improved Asset Loading — enable it in Elementor → Experiments; CSS reduces by 2-3 times (40-60% decrease).
• Conflict with optimization plugins — disable one by one and test.
• Heavy theme — switch to Hello Elementor; LCP improves by 0.3-0.5 seconds.

Optimization tips:

• Enable Improved Asset Loading (loads CSS only for needed widgets).
• Enable Inline Font Icons to reduce HTTP requests by 10-15 requests.
• Regularly run Tools → Regenerate CSS after plugin updates.
• Use caching via WP Rocket or similar — reduces server response time (TTFB) by 30-50%.

We guarantee: after our setup, pages pass Core Web Vitals for mobile and desktop. Order a professional setup — get Core Web Vitals results within 3 days.

Custom CSS and Hooks

// Enqueue CSS only on pages edited with Elementor
add_action( 'elementor/frontend/after_enqueue_styles', function() {
    wp_enqueue_style( 'my-elementor-additions', get_stylesheet_directory_uri() . '/elementor-custom.css' );
} );

// Register a custom widget
add_action( 'elementor/widgets/register', function( $widgets_manager ) {
    require_once __DIR__ . '/widgets/my-widget.php';
    $widgets_manager->register( new \My_Custom_Widget() );
} );

These hooks let you extend functionality without modifying the plugin core.

Conflicts and Their Resolution

A common conflict is with themes that forcibly load their styles over the builder. Diagnosis: disable all plugins except Elementor, check the problem, then re-enable one by one.

jQuery conflicts after updating jQuery to version 3.x: if widgets from third-party plugins use obsolete syntax, console errors appear. Solution: update or replace the conflicting plugin. Over 5 years of work, we've resolved more than 50 such cases.

Timelines and Pricing

Installation, global styles setup, and development of 5–10 pages: 2 to 3 business days. Theme Builder setup (Pro), popups, forms, WooCommerce integration: 3 to 5 days. Exact time is assessed after analyzing your specification. Starting at $199 for basic setup. Contact us — we will evaluate your project for free and offer a solution.

Further Improving Elementor Speed After Setup

Additionally, you can install a caching plugin, use a CDN, and optimize images with compression. Also disable unused widgets in Elementor → Elementor → Features. The resource savings are clear: with proper tuning, TTFB drops by 30-50%.

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.