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
“This code works” – but it doesn’t! If you’re gonna cache paginated posts, you’ll need to store them chunked: if ( ! $my_paged = absint( get_query_var( ‘paged’ ) ) ) $my_paged = 1; if ( ! $my_query = get_transient( “recent_$paged” ) ) { $my_query = new WP_Query( “cat=3&posts_per_page=5&paged=$my_paged” ); set_transient( “recent_$paged”, $my_query, 60 * 60 … 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
I would’t be affraid of wp_enqueue function itself, not PHP slowdown. But enqueuing more javascript files really matters. But not from the PHP point of view. Each website (even in pure HTML) is getting slower with each other request till it brings all the files. The firs request is HTML file (that’s why we use … Read more
You need to set a unique transient key for each page of posts otherwise each page will output same posts. Here is a example. Focus on get_transient & set_transient functions. <?php $my_posts_query = get_transient( ‘my_unique_transient_key_’ . get_query_var( ‘paged’ ) ); if( false === $my_posts_query ) { $args = array( ‘post_type’ => ‘post’, ‘posts_per_page’ => ’12’, … 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
Unsurprisingly so since you tell browser to cache everything for 1 month by default (ExpiresDefault “access plus 1 month”). You should limit long caching times to static resources and leave pages served by WP out of it. My go to resource for .htaccess configuration is HTML5 Boilerplate. It works with WP nicely and correctly excludes … Read more
These bits of caching are generally considered inadvisable to be messed with. If I remember right you can somewhat control the behavior by query arguments and wrapping related code in wp_suspend_cache_addition() calls. From look through the source it doesn’t seem to be meant to carry custom logic. If you would like similar behavior for your … Read more