First off, I read every review and also searched for some other locations online for the same. I then bought 6 codes. I've been in IT Management & Consulting for over 4 decades (20 years in Atlanta). One of several areas of my skillset was that I have been fortunate to research well enough to successfully recognize potential in a tech related product or service. Fortune corporations looked for that to help manage their risk aversion when striving to make serious decisions of direction to remain among the first in the competitive IT industry.

One of the key reasons that peaked my interest (beyond the idea of its proposed functionality) was the small amount of mediocre scoring. A large amount of the reviews were a love or hate experience. And the 1 star (1 taco) amount might have been around 20-25% (overall here and with other Internet sources). But, over 50% have complete appreciation and happiness of 5 stars (5 tacos). So, that's a high probability of good potential. There are other considerations too, of course.

So, with that said, here's my experience and opinion of BerqWP and how I'll be handling it.

1. I was using Litespeed & their CDN. It was slowly getting slower in the low to mid 90% of PSI metrics. BerqWP achieved 99-100% on all PSI metrics of 3 of my sites the first day.

2. It took me several months to tweak and configure Litespeed settings because a lot of experts had their own suggestions. However, 1 of my sites was a food recipe site which is more difficult to configure to keep all of its specialized functions to still work dynamically (not static html, for example). With BerqWP, I started with its "Aggressive" mode, select some of the options, and, after a few attempts, achieved 99 to 100% PSI metrics. Also, to my amazement, all of the recipe functions still worked! That included the recipe resizing function. Also, the specialized grids for recipes worked and refreshed correctly when a new recipe was added to a filtered area.

3. Two of the biggest issues in reviews were that it worked and then didn't or that it didn't work to begin with. And the other was the lack of response for support. Well, I experienced it too; however, here's what happened. The 2nd day, all the sites plummeted in the performance metric to mid 70 to mid 80%. So, after checking a few things, dropping the mode down lower, rebuilding the cache, etc., I went to submit a support ticket. The leading statement on the support page conveyed that support was currently high and it would be 1-2 days for response. So, I submitted my ticket and received a confirmation email. Now, in the meantime, what about my production sites? Well, I instituted my backup plan, and returned my critical site (the food recipe site) back to LiteSpeed. Then, the first day after I experienced the issue and submitted my support ticket, a plugin newer version was released. So, I installed it, and it fixed everything. Although I noticed the update removed my original settings so I reapplied them. Still worked perfectly. There were 2 more updated versions administered within the next 24 hours as well. Each one was logged for several specific fixes such as not dropping the settings and for something else I wasn't having an issue with.

So, I understand the difficulties of growing a developing product or service. While nearly all will have some bad experiences with some clients, this one is apparent to me. I suspect that the developer's time was devoted to switch focus to repairing some common issues being initially reported. This, in turn, would resolve a bulk of the support tickets that I'm certain were piling up. So, when mine was resolved, for example, I went in and made a noted reply on my support ticket, and then promptly closed it.

I am sensing this to be a future great product and service. I heartily recommend it.

I am saving about $180 a year from my LiteSpeed license. Plus, I now don't have a limitation on a low number of domains or RAM that LiteSpeed licensing imposes. And, it took several hours for Litespeed to rebuild my 180 post recipe site. Plus, it's settings are far simpler to set that actually work! Also, my PSI metrics (and other measuring sites) give outstanding results. Also, as a user, I could feel my sites were much peppier than before. The CDN speeds were showing not as good as LiteSpeed CDN but still fine. So, I recommend it but, I have disabled the auto-upgrade option. I recommend you keep a downloaded version that works for you in case a newer version has an issue for your scenario. Also, as another reviewer recommended, read through what cache options are compatible or not. In my case, I disabled LiteSpeed (didn't have to uninstall it) and kept Redis Object Cache active (compatible).

Hope this helps.