Do WordPress Page Builders Slow Down Your Website?
Disclosure: This post contains affiliate links. If you buy through one of them, we may earn a commission at no extra cost to you. We only recommend tools we’d genuinely suggest to a friend.
Troubleshooting
Yes, most WordPress page builders add extra CSS, JavaScript, and HTML that can slow your site down. How much depends on the builder, how you build your pages, and your hosting. Lightweight options like the block editor or Bricks add little weight. Heavier builders need caching and tuning to stay fast.
- Only 30.0% of Elementor sites pass Core Web Vitals on mobile, compared with 41.5% of block editor sites, according to PageSpeed Matters’ July 2026 field study of about 2.1 million WordPress sites.
- In WP Rocket’s June 2026 lab test of 10 builders (vendor-reported), Gutenberg scored 89/100, Bricks 88, Oxygen 87, and Elementor 81 before any optimization.
- Loading is the weak spot, not responsiveness: every builder in the field study had good INP on 92% to 97% of mobile sites, but Elementor had good LCP on only 44.8%.
- Google’s Lighthouse warns at about 800 DOM nodes and flags an error at about 1,400. The median web page has 594 DOM elements, per the 2024 Web Almanac as cited by CoreWebVitals.io.
- PageSpeed Matters estimates a speed plugin cuts page builder overhead by 30% to 50%, but doesn’t eliminate it.
Do WordPress page builders slow down your website? Usually, yes, at least a little. Sometimes the slowdown is big enough to hurt your rankings and sales. The size of the hit depends on which builder you pick and how you build with it.
Real-world data backs this up. A July 2026 study by PageSpeed Matters looked at about 2.1 million WordPress sites. Only 30% of Elementor sites passed Google’s Core Web Vitals on mobile. Sites on WordPress’s free block editor passed at 41.5%.
This guide shows what the data says about each major builder. You’ll also learn how to check whether your builder is the problem, and how to fix it without starting over.
Do WordPress Page Builders Slow Down Your Site? The Short Answer
Yes, WordPress page builders can slow down your website. They load their own CSS, JavaScript, and extra HTML on top of WordPress. That added code gives browsers more work, which can delay loading and make pages slower to respond. Lightweight builders add far less code than heavy ones.
The gap between builders is measurable. In WP Rocket’s June 2026 test of 10 builders on identical hosting, a Gutenberg page fully loaded in 3.5 seconds. The same page took 5.0 seconds in Elementor and 5.4 seconds in Thrive Architect.
Still, your builder is rarely the only thing slowing your site. Kinsta, a managed WordPress host, says plugin quality matters more than plugin count.
Real-world fixes tell the same story. Consultant Warren Laine-Naida relaunched a client site without Elementor, and load speed improved. He attributes part of the gain to dropping the builder and the rest to image optimization and a lighter theme.
In practice, your page speed depends on several things working together:
- Your builder’s code output: how much CSS, JavaScript, and HTML it adds to each page
- How you build: the number of widgets, animations, and add-on packs on each page
- Your hosting: how fast your server responds before any builder code loads
- Caching, images, and fonts: the optimization layer that sits on top of everything else
Why Page Builders Add Weight to Your Site
A page builder does a lot of work to turn drag-and-drop design into a real web page. That convenience leaves traces in four places.
Common Causes of Page Builder Slowdowns
- Extra CSS and JavaScript loaded on every page
- Bloated HTML and an excessive DOM size
- Add-on packs and unused widgets
- Server-side work: PHP rendering and stored layout data
Extra CSS and JavaScript on Every Page
Every builder ships its own style sheets and scripts. Your visitors’ browsers must download and process these files before the page is fully usable.
The amount can be large. PageSpeed Matters, a speed optimization firm, estimates that a default Elementor install ships roughly 350 to 500KB of JavaScript, plus 250 to 400KB of CSS, before you add any content. The same firm reports that a well-configured Elementor site can now get under 200KB of JavaScript, which is why the settings covered later in this guide matter.
Some builders also load files where they aren’t needed. WP Rocket gives a common example: you add a contact form to one page, but the builder loads the form scripts on every blog post.
Bloated HTML and Excessive DOM Size
The DOM (Document Object Model) is the tree of elements a browser builds from your page’s HTML. Builders often wrap each design element in several layers of containers.
WP Rocket illustrates this with a simple hero section. One builder might create 15 elements for it, while another creates 60 nested elements for the same result.
CoreWebVitals.io also notes that since Lighthouse 13 (October 2025), this check is called “Optimize DOM size.” It now also looks at how much rendering work the page causes.
A big DOM matters for more than load time. Google’s web.dev explains that it makes layout and styling work more expensive, which can slow how fast a page responds to clicks and taps. In a 2023 test by developer Rhys of Dwi’n Rhys, a combined Beaver Builder page had about 80 more DOM elements than the same page in the block editor.
Add-On Packs and Unused Widgets
Many builder users install third-party widget packs for extra sliders, counters, and effects. Each pack brings its own CSS and JavaScript.
WP Rocket’s review lists add-ons that increase page weight as a drawback of Elementor. It also notes that heavy animations can hurt performance.
This is called asset bloat: visitors download code the page never uses. A page with only a button and an image might still load popup styles, carousel scripts, and extra icon files.
Server-Side Work: PHP Rendering and Layout Data
Not all the weight shows up in the browser. Your server also has to build each page before sending it.
Builders store layout settings in the WordPress database and assemble pages from them on request. PageSpeed Matters notes that builders also pile up autosaves, post revisions, and stored layout data over time.
This server work mostly affects uncached pages. Page caching sidesteps much of it by serving a saved copy instead of rebuilding the page for every visitor.
A builder’s weight also grows with use. Online Media Masters points out that Elementor can look lightweight in speed tests right after activation. The extra CSS, JavaScript, and fonts appear once you start building pages with it.
How Page Builders Affect Core Web Vitals
Core Web Vitals are three metrics Google uses to measure real visitor experience. They cover loading, responsiveness, and visual stability. According to Google’s web.dev, a page passes only when it meets the “good” target for all three at the 75th percentile. That means at least 3 out of 4 visits need a good experience.
Passing isn’t easy for anyone. SEO Kreativ cites the 2025 Web Almanac, which found only about 48% of mobile websites pass all three metrics.
| Metric | What It Measures | Good | Needs Improvement | Poor | How Page Builders Can Affect It |
|---|---|---|---|---|---|
| LCP (Largest Contentful Paint) | Loading speed of the main content | 2.5s or less | 2.5s to 4s | Over 4s | Extra CSS and JavaScript can delay the hero image or headline |
| INP (Interaction to Next Paint) | How fast the page responds to clicks, taps, and key presses | 200ms or less | 200ms to 500ms | Over 500ms | Heavy scripts and a large DOM slow down each response |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | 0.1 or less | 0.1 to 0.25 | Over 0.25 | Late-loading sliders, widgets, and fonts can push content around |
Thresholds: Google web.dev, measured at the 75th percentile of real visits. Summary of bands via Yasser Soliman (July 2026).
Largest Contentful Paint (LCP)
LCP measures how long the biggest visible element takes to appear. On most pages, that’s a hero image or a large headline.
LCP is where page builders struggle most. The PageSpeed Matters field study found Elementor sites have a good LCP only 44.8% of the time. The study concludes that page builders tend to fail on loading, not responsiveness.
Interaction to Next Paint (INP), and Why FID No Longer Counts
INP measures how quickly your page reacts when someone clicks, taps, or types. It replaced First Input Delay (FID) on March 12, 2024.
Page builders can hurt INP through heavy JavaScript and deeply nested layouts. As covered earlier, a bigger DOM means more work every time the page updates.
Cumulative Layout Shift (CLS)
CLS measures how much content jumps around as the page loads. You’ve felt it when a button moves just as you try to tap it.
Kinsta notes that layout shift warnings in speed tests can come from page builders or themes. Common causes include sliders, popups, and web fonts that load late and nudge content out of place.
Core Web Vitals are one ranking input among many. Unlighthouse notes that relevance and content quality remain stronger search signals. Speed still matters, though, especially for keeping visitors on the page.
Which Page Builders Are Fastest? What the Data Shows
Two very different 2026 data sources help answer this question: a controlled lab test and a large real-world field study.
Lab Test Results: One Page, 10 Builders
WP Rocket’s June 2026 test rebuilt the same page in 10 builders. Each page used the same hosting, theme, images, and plugins. The team tested on a simulated iPhone 14 using GTmetrix.
Gutenberg scored highest at 89/100, followed closely by Bricks at 88 and Oxygen at 87. Breakdance scored 84, Elementor 81, and Thrive Architect came last at 78. These scores were measured before any speed optimization.
Real-World Field Data: 2.1 Million WordPress Sites
Lab tests show what’s possible. Field data shows what real visitors actually experience. The PageSpeed Matters study (July 2026) matched builder detection data to Google’s Chrome UX Report. It covered about 2.1 million WordPress sites, measured on mobile in May 2026.
The results line up with the lab test in one big way: builders that stay close to native WordPress passed most often. The WordPress Site Editor passed at 43.8%, Beaver Builder at 42.7%, and the block editor at 41.5%. Divi passed at 34.5%, WPBakery at 32.7%, and Elementor at 30.0%.
The study also found a surprise. Every builder had good INP on 92% to 97% of mobile sites. Loading (LCP) is the real weak spot, not responsiveness. Elementor sites, for example, had good INP 92.6% of the time but good LCP only 44.8% of the time.
The gap shrinks on desktop but doesn’t close. In the same study, block editor sites passed Core Web Vitals on desktop at 50.2%, compared with 40.3% for Elementor, 38.8% for WPBakery, and 31.7% for Divi.
Bricks, Oxygen, and Breakdance don’t appear in the field data. The study only included builders with at least 20,000 mobile sites in Google’s dataset.
A smaller third dataset points the same way. As summarized by WP Boosters, Kyle Van Deusen of The Admin Bar recorded Lighthouse scores for more than 150 agency-built websites. Elementor and Divi sites had the lowest medians, at 66 and 62, while GenerateBlocks sites had the highest, at 90.
| Page Builder | Lab Score /100 (WP Rocket) | Lab LCP (WP Rocket) | Mobile CWV Pass Rate (PageSpeed Matters) | Mobile Good LCP (PageSpeed Matters) | Starting Price (USD) |
|---|---|---|---|---|---|
| Gutenberg (Block Editor) | 89 | 2.2s | 41.5% | 65.0% | Free |
| Bricks Builder | 88 | 2.3s | Not in study | Not in study | $79/year; $599 lifetime (vendor site) |
| Oxygen Builder | 87 | 2.4s | Not in study | Not in study | From $199* |
| Beaver Builder | 86 | 2.5s | 42.7% | 62.9% | Free Lite; paid from $99/year* |
| Breakdance | 84 | 2.7s | Not in study | Not in study | From $99/year* |
| Elementor | 81 | 3.1s | 30.0% | 44.8% | Free; Pro from $59/year* |
| WPBakery | 80 | 2.7s | 32.7% | 48.9% | From $69 one-time* |
| Divi | Not tested | Not tested | 34.5% | 52.6% | Not listed in either source |
Sources: WP Rocket lab test, June 2026 (vendor-reported). PageSpeed Matters CrUX field study, mobile, May 2026 data. Pricing last verified: September 23, 2026, for Bricks, from its official pricing page. *Prices marked with an asterisk are as listed by WP Rocket in June 2026; confirm them on each vendor’s official pricing page before buying.
WP Rocket’s 10-builder test didn’t include Divi, and its separate Divi review dates from 2024, before Divi 5. PageSpeed Matters notes that Divi 5 was a full rewrite, so we’ve left the older lab numbers out.
Why Lab Scores and Real-User Data Don’t Always Agree
A lab test isolates the builder on one clean page. Field data mixes in everything else real sites do, including their hosting, images, and plugins.
That means the field numbers show a pattern, not proof that the builder caused it. An Elementor site might also run on budget hosting or use huge hero images. PageSpeed Matters itself says the LCP problem is fixable with image cleanup and caching.
PageSpeed Matters also sells speed optimization services. Still, all three sources point the same direction. The closer a builder stays to native WordPress output, the easier it is to keep fast.
If you’re starting a new site and want a visual builder with lean code output, Bricks scored near the top of WP Rocket’s lab test. Read our Bricks Builder review, or see its current plans below.
See Bricks Builder’s Current Plans →
Gutenberg vs. Page Builders: Is the Block Editor Really Faster?
The short answer: Gutenberg is usually faster than the heavy drag-and-drop builders, but it’s not automatically the fastest option. The data shows a clear edge with a few exceptions.
What the Data Says
In WP Rocket’s lab test, the Gutenberg page fully loaded in 3.5 seconds. The same Elementor page took 5.0 seconds. In the PageSpeed Matters field data, block editor sites passed Core Web Vitals at 41.5%, compared with 30.0% for Elementor.
The field data has a twist, though. Beaver Builder sites passed slightly more often, at 42.7%. Sites using the WordPress Site Editor, the full-site version of the block system, did best at 43.8%. PageSpeed Matters’ speed guide takes a firm stance here. It calls Gutenberg with a block theme the fastest path, and says Elementor and Divi can be made acceptable but won’t match native blocks on mobile LCP.
The Trade-Off: Speed vs. Design Freedom
Speed isn’t the only factor. Hostragons notes that Gutenberg’s cleaner HTML suits performance-focused sites. But it may be less convenient for complex visual layouts than Elementor.
WP Rocket’s review lists similar drawbacks for Gutenberg. It has fewer advanced design features and less visual flexibility, and you may need extra block plugins to fill the gaps.
The Middle Path: Block Plugins
If Gutenberg feels too limited, block plugins can add design tools without a full page builder. Web developer Peyton Gregory points to GeneratePress with GenerateBlocks and Kadence Blocks as lighter options that work with native WordPress. See our GeneratePress review and Kadence review for details.
How to Tell If Your Page Builder Is the Real Problem
Easy: Free Tools Only
Before you tune or replace your builder, confirm it’s actually what’s slowing you down. Many sites blame the builder when the real culprit is hosting, images, or another plugin.
Here’s a six-step check you can run with free tools:
- Compare real-user data with lab data in PageSpeed Insights
- Look for DOM size and unused code warnings
- Measure unused builder code with Chrome DevTools Coverage
- Check your server response time (TTFB)
- Compare a builder page with a plain post
- Profile server-side load with Query Monitor
Compare Real-User Data With Lab Data
Run your page through PageSpeed Insights. The top section shows field data from real Chrome visitors. The lower section is a lab test on a simulated device.
Start with the field data, since that’s what Google evaluates. As Yasser Soliman’s 2026 guide for marketers points out, the big performance score is a weighted lab estimate, not your pass/fail verdict. Low-traffic sites may not have field data yet. In that case, rely on the lab results and Google Search Console’s Core Web Vitals report.
Look for DOM Size and Unused Code Warnings
Scroll to the diagnostics in the same report. Look for “Optimize DOM size” (formerly “Avoid an excessive DOM size”) and “Reduce unused CSS” or “Reduce unused JavaScript.”
Then check the file paths listed under each warning. Builder files usually load from your plugin folder, such as /wp-content/plugins/elementor/. If builder files dominate these warnings, that’s a strong sign the builder is a real factor.
Measure Unused Builder Code With DevTools Coverage
Chrome’s Coverage panel shows how much of each CSS and JavaScript file a page actually uses. Open DevTools, open the Command Menu, and run “Show Coverage.” Then reload the page.
You’ll see used and unused bytes for every file. Large builder files that are mostly unused point to asset bloat you can often trim.
Check Your Server Response Time (TTFB)
Time to First Byte (TTFB) measures how long your server takes to start sending the page. According to Google’s web.dev, a good TTFB is 0.8 seconds or less, and anything over 1.8 seconds is poor.
A poor TTFB usually points to hosting or missing page caching. Fix that first. Until your server responds quickly, you can’t fairly judge how much weight the builder adds. Our guide to WordPress hosting requirements explains what server resources a builder-based site needs.
Compare a Builder Page With a Plain Post
Find a regular blog post written in the block editor, then test it alongside a builder-made page. Both share the same hosting, theme, and plugins, so the difference mostly reflects the builder.
If both pages are slow, look beyond the builder. If only the builder page struggles, you’ve found your main suspect. For a cleaner test, rebuild one simple page both ways on a staging site.
Profile Server-Side Load With Query Monitor
The free Query Monitor plugin breaks down database queries and page generation time by plugin and theme. It helps you spot whether the builder, or another plugin entirely, is slowing uncached pages. Run it on staging when you can, and deactivate it when you’re done.
If these checks point at your builder, you usually don’t need a rebuild. The fixes below solve most builder slowdowns.
How to Speed Up a Page Builder Site Without Switching
Rebuilding is rarely the first fix. The PageSpeed Matters field study found that Elementor’s weak spot is loading, which it describes as a fixable problem. Image cleanup, fewer widgets, and page caching all improve LCP directly.
Quick Fix
- Turn on your builder’s built-in performance settings (test on staging first)
- Remove unused add-on packs, widgets, and animations
- Add page caching and delay non-critical JavaScript
- Compress and resize your hero image, and host fonts locally
- Upgrade hosting or add a CDN if your TTFB is slow
Turn On Your Builder’s Built-In Performance Settings
Most major builders now include speed settings, but many aren’t switched on by default for older sites. Elementor’s official help docs say its performance features live in two places: the Performance tab and the Features tab. They include Element Caching, which serves a saved copy of an element instead of rebuilding it on every load.
These Elementor settings are worth reviewing:
- Flexbox Containers: PageSpeed Matters recommends switching every section from the old section-and-column layout to containers.
- Improved Asset Loading and Improved CSS Loading: According to Crocoblock, which sells Elementor add-ons, these stop unused scripts from loading and cut the default CSS on each page.
- Inline Font Icons: Elementor’s help docs say this renders icons as inline SVG, so the page doesn’t load the full Font Awesome and eicons libraries and their CSS and font files.
- Optimized Image Loading: According to the same docs, this adds a high fetch priority to the LCP image and lazy-loads images below the fold.
Elementor’s Optimized DOM Output, which removes extra wrapper elements, no longer needs to be switched on. Elementor says these DOM improvements became part of Elementor Core starting with version 3.19, so you get them by keeping the plugin updated. If you’re on an older version, update on a staging site first, because the markup changes can break custom CSS that targets the removed wrappers.
Using Bricks, Divi, or another builder? Check its official documentation for similar asset-loading options.
Trim Add-Ons, Widgets, and Animations
Every add-on pack and animation brings its own files. Remove widget packs you only use for one or two elements. PageSpeed Matters also recommends disabling widgets you don’t use at all.
Add Caching and Asset Optimization
A caching and optimization plugin handles the fixes a builder can’t do on its own. The main jobs are page caching, minifying files, and delaying JavaScript that isn’t needed right away.
Results vary by feature. In a September 2025 test that Kinsta published when announcing its WP Rocket partnership, delaying JavaScript execution cut load time on a page builder site by 33.33%. Minification had little impact, because the builder’s files were already minified.
WP Rocket’s own test reports a bigger jump: a WPBakery page went from 80/100 to 100/100, with LCP falling from 2.7 seconds to 461 milliseconds. That’s vendor-reported data from a single page. PageSpeed Matters, which sells optimization services rather than a plugin, estimates that a speed plugin cuts builder overhead by 30% to 50% but doesn’t eliminate it.
Popular options include WP Rocket, LiteSpeed Cache, and Perfmatters. LiteSpeed Cache is free, but it needs a LiteSpeed server for page caching; you can download LiteSpeed Cache free from WordPress.org. Perfmatters is an asset manager rather than a cache, and its official pricing page lists plans from $24.95 per year for one site.
If you want a paid plugin that handles caching and JavaScript delay in one place, read our WP Rocket review or check its current pricing.
Check WP Rocket’s Current Pricing →
Fix Hosting, Images, and Fonts
On most builder pages, the LCP element is a hero image. CriticalWP recommends making sure it’s properly sized and not lazy-loaded. It notes that Elementor background images can’t use the browser’s eager-loading setting, so compressing the file matters even more.
For fonts, consider hosting Google Fonts locally or using system fonts, as Peyton Gregory suggests. And if Step 4 showed a slow TTFB, better hosting or a CDN may help more than any builder tweak. Our WordPress hosting cost breakdown shows what an upgrade typically costs.
| Fix | Metric It Mainly Helps | Effort | Cost |
|---|---|---|---|
| Turn on builder performance settings | LCP, INP | Low to medium (test on staging) | Free |
| Remove unused add-ons and widgets | LCP | Low | Free |
| Page caching | TTFB, LCP | Low | Free to paid, depending on host and plugin |
| Delay non-critical JavaScript | LCP, INP | Medium (can break features) | Free to paid plugin |
| Compress and resize the hero image | LCP | Low | Free to paid plugin |
| Host fonts locally or use system fonts | LCP, CLS | Low to medium | Free |
| Upgrade hosting or add a CDN | TTFB, LCP | Medium | Paid, varies by provider |
When Should You Switch Page Builders?
Switching usually makes sense when your field data still fails after optimization, and builder files still top your unused-code warnings. It’s also worth considering if you’re already planning a redesign. On the other hand, if your site passes Core Web Vitals, a builder change adds risk for little speed gain.
Page Builder Trade-Offs: Honest Pros and Cons
Speed is only one part of the decision. Here’s how the trade-offs look, based on the sources cited throughout this guide:
Pros
- Visual, drag-and-drop editing that non-developers can use
- Faster page design without custom code
- Built-in tools such as forms and popups can replace separate plugins
- Strong ecosystems for WooCommerce and client sites
Cons
- Extra CSS, JavaScript, and HTML on every page
- Lower Core Web Vitals pass rates for the heaviest builders in 2026 field data
- Add-on packs and animations can quickly increase page weight
- Switching away later can take real work
On the third pro, Beaver Builder, a builder vendor, argues that one well-coded builder can replace several other plugins. Warren Laine-Naida makes the same point about reducing a site’s overall weight. If you’re weighing two popular builders against each other, our Elementor vs. Divi comparison covers features and pricing side by side.
Lock-In Risk and the Partial Migration Approach
Leaving a builder isn’t always clean. WP Rocket lists shortcode dependency as a drawback of WPBakery. With shortcode-based builders, deactivating the plugin can leave raw shortcodes scattered across your pages. Newer builders store layouts differently, but you’ll still need to rebuild each page’s design.
You don’t have to move everything at once. Horde Marketing suggests migrating your highest-value templates first, such as your homepage and main service pages. Lower-priority pages can stay in the builder for now. Your most-visited pages improve first, and you avoid the risk of a full rebuild.
Bottom Line: Should You Worry About Page Builder Speed?
Do WordPress page builders slow down your website? Usually, but the slowdown is rarely beyond repair. Builders closest to native WordPress stay fast most easily, and most of the damage lands on loading speed, which is the most fixable metric.
Here’s our recommendation, based on where you’re starting:
Don’t switch yet. Run the six-step check, turn on your builder’s performance settings, and add caching. Consider migrating only if your field data still fails after that.
Begin with the block editor and a lightweight block theme, or a lean builder like Bricks.
A heavier builder is still a reasonable choice. Just plan for optimization from day one, not after launch.
Skip the switch. A migration adds cost and risk for little speed gain.
Your Builder Sets the Starting Point
Your hosting, images, and caching decide how fast your site actually feels to visitors. If you want one plugin that handles caching, file optimization, and JavaScript delay, WP Rocket is a common choice. We haven’t personally tested it on our own sites, so compare it with free options like LiteSpeed Cache before you buy.
Page Builder Speed FAQ
Does Elementor slow down my website?
Does Divi slow down WordPress?
What is the fastest WordPress page builder?
Is Gutenberg faster than Elementor?
Do page builders hurt SEO?
Can a caching plugin fix a slow page builder site?
How many plugins is too many for WordPress speed?
References
-
PageSpeed Matters (Matt Suffoletto)
Elementor Is the Slowest Major WordPress Page Builder, Passing on 30% of Sites.
-
PageSpeed Matters
WordPress Page Builder Speed: Elementor, Divi, Gutenberg.
-
WP Rocket (Marine Larmier)
10 Best WordPress Page Builders Performance Comparison in 2026.
-
Kinsta
How to Speed Up Your WordPress Site.
-
Google web.dev
Optimize Time to First Byte.
-
Google web.dev
Web Vitals.
-
Chrome for Developers
Avoid an Excessive DOM Size.
WP Essentials Hub — Your Complete WordPress Essentials Hub
I’m Shamim Sarker, the founder and lead reviewer at WP Essentials Hub — a dedicated WordPress toolkit review site where I help website owners, bloggers, and developers find the right tools to build, grow, and secure their WordPress sites.
With 8+ years of hands-on WordPress experience, I’ve personally built, tested, and troubleshot hundreds of websites. I cover themes, page builders, plugins, hosting, domains, coupons, and deals — all tested on live WordPress sites with my own money. No paid placements. No vendor influence. Just real testing and real results.
