In reply to GeekPress.

Hello GeekPress,

I can certainly appreciate what you're saying about W3TC support. It's terrible. The question is ...is that a selling point? That in return for money, WP Rocket offers support (said differently: that WP Rocket's support is cheaper than W3TC's)?

Re: LazyLoad:
But I can use the Rocket Lazy Load (or another lazy load plugin) with any caching engine I want to...

Re: DNS Prefetching:
But I can use the DNS Prefetch plugin with any caching engine I want to (or implement DNS prefetching with very simple coding, the exact verbiage and placement of which is a single Google search away)...

Re: Google Fonts Optimization:
I am unaware of any data indicating that the minification of Google Fonts improves the load time of a website in a manner that is either consciously or subconsciously perceptible. I am, however, certainly open to reviewing data in your possession which proves the assumptions predicated by the word "optimization" as you've applied it to the minifcation of Google Fonts.

Re: Support
Addressed above.

Re: Preload Cache
Wp Rocket does this for all pages linked to directly from the homepage, correct? But you're solving a non-problem. For busy sites, most-visited-pages have their cache revalidated/rebuilt almost instantly and this is accomplished with any caching plugin. For not-so-busy sites, the site administrator can click-around for 15 seconds and revalidate/rebuild the cache for whatever pages he or she deems important. This, of course, sidesteps WP Rocket's apparent assumption that all sites' most visited, most important pages are linked to via the homepage. (As somewhat of an aside, W3TC has a similar feature: Performance --> Page Cache --> Cache Preload).

Believe it or not, I really am on your side. But my criticisms -- and especially my suggestions about implementing something truly innovative (e.g. Inlining and Defering CSS on a page-by-page basis) -- still stand.

Honestly, best of luck,
AJ