@davidedwards sorry for looking into this late.
There are some areas where EE currently does not offer any solution out of the box such as CDN, CSS/js minify, object-cache. In some cases, we reply 3rd party plugins.
I will be happy to give wp-rocket a try but the process of adding anything in EE is bit lengthy. It roughly looks like below:
- Use something on a test site.
- If works on test sites, use on own sites. At this stage document what we need to get it working with EE.
- If works on own sites, use on our client sites. Improve documents based on ongoing work.
- If works on client sites, add that feature in EE. May be marked as experiemental such as current
--wp-redis cache option.
Above can take 1-3 months. But we will likely have a document which at least users can use on their end.
One more thing, I would like to add is - all new features going ahead will be added in EEv4.
And most likely
wp-rocket will be added as an EE package. In fact, in future, the community can build own EE packages and use them.
Please note that by accepting to test
wp-rocket or any plugin/service for that matter, we can’t promise to add it in core. But when EEv4 comes out, even if we decide against working on a 3rd party plugin/service, we would be happy to work with concerned people to help them build an EE package.
I like many things about people behind
wp-rocket but as I haven’t used it once before, I can’t promise anything.
Please let me know if above works.