No.
The new version has WooCommerce support now and is improved again under the hood.
Minifying requires page parsing and Minifying is not 100% fault tolerant, it should be done by the developers that provide .min.* files. Most of them do, so it is not realy necessary to add on top, i think.
Thank you very much for the clarification.
Hello
many cache plugin have a preload function which warm up the page cache. Usually they depend on sitemap.xml . Do you think a similar function would benefit your plugin?
Thank you for your question.
No, preloading fills the cache with pages that might never be used.
Plus on global events (like plugin activation/deactivation) the whole cache must be flushed and refilled again. Makes no sense.
Only the first request to a page will be of normal speed, every following request will be delivered from cache in “no time”.
See, most of the other plugins have a large overhead, thus there response time is slower than mega cache.
w3T cache for example, is >50 MB in size, MC is 500 KB! That is x100 !
we do have atec-minify plugin in atec-Plugins now.
This is independant of mega-cache.
