The biggest criticism of WpDiscuz – huge CSS and JS files

  • While I love this plugin, the sheer number of CSS and JS code that gets bundled with the plugin has become unreasonable. As developers, your team needs to make it so that the plugin only loads required CSS and JS code for the features that are enabled – not bundling everything together, even when the features are disabled. It does not matter how minified and “optimized” the code is. Why load all that extra code that’s not needed?

    For example, I only have the most basic WpDiscuz setup with nothing other than the comments section. And yet, no matter what I select in the configuration, your plugin loads everything, thus impacting site rendering performance. I keep finding myself trimming your JS and CSS files to bare minimum each time a major plugin update comes out. That’s just not sustainable.

    You are only making the Internet slower. Please load CSS and JS features based on what configuration the end user chooses. This should be easy to do. Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support gVectors Support

    (@gvectorssupport)

    We may suggest you enable the following two options:

    1. Combine JS and CSS Files to Optimize Page Loading Speed
    2. Minify JS and CSS Files to Optimize Page Loading Speed

    It does not matter how minified and “optimized” the code is.

    @megaz

    @gvectorssupport please read the original post carefully, as it contains important information. This request makes absolute sense and can be easily facilitated by structuring the loading of code based on the featured enabled.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘The biggest criticism of WpDiscuz – huge CSS and JS files’ is closed to new replies.