Excessive front-end asset loading — HUSKY Products Filter loads 27 JS files on pages without any filter widget
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Support notice: Our support team will be on vacation from August 8 to September 3, so response times may be delayed and replies may be irregular.
Hello,
I'm running HUSKY - Products Filter Professional for WooCommerce v3.3.8.1 on a WooCommerce/Dokan marketplace site (elektrotekhnika.com), WordPress 7.1, WooCommerce v11.0.1.x, theme Wolmart.
During a performance audit I found that the plugin enqueues around 27 separate JS files (plus a comparable number of CSS files) on every single page of the site — including pages that don't contain any HUSKY filter widget or shortcode at all, such as the homepage. This is a significant contributor to total page weight and request count.
What I've already checked on my end:
- The plugin is on the latest available version.
- Under Advanced → Extensions, all optional extensions are already disabled except the two default ones I actually use (Featured products, Quick search).
- I reviewed the Advanced → Conditionals tab, but it appears to control filter behavior per page, not asset enqueueing.
My question: is there a supported way to have HUSKY only enqueue its scripts/styles on pages that actually contain a filter (product category/archive pages), rather than loading them globally on every page including posts, the homepage, and static pages that have no filter present? If there's a filter hook or a setting I'm missing, I'd appreciate pointers. If this isn't currently possible, I'd like to flag it as a performance improvement request, since global asset loading is a meaningful load-time cost for stores with a large catalog and heavy homepage traffic.
Happy to share network request exports or a debug log if that helps.
Thank you!