Try to remove all the revisions from the edited page in admin panel. You can find the revisions in right sidebar. And you can disable the revisions by using config.php by putting this define(‘WP_POST_REVISIONS’, false);. And also you can delete from database using SQL query DELETE FROM wp_posts WHERE post_type = “revision”; Hope it will … Read more
No, there isn’t. WordPress does not provide page caching mechanisms, and has no APIs for it. There is no generic way to say example.com/page is now stale and needs recreating. Nor is there any generic way to pre-generate every page short of visiting them all. Every plugin uses a different solution with different APIs and … Read more
You can use the second parameter passed to the wp_feed_cache_transient_lifetime filter which, in the context of fetch_feed(), is the URL of the feed: add_filter( ‘wp_feed_cache_transient_lifetime’, function ( $time, $url ) { if ( $url === ‘https://example.com/rss’ ) { $time = MONTH_IN_SECONDS; } return $time; }, 10, 2 );
It is prolly injected in your files. Look at the plugin files, search for eval or base64.
As long as you use WP API ($wpdb) to perform queries, they will be cached by caching plugins (well, by those that have such functionality). If you need to cache data that is more compelx to generate rather than just retrieve look into Transients API.
It would be a bad idea to combine common CDN served files that the majority of web users already have cached for obvious reasons…
It looks like your site is doing a lot of processing when displaying a page. have you tried adding a caching mechanism? you can give plugin a try: http://wordpress.org/extend/plugins/w3-total-cache/
Either way you’re going to need to store the data you retrieve from an external database, in your WordPress database, if you don’t want to continually run the same query on your external database each time the page is accessed. You can either store the data in your WordPress database using Custom Fields (post meta) … Read more
I looked at the source code of the site and found this: <meta name=”robots” content=”noodp,noydir,noarchive,nosnippet”/> Apparently noarchive tells Google to not cache the page. Check out Google Webmaster Tools documentation/guidelines for “Meta tags” for more info on what each value does. PS: If you are unaware, nosnippet should also be removed as it “prevents a … Read more
If WordPress is using APC it will use it for its object cache, and since APC is per machine, not per cluster, the two will diverge, giving you problems if you’re trying to run 1 site off of two machines. In that scenario you will want 1 memcached deamon running, and configure your 2 servers … Read more