WPIntell

Source evidence

Dequeue/Disable Plugin Hook (Beaver Builder)

WP Accessibility · support · 2025-04-09T17:01:00+00:00

complaintsentiment
mediumseverity
0.87relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 31 rows with source links

19.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

25 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
etaproducto unresolved
Hi! My name is Peter and I’m a WordPress Developer. So the the theme we’re running is Beaver Builder (w/ UABB, BBPP and Beaver Themer). And in the Builder context (as is pretty typical) there’s a lot going on in JS; Shadow-DOM stuff, re-rendering, Ajax calls etc. We’ve noticed some performance issues using the Beaver Builder page editor (all OS/all modern Browsers)… And one of the culprits was WP Accessibility, running in the Builder context as it would on the front-end (which might be fine/desirable in some cases, but we’d like it not too) and bottle-necking Ajax calls. I’ve searched high and low and can’t find a filter, action or hook that would let me disable the plugin in this context. Should I simply dequeue the JS whenever the Builder is active? Not wanting to create more problems of course. Thanks! The page I need help with: [ log in to see the link] I would think that dequeuing the JS would be the most reasonable thing to do; that’s pretty much what any filter I’d add would control, so it doesn’t seem worthwhile to add an additional one. I can’t think of any reason that conditionally dequeuing JS would cause any problems.

Comments

1 shown
Joe Dolson 2025-04-09T20:10:00+00:00

I would think that dequeuing the JS would be the most reasonable thing to do; that’s pretty much what any filter I’d add would control, so it doesn’t seem worthwhile to add an additional one. I can’t think of any reason that conditionally dequeuing JS would cause any problems.