

Real three-run mobile PageSpeed comparison on the same public Elementor template page: median score 70 to 84, FCP 3.0s to 1.2s, and LCP 6.0s to 4.2s. Lighthouse lab values can vary by site and run.
Make Elementor faster without breaking the design.
ElementsBoost finds page-specific Elementor CSS, JavaScript, fonts, icons, sliders, and addon assets that may be adding unnecessary weight. It helps you review the evidence, preview supported performance changes, verify the public result, and reverse eligible changes without editing code.
ElementsBoost complements your existing cache plugin. It focuses on reducing selected Elementor and WordPress frontend work before the finished page is cached or delivered by a CDN.
Buraq is the in-editor mechanism behind the ElementsBoost workflow. It scans the current public page, explains what it found, highlights matching elements with X-Ray, and verifies supported actions against fresh page output before showing them as completed.
Buraq does not mark a supported action successful just because a switch was enabled. When a rendered result can be checked, it rescans the public page and reports what it can confirm. Supported setting and content changes retain scoped recovery paths so you can test, verify, and reverse eligible changes without guessing.
ElementsBoost does not replace a full-page cache or CDN. It complements cache plugins by reducing selected Elementor and WordPress frontend work before the result is cached.
Free includes the Buraq workflow, global controls, profiling, and practical page fixes. Pro adds deeper per-page optimization and before-and-after testing.
See ElementsBoost Pro features and pricing
When Self-host Google Fonts is enabled, ElementsBoost downloads CSS and font files from fonts.googleapis.com and fonts.gstatic.com, stores them locally, and serves the local files later.
When an administrator enables Diagnostics, the plugin sends one diagnostic report immediately and then weekly to https://elementsboost.com/wp-json/elementsboost-telemetry/v1/collect. The payload is restricted to WordPress, Elementor, PHP and plugin versions; theme name; locale and multisite status; active-plugin, Elementor-page, disabled-widget, scan, issue, image, conflict and dequeue-rule counts; the installation date and age; the on/off state of documented ElementsBoost controls; and a persistent random installation UUID. The UUID is generated locally, is not derived from the site URL, and is removed when the plugin is uninstalled. The JSON payload does not include the site URL, page URLs, page content, plugin names, WordPress usernames, or email addresses. Diagnostics is off by default.
The dashboard can retrieve aggregated benchmarks from https://elementsboost.com/wp-json/elementsboost-telemetry/v1/benchmarks. The request sends no site or user data and is cached for six hours.
When compatibility alerts are enabled, the plugin downloads a curated feed from https://elementsboost.com/wp-json/elementsboost-intel/v1/intelligence-feed and refreshes the local copy weekly. The fixed feed URL has no site or user data in its query string or request body. Disabling compatibility alerts unschedules feed requests and suppresses plugin-activation compatibility notices.
When an authorized user runs an on-demand test in Free or a benchmark in Pro, the selected public page URL is sent to Google PageSpeed Insights. Free stores the latest result locally. Pro adds history, comparisons, scheduled monitoring, and support for a site-owner API key. Google quotas and policies apply.