Not clear on what you want us to do. Manually switching posts and pages to TagDiv Composer? What?
See the docs … but I believe it’s just ‘pages’ — such as building a home page, or content pages such as “services and features’ — since ‘most’ publishers use normal WP post features or ACF custom fields to not be ‘tied’ to any one plugin/theme. But your mileage may vary. Probably a ‘conversion’ process to use TDC for posts, but dunno.
Yes. We have a dedicated server, and have been doing our own server management since 1996, and webdev since 3/95, and using WP since Dec 2004. VC caused CPU spikes, more RAM usage, and on two occasions major security vulnerabilities. On our old server (prior last August), we would get bizarro CPU spikes where system would go from 0.7 load to 72.0 !
We were early adopter of the “shim” that Radu came up with, to make Newspaper run for home page blocks without using VC. This evolved into TDC, which was in BETA last year, and we have been using since then. We are using it on numerous sites and refuse to use VC for anything, regardless of its popularity.
Of course, we have high traffic news portals, found in Apple News, Google News, Bing News, (main site syndicated worldwide from 250+ other news sites, top 10 social platforms, etc.), and so we get a lot of traffic, which means a lot of queries.
Besides all of that … the biggest change was moving fully to PHP 5.6.x and no longer using PHP 5.4 for anything in prep for PHP 7.0.x. 5.4 is a dog compared to 5.6, and frankly nobody should be using it anymore for WP, certainly not for VC; and anybody using 5.3 and 5.2 will likely get hacked at this point.
In our case, dedicated server, PHP 5.4, Apache, Linux, any theme with VC => DOOM!
And yes, if you look at the specs posted by TD, they have tested TD against VC for speed — and since it has lower footprint, less code bloat, etc., it’s faster. QED.
My opinion based on our sites and millions of page views. Your mileage may vary.