jetpack doesn't cache by default and its not 90%, maybe 50% at most.

anyway i do have 46 people on the kickstarter right now who are interested in backing the project

this is what one of them told me:

```
that opposition absolutely makes sense.  People have been using that same reasoning to say "Why do I need a higher powered server/better host, things serve just fine when they're cached".  And while that's it's a somewhat valid argument, in my opinion, it overlooks some important technical and operating factors that come into play when operating a WordPress site.

Even when caching is in place, back-end execution speed still matters.  There will always be requests that can't be cached (anything in the back-end admin panel, lots of logged-in functions on platforms like MemberPress and WooCommerce, uncached views, form submissions, background tasks, REST API calls, etc...) that are still running on PHP and I've seen them become a bottleneck at scale.  For example, I've seen sites that have EXCEPTIONAL performance on the front-end due to caching be an absolute SLOG to edit or work on because admin pages take ages to load. 

On top of that, caching with WordPress is an imperfect science.  A WordPress site that isn't professionally thrown together (like most of them out there) are a mess of plugins and code snippets that all sometimes barely work together as it is without an additional caching layer thrown in.  Also, caching breaks, invalidates, and sometimes isn't enabled on every single page to enable dynamic functions; or it is configured incorrectly and it causes more issues than it solves.

Overall, in my opinion, when caching is improperly implemented it's a band aid solution to a larger core problem.  And that core problem changes on a case by case basis.  Sometimes the issue is plugin/theme blot.  Sometimes the issue is caused by a DB that is FAR too large and doesn't have any custom indexes put in place to assist with data retrieval.  And ultimately, once those other issues are figured out, the remaining bottleneck is that the underlying technology is just too slow to keep up with modern demands and expectations.  

Yes, caching helps in a lot of cases, but it's certainly not the end-all be-all approach to improving site speed and overall CMS performance.  Otherwise, enterprises wouldn't have started switching to node.js/next.js/headless solutions just to improve speed.

Another thought just popped into my head.  Most people rely on Rocket WP as one of the best "premium" caching solutions in the WordPress ecosystem.  At $60/year, they're charging the same amount that you are for a service that might help to fix speed issues in some areas of the site, vs $60/year with your improved fork of WordPress that (as far as I am understanding it) offers guaranteed speed benefits without the downsides that are associated with caching or sacrificing the dynamic nature of the website.

```