Hello @giaco91dena
Thank you for reaching out and I am happy to assist you with this.
I am not sure what the question is really ??
If the question is why W3 Total Cache creates minified files, the answer is simple, Minify is enabled.
I’ve made some more tests, and as I can see the load time for these files varies depending on the location of the testing.
What you can try is to use the Disk Caching method for Minified files instead of Memcached and see the test results. Minified files are not big and should not use more than 100 kb of disk space in your case.
W3 Total Cache minifies the files when minify is enabled. Depending on the number of CSS/JS files and their location, a number of minified files is also created.
You can also try Manual minify, and manually add files to minify in proper order. This will create a single file for both JS and CSS.
The testing shows that those minified files take some time to load, and this is indeed interesting taking into account the size of those files, so the only possible problem is the Memcached server’s ability to serve those files fast.
What would be interesting to test in your case is the CDN for the static assets, Stackpath for example, and see if the load time of those files is faster since the files would be served from the CDN.
Once again, disable the Minify and make the test. Check what Google Page speed is suggesting. Try the Disk caching method instead of the Memcached.
Let me know if this helps!
Thanks!
