WordPress verdict · build Pain point

Script dependency resolver for WordPress minification tools

Built for WordPress admins using WP-Optimize with form plugins.

“Replies: 0 Recapcha issue, does not adapt to zoomed screen. That means wpforms_settings is not defined error happens even on the raw, unmerged plugin file. This…”

The receipts — real demand

“Replies: 0 Recapcha issue, does not adapt to zoomed screen. That means wpforms_settings is not defined error happens even on the raw, unmerged plugin file. This means WP-Optimize’s JS merging setting is breaking WPForms’ own validation script. WPForms normally outputs a small inline <script> block that defines wpforms_settings (a config object) before its main JS file loads and reads it. When WP-Optimize merges/reord…”
WordPress · view original →

Full dossier

Unlock the full dossier — free

Every corroborating quote, the source receipts, and the community echo. One email, no payment.

6.0 / 10 · demand score
Pain 8
Willingness to pay 4
Feasibility 7
Specificity 9
Audience 6
Competition 8

Why this is a gap

Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.

The market

WordPress admins using minification (WP-Optimize) alongside form plugins (WPForms). No search volume; a single unresolved support thread with 0 replies suggests a narrow technical edge case, not a product market.

Competition & the opening

Already owned an incumbent owns the exact job Moat 2/10 · no real moat Market 4/10 · small niche
Category giants · 8/10 vs Autoptimize (WordPress plugin with JS/CSS dependency-aware minification)WP Rocket (premium caching/minification plugin with script load-order management)W3 Total Cache (free plugin with minification and dependency exclusions)Asset CleanUp Pro (WordPress plugin for script/style dependency management and removal)LiteSpeed Cache (free plugin with JS defer/combine respecting wp_enqueue dependencies)webpack / Vite (build-tool layer that resolves JS module dependencies before WordPress ever sees them)

Autoptimize, WP Rocket, W3 Total Cache, Asset CleanUp Pro, LiteSpeed Cache, and webpack/Vite are all mature (8/10 competition). The gap: existing plugins exclude scripts from minification but do not automatically resolve dependency order for excluded scripts (e.g., wpforms_settings dependency chain). Vite/webpack solve this at build time, not at WordPress enqueue runtime.

What's hard to build

WordPress wp_enqueue_script dependency resolution is shallow (only direct parent declared, not transitive closure). Building a dependency graph at minification time requires static analysis of JS code or manual declarations. Integrating into WP-Optimize's internal minification pipeline without breaking updates is risky.

Why now

Free minification plugins (Autoptimize, W3TC) ignore WordPress dependency registry; Elementor/WPForms validation scripts break silently when merged without dependency awareness.

How you'd monetize

$19/year WordPress plugin (one-time purchase, no recurring churn risk)