Great questions! The current setup doesn’t include advanced optimizations like code splitting, tree shaking, or minification out of the box More Information. You’re right—the demo theme does have some unused JS/CSS, mostly for showcasing features. We recommend customizing and optimizing the build process based on your needs. If you're looking to improve performance, integrating plugins like TerserPlugin for minification or SplitChunksPlugin for code splitting in Webpack would be a good start.

You're right to be cautious. The docs are a bit light on those details. Webpack and Gulp can handle code splitting, tree shaking, and minifying, but you’ll need to configure them properly with the right plugins/loaders. The demo theme probably includes extra assets for showcase purposes, but it’s definitely a good idea to clean that up for production (Read More). Let me know if you want help setting that up.

Hi Devin Schumacher,

The numerous JS/CSS files included in the Metronic demo are primarily for illustrative purposes. In a real-world application, you typically include only the files necessary for your specific use case. To enhance performance, you can remove the CSS/JS plugins that are not required.

For minifying the output of CSS/JS files, you can use Gulp with the --prod flag, as an example:

gulp --prod

Keenthemes wrote in the documentation that they did it that way on purpose. You can use webpack or gulp in the “tools” folder to delete the plugins etc that you don’t need in the respective config files and then recompile them.
And the code will be minified too. On gulp compile file:

if (args.prod !== false) {
 // force disable debug for production
 build.config.debug = false;
 // force assets minification for production
 build.config.compile.jsMinify = true;
 build.config.compile.cssMinify = true;
}