There are kind of two levels to browsing caching: Browser is provided with explicit information when page expires via response headers or 304 Not Modified response. Browser kind of assumes that page was loaded very recently and is still good for a while. Respectively there are two possible things going wrong: Your server is replying … Read more
The short answer is: it doesn’t That doesn’t mean it can’t be made persistent, and it doesn’t mean it doesn’t improve performance. Performance Gains Despite No Persistence Lets say we fetch 5 posts, and on each post we retrieve various post meta. You might think that each call to get_post_meta results in an additional DB … Read more
I think HTML mirror is the way to go here. There is no point keeping dynamic site that doesn’t need to be. And leaving it unmaintained is not really possible on auto-pilot – even if updates are automatic there is no guarantee some plugin won’t get just dropped by developer. Alternatively you can build multi-design … Read more
Caching full pages is not going to do you any good for a situation like you described. Users will update things and expect to see their updates right away — meaning you spend more server time invalidating cached pages. The database server is likely to be your biggest bottleneck in just about any webapp. Two … Read more
If the generation of the graphic presentation requires a lot of CPU time or memory, then yes, you could cache your graphic presentation (HTML I guess, right?). Perhaps in the database/memory, as a transient. Caching post meta data (that you use to generate the graphic) is not necessary, because WP already handles this. If you … Read more
A great deal of this will depend on your server configuration, but: Will WP Super Cache cache the css.php output? Extremely unlikely. If your file simply generates CSS from a few variables, then no. If however it bootstraps and loads WordPress, then it ‘might’ cache some things, but I doubt it will work as you … Read more
Had you verified that there is no advanced-cache.php already there from another plugin (or as leftover of one)? You can try to copy this file manually from W3TC folder: wp-content\plugins\w3-total-cache\wp-content\
get_bloginfo() is not cached and calling it over and over would harm your performance just like creating many calls to the database yourself. a simple solution which doesn’t evolve any caching in to minimize the database and function calls by defining a an array with all the info you need and save that as an … Read more
The point of caching is to increase performance, not specifically to reduce server load, but there is pretty obviously a relationship– perhaps not exactly the one(s) you expect. This is by no means a canonical answer but here are several things I can think of: Some kinds of caching increases memory usage. Caching that uses … Read more
4.1 is coming from your WordPress version. Also you should not append ver= to the src manually but use the fourth parameter of wp_enqueue_style.