Update: So I decided in the end to stick with Hyper Cache, which is pretty okay, enable caching to true in the wp-config file and since I’m not expecting hundreds of visitors to interact with the social aspect of the site, it’s a small group, the images seemed to be the issue with the site’s speed and the other caching plugins were breaking buddypress features.
So I’m using Imsanity and Ewww Image Optimize plugins to control the maximum size of the images being uploaded (they get re-sized by the plugin) and to optimize the existing images I had in the library. This has helped my site’s speed a whole lot especially with the Site Activity Feed widget on the front-page.
I’m still looking into caching, looking into mem-caching but not sure if it’s necessary at this point in time for a site that if we’re lucky, has a maximum of 100 members. Hope this topic helps someone.
Hmm I’ll try disabling the Page Cache and then putting DB cache back on to see if it’s the combination. It didn’t really act up until I installed the DB cache but the site seems to be getting slow from what looks like the images being uploaded by the users or a post versus the images from the site itself or code.
I’ll also check out w3total cache as well – will post with results. Thanks!
Thanks! It wasn’t the Hyper Cache but it looks like my database caching plugin (DB Cache Reloaded Fix) was the issue, the moment I disabled that, the “join” button was gone on his account and the text editor re-appeared for him to post on his group. I don’t understand why that would happen though for this one member due to database caching? Does this mean that buddypress doesn’t behave well with db caching plugins in general or I just need to adjust my settings somehow?
