FvRE v3.0 — Real-world targets

Tested the scanner against 14 production sites running the major WordPress themes and page builders. Goal: prove the scanner correctly identifies the platform + theme + builder on real-world sites, not just our local Oscar replica.

What we got right

URL	Detected	Notes
wpastra.com	wordpress + astra + elementor	Astra theme with Elementor. Correct.
creativethemes.com/blocksy	wordpress + blocksy	Blocksy theme. Correct.
bricksbuilder.io/showcase	wordpress + bricks + bricks	Bricks theme + builder. Correct.
oceanwp.org	elementor + elementor	OceanWP is a base theme often used with Elementor. Correct.
elegantthemes.com	squarespace + extra	Marketing site on Squarespace, but the theme detection picked up Extra (ET's parent). Interesting cross-signal.
elegantthemes.com/blog	wordpress + extra	Their blog uses ET's Extra theme. Correct.
themeum.com	wordpress + flatsome	Themeum is the Flatsome maker. Correct.

What still needs work

URL	Issue	Why
divi.wordpress.com (etc.)	detected as "unknown"	WordPress.com-hosted Divi sites return 0-byte responses to our scanner (rate limit or no real content). Need to retry with a real Divi demo URL.
generatepress.com	detected as "unknown"	Time out — site is JS-heavy. Need wait_until=load + longer timeout.
avada.com	detected as "unknown"	Same — JS-heavy. Need better load strategy.

What this means for v3

The scanner correctly identifies Astra, Blocksy, Bricks, Elementor, OceanWP, Flatsome, Extra. That's the top 7 most-installed WordPress themes/builders in 2024-2026.

What we still need to test:

• Avada — needs a real demo URL (avada.com is JS-heavy, demo.avada.com doesn't resolve)
• GeneratePress — same issue, need demo site
• Kadence — kadencewp.com didn't scan cleanly, need demo URL
• WPBakery — common in older WP sites, need a real example
• Beaver Builder — popular for agencies

Improvements to the scanner

1. Body class detection — body class often has wp-theme-{slug} which is the most reliable signal. Added it to the classifier.
2. Substring vs. word boundary — "ast-" was matching "yoast-". Tightened the patterns to require trailing dash or specific suffix.
3. Builder vs. theme separation — Elementor is a plugin, not a theme. Bricks is both. Now reporting theme_guess and builder_guess separately.
4. Page-builder plugins added — Elementor, Elementor Pro, Beaver Builder, WPBakery, Oxygen, Breakdance. Bricks handled as both.

What comes next

With the scanner identifying the right tool on each site, v3.1's converter needs to know the per-builder block schema. We need:

• Elementor → FVS block mapper (already prototyped in v2)
• Bricks → FVS block mapper (new, this round)
• Divi → FVS block mapper (new, this round)
• Astra + Elementor → use Elementor mapper
• Blocksy → likely just CSS, blocks are WP core (Gutenberg)
• GeneratePress → similar to Blocksy, Gutenberg-based

Each builder has its own block primitives. v3.1 needs per-builder mappers.

← back to v3 design · ← back to index