[ad_1]
I’ve seen plenty of folks get good PageInsights scores using Divi and getting some good first-load perf. Just have a few questions;
1. Is Divi fundamentally a CPU hog? On a single cold request my server CPU can sometimes spike to around 50%
2. If 1 is true, this just a feature of server-side rendering? i.e Building a response for every request? (hence CPU usage)
3. I’ve tried quite a few plugins to remove the burden of render blocking resources, but just can’t seem to get it sorted.
Hosted on DigitalOcean, 2vCPU, 1GB RAM.
[Waterfall of a typical request]) [PageInsights scores]) [Metrics breakdown]) [Render blocking resources that I can’t seem to eliminate]) [Critical render path chain that seems a bit too beefy])Once I enable page caching it’s fast as heck as expected, it’s just these first page loads that are killing me.
[ad_2]
1. Most builder themes are, Divi is as well.
2. It’s just a feature of most themes that are multi-purpose built. So much code to traverse, so much code to discard, because it’s not fit for your purpose.
3. Using more plugins is just adding kindle to the fire, as each plugin is just another ressource drain (some larger, som smaller).
Ressource wise, you’re loading a lot of ressources that might not be necessary. The most “critical” one i can gauge, might be a off-site load of a Google font that you’d have more success of loading locally, instead of from their repository, but it’s just a guess as i can’t see the full path of the query.
Just as a precaution, have you run a scan with Wordfence just to ensure you don’t also have malware running?
I haven’t used Divi in a long time, but I have clients who use Elementor and WPBakery and none of them use anything like 50% – and that’s on a server with 20 other sites. A single page request might hit 35% server cpu, but just for half a second. If you’re seeing constant high cpu usage that’s not due to your theme.