Directory Size is growing too much!

Hi,

Unless /wp-content/plugins/bdthemes-element-pack/assets/css/bdt-uikit.css is a dynamic generated file, that’s likely not it.

You can see that both files start with 1612730429, meaning that is the last time you purged the cache, however, those are two different files as they have different hashes.

If you save both files and make a diff (check the differences), you will certainly see some difference. The file name, is an sha1 hash of the css code it reads, so even if 1 character changes inside, it’s considered a new file and thus it needs a new name.

FVM merges CSS files together, so likely, one of the merged files inside of it is changing for whatever reason. Maybe you are merging a dynamic generated file, or maybe you edited something and the css file changed.

If your site is maritimecigars.ca (judging from the permalink on google), the difference is coming from elementor.

https://i.imgur.com/YtbmxeJ.png

Basically the css file being merged, is different for every single page, as it keeps changing relative to the post ID. That means, while 99% of the code never changes, at least one file being merged is causing the cache to be different.

You could exclude the file from being merged, or perhaps they should have not generated css files per post… it should be inlined, to prevent this, else you are always going to have at least 1 css file generated by elementor for every post.

Check if there is some option to inline it instead of creating css files on elementor. That way, FVM won’t merge inline styles.

It’s more apparent on FVM because you are merging the files, so every time is different.