Cache Footer Improvement?

From what I see, one css url is for the header and another is for the footer… so it’s correct. Each plugin decides where they want to enqueue their css files, either on the head or footer.

If all your plugins enqueue in the header, then there will be only one file in the header and none in the footer, so this happens because your plugins need to do this, this way.

As for the js on the footer, it merges by groups and it has to consider dependencies and order of scripts. For example, if you have 100 scripts and one is on the ignore list, you will end up with 3 files. One with merged files, the ignored file and another set of merged files.

You may have libraries that are for mobile only too, so it’s unavoidable to have separate files for those.

There are also limits on the amount of files you can merge. For example, Internet Explorer 9 and earlier, cannot read past 4095 selectors in CSS…

I’m always looking forward for improvements, so if you’re sure that those should be merged and this is a bug, kindly post the list of files that have been merged inside each file (it’s on the status page logs).

Else, you’re already probably having the least amount of files possible.

Raul,

Thanks for the quick response. Your explanation makes sense.

We are very happy with the results compared to what we had before. Thanks for a great plugin!