Raul P.

Hi there,

You should hire a developer if you are trying to optimize a site and are not sure how the plugin works. You have to manually configure it, it’s not just install and call it a day.

Because optimization needs to minify your css and js files, it creates minified copies of the originals in the cache directory, which you are seeing with the long names.

However, if you purge the FVM cache… You just deleted those very cache files, so now you need to clear your page caching too, else your content is still pointing to the old deleted css and js temporary files, until the page cache expires.

The plugin doesn’t break anything. A plugin can be enabled or disabled.

If you are seeing the layout broken with 404 errors to FVM related css or js files… That simply means you are seeing a page cache version that points to delete files. It would be the same if you delete an image.

The page caching can be either from some other plugin, but more often from your hosting configuration or even cloudflare (if you use APO) for example.

When page cache is enabled on your hosting, page caching saves a snapshot of your page and your further requests never reach WordPress. If meanwhile you delete the cache on FVM without clearing page cache after, those files would return 404 not found.

You need to ensure page caching is cleared properly after purging FVM and that has nothing to do with FVM itself.

Contact your hosting and ask them how to purge the cache. Some hosting providers for example, require you to log to their control panel to clear it. Others put a plugin on your site to allow you to do it.

If you modify your content, including using minification plugins, you won’t see any changes until you clear the page cache.

If you clear too many times… sometimes hosting services rate limit your request and ignore your cache purge request.

If FVM cannot purge your page caching and if you need to manually clear page caching from somewhere, you first need to try FVM in a staging version of your site that doesn’t use page caching.

If the plugin is properly configured (without page caching), and if you disable the option to purge cache immediately on FVM for example… It will work even with your type of hosting or after reenabling page cache.

You cannot do development with page cache enabled… Speed optimization is development work.

Else find better hosting. Bluehost, GoDaddy, wpengine, kinsta, are all good options.

FVM does not have scripts so the file doesn’t belong to FVM. As you can see from the file path, it’s a cached file. What happened there, is that you already have that file on your site and FVM caught it and minified it.

FVM doesn’t check for malware.
If you already have malware on the site, FVM will treat it as a normal javascript file.

I suggest you look at the file position on the HTML code, disable fvm and check what file is showing there with that content. That file must be already there with a different name.

The file indeed looks like malware, so try to deactivate fvm first (else it will keep populating the cache directory), manually delete the cache directory, purge all caches anywhere else and run a scan with wordfence for example.

wordfence doesn’t detect everything, so you may need to hire someone to remove that malware.

Assets will be generated whenever a page has different css or js file names, it doesn’t care if it’s search or some other page.

If you have a lot of files being created on search pages, check what is on the list.
Likely, one or more files is different on every search you are doing.

You should exclude the dynamic file from minification, or ideally, fix your code so that the enqueued file url never changes, or only changes when needed. If a file name changes every time, FVM sees a new file every time.

You can minimize the cache directory by disabling merging, which will then minify each file individually. But then, if 1 file is changing, that file is always still going to be regenerated unless you either fix the url, or exclude it.

The styles are not loading, because, you have purged the css/js files but not your server page cache, or some other page cache plugin.

The pages are pointing to minified css files that you have deleted, either on purpose or not, it doesn’t matter.

Another possibility, is that the server has no file permissions to allow saving those files.

All you need to do is to disable the plugin and then clear the page cache.
Look for any other cache plugins you may have installed and purge everything.
Then ask your hosting to purge their own cache (check their control panel).

If you are using cloudflare as well, depending on the features you use (such as APO) it may be cached there as well.

Some hosting services have very persistent caching, so speed optimization that requires minification of css and js files, it’s best done by a professional (or get a better server provider, ie cloudways for example).

FVM has an option to preserve css and js files instead of deleting them immediately when you clear the cache. It will keep the files for some time, to prevent accidents where your page is still cached but you already deleted the optimized files (the filenames change every time you purge, that is why you cannot load them as your page is still pointing to the old ones in it’s cache).

FVM does not do page caching.
For your type of cache, make sure the “Purge Minified CSS/JS files instantly” is not active.

But first you need to configure it properly, which may prove difficult as your page cache is apparently not updating when needed. Basically, every time you change something on the site, the cache should be purged.

If your hosting cannot sort it out, follow the instructions I provided here.
Emergency fix is to deactivate the plugin, followed by page cache purging.

If you used some cache plugin and disabled it after, you may still be having cache rules on your .htaccess file.

Check the site files (control panel, plugin, sftp, etc) and delete the wp-content/cache directory manually, if it exists.

It works with WP 5.8 but an update will come in the next coming days, once I have some time to add a few new features I have planned. Thanks

The validation is just a guideline, it’s telling you that it doesn’t recognize the fvm-script-delay as a javascript type, because it’s not part of the specification. It’s telling you, that there is a error so the scripts won’t run.

But creating the error and not being part of the specification is intended. It’s required to bypass javascript execution there, and then there will be a proper script at the bottom, that runs these types later. If it was valid, the script would not be delayed.

This is similar to what cloudflare does, as well as any other plugin that delays javascript. Being invalid, doesn’t mean it does not work. Only that it’s unexpected, according to the specification on HTML.

https://community.cloudflare.com/t/rocketloader-causing-w3c-errors/17991/3

If you want to delay the scripts, you have to make them invalid so the browser will ignore them. Then later, you manually execute them on interaction or some other rule.

it’s not a setting, it’s probably how yoast rewrites that part. FVM captures the html page on template load, so if yoast does that later, in the header for example, it won’t work. I will look into it soon.