How To Speed Up Your Slow Divi Website And Pass Core Web Vitals In 22 Steps: 2023 Straightforward Guide With Advanced Tips

Slow divi website

Divi is slower than most themes because it adds more CSS/JavaScript (you can check this in your coverage report). But, it doesn’t mean you can’t get good scores and pass core web vitals.

Two easy ways to speed up Divi are removing unused CSS and delaying JavaScript which many optimization plugins support. However, you’ll need to add a few Divi-specific exclusions (step 4 + 5) to prevent these from breaking your site. Disabling Gutenberg, lazy rendering Divi sections, and enabling (some) Divi’s performance settings should also help improve your core web vitals.

It’s still amazing how many people complain about their slow Divi site when they use cheap shared hosting, CDNs with small networks and no full page caching, and a bad cache/image optimization plugin. There’s a lot of misinformation, so I’ll also shed light on tools I recommend.

Good luck and lmk if you have questions.


1. Test Divi’s Performance Settings

Divi’s performance settings are found under Divi → Theme Options → Performance.

Many Facebook Group members reported better results when disabling all settings and letting their cache plugin handle everything (which I generally agree with because most cache plugins have better compatibility, while the Divi Theme Users Groups is loaded with posts about errors).

Bottom line – learn what each one does and test it.

Since most settings are for CSS/JS, I would check 3 things: your website (for broken elements), Chrome Dev Tools coverage tab (to monitor CSS/JS file sizes), and the Console tab (for errors).

These are general recommendations, test them yourself!

  • Dynamic Module Framework: On – only loads used modules/features.
  • Dynamic CSS: On – same concept as previous setting for Divi’s Stylesheet.
  • Dynamic Icons: On – again, same concept as previous setting for font subsets.
  • Load Dynamic Stylesheet In-line: Off – loads dynamic CSS non render-blocking, but I’ve seen many reports of it breaking sites. That said, I would leave it disabled.
  • Critical CSS: Off – most cache plugins do this and you don’t want duplicate features (SG Optimizer still doesn’t to my knowledge, in which case, enable it).
  • Dynamic JavaScript Libraries: On – similar to first 3 settings for JS functions.
  • Disable WordPress Emojis: Off – most cache plugins do this, or enable it here.
  • Defer Gutenberg Block CSS: Off – since you’re using Divi instead of Gutenberg, you should disable Gutenberg completely (in step #2) instead of just deferring it.
  • Improve Google Fonts Loading: Off – caches Google Fonts and loads them in-line, but most cache plugins do this already and you’re better off viewing step #3
  • Defer jQuery And jQuery Migrate: Off – seems useless since Divi says “if a third-party plugin registers jQuery as a dependency, it will be moved back to the head to avoid conflict.” And chances are, you’re using several jQuery-dependent plugins.
  • Enqueue jQuery Compatibility Script: Off – leave off if you’re not using the previous setting. You can test both and check your results and Console report, then enable this which loads a compatibility script that attempts to solve issues.
  • Defer Additional Third Party Scripts: Off – you’re better off deferring JavaScript in your cache plugin which gives you more control by excluding problematic files.

Divi performance settings


2. Disable Gutenberg

Since you’re using Divi Builder, you can disable Gutenberg which loads a CSS file across your site (/wp-includes/css/dist/block-library/style.min.css). You can find in this your source code.

Gutenberg wp block library css 1

The Disable Gutenberg plugin and Perfmatters script manager both do this. If this breaks your site, you can control whether Gutenberg loads on pages, posts, specific post IDs, user roles, etc.

Disable gutenberg plugin


3. Host Fonts Locally, Convert To woff2, And Preload Them

Some plugins (like FlyingPress, Perfmatters, LiteSpeed Cache) host fonts locally and preload them, but you’ll still need to convert them to woff2 and remove any font families/weights you don’t use. OMGF also lets you host fonts locally, disable fonts you don’t use, and preload them.

Step 1: Disable Google Fonts in Divi’s general settings.

Disable google fonts divi

Step 2: Download only the font families/weights you use. WP Johnny has a good video on this.

Step 3: Convert fonts to smaller woff2 files using a free converter.

Step 4: Upload the fonts to your site. Divi only supports .ttf and .otf (which are larger files), so you’ll need to add them to CSS (like in the video) or use a plugin like Use Any Font. You can also search/replace fonts in stylesheets, then Better Search Replace to change them in the database.

Step 5: Preload fonts if they load above the fold. Grab your font files (i.e. in your GTmetrix Waterfall chart) and preload them using your cache plugin, Perfmatters, or Pre* Party Resource Hints. If you see the option to use crossorigin, you should be using these when preloading fonts.

Preload local fonts

Step 6: Set your font-display property (I usually recommend “swap”) to fix ensure text remains visible during webfont load in PageSpeed. Some cache plugins add this automatically (check their documentation). You can also change this in your font’s CSS by searching for the font with String Locator, or install a plugin that does this for you. This can also fix font-related CLS issues.


4. Remove Unused CSS While Excluding “/et-cache/”

Most cache plugins remove unused CSS, but you’ll want to exclude Divi’s dynamic stylesheets. If there’s a stylesheet behavior setting, remove is fastest but requires the most work between checking for errors and excluding problematic files. Otherwise, delay is the next fastest setting.


Remove unused css divi

I recommend using FlyingPress, LiteSpeed Cache, or Perfmatters to remove unused CSS. Like the Perfmatters’ documentation and Vikas explain, WP Rocket loads used CSS inline which is better for “scores” but slower for users. However, the other 3 plugins load it in a separate file which is slightly worse for scores, but faster for users. WP Rocket values scores over visitors :/

Wp rocket used css
Why other plugins do a better job at removing unused CSS than WP Rocket


5. Delay JavaScript With Divi Exclusions

Most cache plugins can also “delay all JavaScript,” but it also breaks Divi sites.

Just like the previous step, we’ll exclude specific Divi files from being delayed. Again, Perfmatters has good documentation and depends whether you use animations or not. Excluding “” can also prevent flash of unstyled content to improve CLS.



Divi With Animations

var DIVI

Which would look like this:

Delay javascript divi

WP Rocket lists additional Divi exclusions when you’re using sticky elements, video backgrounds, as well as avoiding having to double click your mobile menu to open it.

If your optimization plugin can’t delay JavaScript, use Flying Scripts. However, this requires manually adding JS files/keywords to delay (as opposed to delaying all then excluding any problematic files). Which means you’ll need to open your “third-party code” and “remove unused JavaScript” reports in PSI and manually delay files while testing for broken elements.


6. Lazy Render Divi Sections

Lazy render is supported by FlyingPress and LiteSpeed Cache. It’s like lazy loading images only for any element on the page. It’s usually done for Divi sections when they load below the fold.

View your site, then right click any Divi section you want to lazy render. Inspect it in Chrome Dev Tools, right click the code, copy the CSS selector, and paste it in FlyingPress or LiteSpeed Cache.

Copy divi section css selector

Lazy render divi section


7. Lazy Load Background Images

Divi’s background images aren’t lazy loaded by default.

This is because they’re loaded from CSS which plugins don’t lazy load, resulting in defer offscreen images errors in PageSpeed Insights and making your initial page load much larger.

The easiest method is to use an optimization plugin that includes a “lazy-bg” helper class. FlyingPress (lazy-bg) and Perfmatters (perfmatters-lazy-css-bg class) have helper classes you can add to the background image’s CSS class (under the Advanced tab), which looks like this:

Divi lazy load background images

Or use Optimole to lazy load CSS selectors (very similar to lazy render HTML elements in the previous step). WP Rocket makes you move background images to inline HTML which is a pain.


8. Upload Images In WebP

Do this manually, here’s why:

Using image optimization plugins to compress images and convert them to WebP can be taxing on your server and increase memory usage. And if you’re using an image CDN like Cloudflare Polish, it doesn’t always convert images to WebP even when savings are significant. You can avoid both by uploading WebP images manually which fixes serve images in next-gen formats.

Test webp images chrome dev tools
Use the Chrome Dev Tools Network report to see if image CDNs are actually serving images in WebP


9. Exclude Viewport Images From Lazy Load And Preload Them

Since above the fold images are seen first, they should be excluded from lazy load. Otherwise, this creates a resource load delay and increases LCP. They should also be preloaded to make them “high priority” which also improves LCP. Luckily, there’s an easy (1-click) way to do both.

The preload critical images setting in FlyingPress and Perfmatters is the easiest way to do both. Just set the number of images that usually load above the fold (2-3 is typical) and you’re done.

Preload critical images perfmatters

LiteSpeed Cache and WP Rocket have a relatively simple way of excluding above the fold images from lazy load, but it doesn’t preload them. For that, you can use Preload Features Images which is compatible with Divi. But if you have additional above the fold images, you’ll need to preload them manually which you can do in Perfmatters or Pre* Party Resource Hints.


10. Use A Better Image Optimization Setup

Optimole if you’re going to use a plugin, but Cloudflare Mirage/Polish is better.

Plugins like Imagify don’t support mobile image resizing for better mobile LCP, uses server resources, and take up storage when creating backups. Optimole addresses most them but I prefer Cloudflare Mirage/Polish (with image resizing) which optimize images “on the fly.” It’s $20/mo with Cloudflare Pro or included with Cloudflare Enterprise on + Cloudways.

Imagify ShortPixel Optimole SiteGround CDN Bunny Optimizer Cloudflare Mirage/Polish
Mobile resizing x Requires ShortPixel Adaptive Images x
Viewport optimizations x x x x
Network optimizations x x x x
AVIF conversion x x x
AVIF support x x x
Serve images from CDN x Requires ShortPixel Adaptive Images Cloudfront SiteGround CDN
No server usage x x x x
No bloat x x Offload to cloud x
Price Free 20MB/mo then $9.99/mo Free 100 credits/mo then $3.99/mo Free 5,000 visits/mo then $19.08/mo Free ($7.49/mo for paid CDN) $9.5/mo or $.03/GB w/ FlyingCDN Included w/ Cloudflare Enterprises

There are quite a few ways to optimize images on your Divi site. Most speed testing tools only show errors for the single page that’s tested, so make sure you test your most important pages.

Assuming you’re uploading images in WebP, scaling them to correct dimensions, optimizing viewport images (step #9), and using a good image optimization plugin or CDN, this should fix most image-related PageSpeed items. The only other things would be adding missing image dimensions (most cache plugins do this) and use a long cache policy in your host or Cloudflare.

Optimize images in wordpress


These load across your entire website, and CSS is much more lightweight than Divi’s code.

I know this is over some people’s head including mine, so you can outsource it to a developer. WP Johnny offers it as a service, but he’s a busy guy and expensive. That said, you can hire my developer on who I’ve worked with for 10 years. He’s in Bangladesh so there is a time change, but his work and communication are both excellent. Hence, the perfect 5/5 rating.

Pronaya wordpress speed optimizer


12. Use Transform + Translate In Animations

I’m not a fan of animations but if you must use them, use the CSS transform properly instead of changing width/height attributes. It’s recommended by Google and should reduce layout shifts.

Divi transform animations


13. Disable Plugins On Pages They’re Not Used

You’ve probably heard of Perfmatters or Asset CleanUp which remove CSS/JS by disabling plugins (and individual scripts/styles) on pages/posts they’re not used. I prefer Perfmatters because of its other optimizations too (bloat removal, preload critical images, local fonts, etc).

Step 1: Activate the script manager (Settings → Perfmatters → Extras → Script Manager), go to your script manager settings, and enable testing mode. This lets you test the script manager without it breaking your site, but remember to disable it when you’re ready to publish changes.

Step 2: View the script manager and unload plugins where they’re not used (everywhere but pages, posts, current URL, Regex, etc). Plugins like your contact form are easy… just view your contact page, and use the script manager to disable it everywhere but current URL. You could even disable your social sharing plugin “everywhere but posts” if you only show it on your blog.

Disable divi contact form

Other plugins aren’t so easy. Most of them load scripts/styles across your entire website. Which means if you’re using them for something like your header or nav menu, it’s a PageSpeed killer.

Divi plugin size 1


14. Test Plugins For CSS, JavaScript, Memory Usage

I consider a plugin “slow” if it adds lots of CSS/JavaScript, loads across your entire site, increases memory usage, or uses jQuery. Here’s how to test whether your plugins do this.

Extra CSS/JavaScript – open the Chrome Dev Tools coverage report and search for “Divi.”

Divi css javascript 1

High Memory Usage – I usually search plugins in WP Hive, but most Divi plugins aren’t listed in the WordPress plugin repository, so you’ll need to use something like Query Monitor. I also have a list of common slow plugins (including those that increase memory usage), but it’s not Divi-specific. However, it’s well-known that many security, image optimization, and backup plugins increase memory usage (you can avoid most these by using an image CDN like Cloudflare Pro).

Plugin Category Memory Impact PageSpeed Impact
Analytify Analytics X
Backup Buddy Backup X
iThemes Security Security X
Broken Link Checker SEO X
Jetpack Security X X
Query Monitor Analytics X
NextGEN Gallery Gallery X X
Site Kit by Google Analytics X
Wordfence Security X
wpDiscuz Comments X X
WPML Translate X X

jQuery Plugins – if using Perfmatters, enable display dependencies in the script manager settings. Now when you view your script manager, you can see all plugins that rely on jQuery.

Perfmatters display dependencies jquery


15. Rethink Your Cache Plugin

LiteSpeed Cache if you’re on a LiteSpeed server, FlyingPress in all other cases.

WP Rocket and their other products (Imagify + RocketCDN) are do a poor job with LCP, TTFB, and mobile speed. You can’t preload LCP images, resize mobile images, host fonts locally, and there’s no full page caching. Plus, they only released 1 new feature after 2020 in their changelog.

SiteGround Optimizer lacks even more features and is unstable. If you insist on using it, I’d probably only use it for dynamic caching/Memcached, then use FlyingPress for everything else.

SG Optimizer WP Rocket FlyingPress LiteSpeed Cache
Server-side caching x x
Object cache integration x x
Delay JavaScript x
Remove unused CSS x Inline Separate file Separate file
Critical CSS x
Preload critical images x x x
Exclude above the fold images By class/type By URL/class Automatic Automatic
Lazy load background images x Inline HTML lazy-bg class x
Add missing image dimensions x
Lazy load iframes x
YouTube iframe preview image x
Self-host YouTube placeholder x x x
Host fonts locally x x
Font-display: swap x
Preload links x
Bloat removal (beyond Heartbeat) x x (details) x
Lazy render HTML elements x x
Guest Mode x x x
Advanced cache control x x x
Gravatar cache x x x
Limit post revisions Delete all Delete all Keep some Keep some
CDN Google Cloud StackPath BunnyCDN
CDN PoPs 176 73 120 83
Full page caching x x
CDN geo-replication x x x
CDN image optimization x x
CDN image resizing for mobile x x x
CDN DDoS protection x x
CDN bandwidth Unmetered Very limited Usage-based Usage-based
Documented APO compatibility x x x
Documentation Not detailed Good Not detailed Good
New features Infrequent Infrequent Frequent Frequent
Facebook group Join Join Join Join
CDN price $14.99/mo $8.99/mo $.03/GB $.02-.08/GB
Plugin price Free $59/year $60/year Free
Renewal price Free $59/year $42/year Free

Omm switches to flyingpress


16. Increase PHP Version And Memory Limit

Compare your system status with Divi’s hosting requirements. This is found under Divi → Support Center → Show Full Report. However, those are minimum numbers and I suggest upgrading to the highest compatible PHP version and using at least a 512 MB memory limit. Elementor recommends 768 MB for best performance, so you could even increase it to that.

PHP Version = 8.0+
memory_limit = 512M+
post_max_size = 64M
upload_max_filesize = 64M
max_execution_time = 120
max_input_time = 60
max_input_vars = 1000
display_errors = 0

Divi hosting requirements


17. Enable Object Cache + OPcache

These help with performance + memory usage and can be found in your host. There are advantages to Redis over Memcached and Redis Object Cache Pro is even better which is available on Cloudways,, and some other hosts. Once object cache is activated, you’ll need to connect it to your website using either your cache plugin (i.e. LiteSpeed Cache + W3 Total Cache) or using a dedicated Redis plugin (search for your host’s specific instructions).

Opcache memcached redis


18. Reduce Memory Usage

Before upgrading hosts, try the following:

  • Offload bandwidth to CDNs – especially helpful when using full page caching.
  • Firewall – block unwanted requests to your server, resulting in less bandwidth.
  • Bot protection – Wordfence’s live traffic report shows all bots hitting your site, but disable it when you’re done and use something like Cloudflare’s bot protection.
  • Remove high memory usage plugins – disable plugins 1 by 1 and test your site.
  • Enable Perfmatters general settings – disabling XML-RPC, controlling Heartbeat, increasing the autosave interval, and moving your wp-login page should all help.
  • Replace wp-cron with a real cron job – Google instructions for your specific host.
  • Limit preloading in cache plugins – WP Rocket’s preloading, LiteSpeed Cache’s crawler, or SG Optimizer’s preheat cache can all increase CPU usage. Some can be controlled more than others. WP Rocket can only preload important sitemap URLs ( and and can increase the preload interval.
  • Limit automatic cache clearing in cache plugins – specific actions trigger your entire cache to clear. Try disabling automatic clearing and setup a cron job to clear this at a specific time. Cron jobs can be setup for cache clearing/cache preloading.
  • Limit unused CSS batch size – decrease the batch size and increase cron interval.
  • Disable link preloading – this is a setting in optimization plugins where if users hover over lots of links, all those pages will have to download in the background.
  • Protect your login page – common target for bots/hackers so you should protect by either moving the wp-login page, with, and limiting login attempts.
  • Block spam comments – I use Antispam Bee since Akismet isn’t free anymore.
  • Choose a hosting plan with more resources – Kinsta, Hostinger, and GoDaddy skimp on these… check their resource limits page before signing up for a plan.
  • Try LiteSpeed – did you know LiteSpeed can handle 2x the capacity of Apache?
  • Disable pingbacks/trackbacks – found in your WordPress discussion settings.
  • Remove autoloaded data – plugins/themes can leave behind autoloaded data even when you delete them which can be cleaned up in your wp_options table.

Wp rocket sitemap preloading
Limit preloading to only important sitemap URLs (not the full sitemap)


19. Remove Bloat (And Database Bloat)

Use FlyingPress’ bloat removal settings, Perfmatters, or Unbloater.

Flyingpress bloat settings 2

WP-Optimize does a better job cleaning your database than cache plugins because:

  • It can remove unused tables (shown below).
  • It can take database backups with UpdraftPlus.
  • It can keep a certain amount of post revisions (instead of deleting them all).

Wp optimize unused database tables


20. Use A Performant CDN/DNS With Full Page Caching

Why would you use anything but Cloudflare’s DNS/APO or on LiteSpeed?

RocketCDN (StackPath) doesn’t have full page caching and SiteGround’s CDN requires you to use their DNS which was blocked by Google for 4 days, causing customers to lose rankings or get deindexed from Google completely. This is what happens when cache plugins and hosting companies try to convince you their CDN is better than already well-established CDN providers.

You also have several third-party Cloudflare Enterprise services like FlyingProxy, Cloudways, and While these are all great choices (and better than most CDNs), they’re not all the same. I’ll get to this in section 21) but basically,’s Cloudflare Enterprise is better.

On LiteSpeed, you should ideally be using’s paid plan which unlike the free plan, uses all 80+ PoPs with DDoS protection. QUIC is also needed for image/page optimizations to work with LiteSpeed Cache. LiteSpeed server + LiteSpeed Cache + is a solid combo.

RocketCDN SiteGround CDN FlyingCDN By FlyingPress Cloudways Cloudflare Enterprise Cloudflare Enterprise
CDN StackPath Google Cloud BunnyCDN Cloudflare Cloudflare
Tbps 100 Not listed 80 192 192
Locations 73 176 120 300 300
Full page cache x x APO APO
Brotli x
Smart routing x Anycast SmartEdge Argo Argo
Priority routing x x x
Load balancing x
Image optimization x Very limited Bunny Optimizer Mirage/Polish Mirage/Polish
Compression x
WebP x x
Mobile resizing x x
Firewall x x
Anti-DDoS x x
Bandwidth Not unlimited as advertised Unmetered Unlimited 100GB Determined by hosting plan
Price $8.99/mo $14.99/mo $.03/GB $5/mo Free w/ hosting


Cloudflare apo impact on ttfb fcp si
Impact of APO on TTFB, FCP, Speed Index (source: Cloudflare)


21. Use LiteSpeed Hosting With NVMe Storage

ChemiCloud uses LiteSpeed servers, NVMe SSDs, Redis, and more CPU/RAM which can scale through their Turbo Boost add-on. You’ll configure LiteSpeed Cache (which is free and does a great job with core web vitals) on top of’s CDN or Cloudflare APO. This beats other hosting setups in terms of TTFB, price, support, and scalability. With a 5/5 TrustPilot rating, it’s obvious other hosts are popular from marketing, but fall short when you actually look at specs.


GoDaddy Managed WP Deluxe Plan Bluehost Choice Plus Plan SiteGround GrowBig Plan Hostinger Business WP Plan ChemiCloud WordPress Turbo Plan
Server Apache + Nginx Apache + Nginx Apache + Nginx LiteSpeed LiteSpeed
CPU cores + RAM 1 core + 512MB Not listed Not listed 2 cores + 1.5GB 3 cores + 3GB (scalable to 6/6)
Storage 60GB SATA 40GB SATA 20GB SATA 200GB SATA 40GB NVMe in 10/11 locations
Object cache Memcached x Memcached Memcached Redis
Database MySQL MySQL MySQL MariaDB MariaDB
Data centers 9 6 10 8 11
Cache plugin x x SG Optimizer LiteSpeed Cache LiteSpeed Cache
CDN Cloudflare (free) Cloudflare (free) SiteGround CDN ($14.99/mo) QUIC (but use Cloudflare APO) QUIC (but use Cloudflare APO)
Full page caching x x
Control panel Custom cPanel Site Tools hPanel cPanel
Inodes 250,000 200,000 400,000 600,000 500,000
Incidents Malware, several data breaches Downtimes TTFB, DNS, CPU issues, controls FB groups Downtimes, fake reviews, scams, bad poll None
Migrations Paid Free on qualified accounts only $30/site Unlimited (but screws it up) 10+ free (details)
Support D D C D A
TrustPilot rating 4.7/5 4.2/5 4.8/5 4.6/5 (fake) 5/5
Intro price $10.49 (2 years) $5.45 (1 year) $4.99 (1 year) $3.99 (4 years) $5.99 (3 years)
Renewal price $16.99/mo $19.99/mo $29.99/mo $9.99/mo $19.95/mo
1 year price $143.88 $65.40 $59.88 $59.88 $82.62
3 year price $359.64 $268.20 $659.64 $191.52 $215.64
 Chemicloud gtmetrix report
 Chemicloud vs sitegroundChemicloud pro feedbackChemicloud speed ui supportSiteground vs chemicloud comparison

Litespeed vs nginx vs apache

Which web server do you use recommendLitespeed cache litespeed serverLitespeed litespeed cache quic. CloudLitespeed pagespeed scores

Which web server do you useLitespeed on litespeed serverLitespeed cache vs. Wp rocketDivi litespeed

Bad Hosts

Mainstream hosts like SiteGround, Hostinger, WPX, and SlowDaddy don’t live up to the hype. They use slow SATA SSDs, no Redis, and skimp on CPU/RAM/inodes (causing CPU issues and forced upgrades). It gets more expensive with renewals, add-ons, price increases, and wasted time dealing with incidents like SiteGround’s DNS causing 2M sites to get deindexed in Google. The only reason you see “glowing reviews” is because SiteGround threatens people who write bad reviews, controls Facebook groups, and untruthful affiliates. Hostinger writes fake reviews and scams people, so don’t believe “unlimited” storage/websites/bandwidth on their website. WPX isn’t ideal for dynamic/international sites (they literally say they target a TTFB of <400ms). Slow technology + limited resources + prices + incidents + poor support… these aren’t worth it.

Siteground cpu dance your faultSiteground to cloudways dns issueSiteground slow ttfb leaveSiteground affiliate payoutHostinger is the worst
Siteground membership cpu limits fastcometSiteground renewal pricesMove on from siteground messSiteground bluehost godaddy ttfb affiliateHostinger banned from facebook groups

Siteground no value


22. Use + Cloudflare Enterprise For A 100ms Global TTFB

If the fastest hosting means the fastest TTFB, averages 100ms.

That’s who I use and they’re specifically good for international audiences and WooCommerce/dynamic sites (hence the 100ms global TTFB) thanks to free Cloudflare Enterprise, 32 CPU cores + 128GB RAM, NVMe SSDs, Redis/Redis Pro, and LiteSpeed’s PHP.

Average ttfb speedvitals
Average TTFB of 40 locations measured in SpeedVitals

10 things to know about TTFB:

  1. Hosting/CDN are the 2 biggest factors.
  2. TTFB is 40% of LCP and also part of FCP/INP.
  3. Which means it impacts 4/6 user metrics in PSI.
  4. SpeedVitals measures TTFB in 40 global locations.
  5. Test your site 3 times in SpeedVitals for accurate numbers.
  6. Doing this ensures your caching/CDN are working properly.
  7. Check your average TTFB of all 40 locations in your 3rd test.
  8. PSI + GTmetrix only test TTFB in 1 location (use SpeedVitals or KeyCDN).
  9. Google flags your TTFB if it’s over 600ms, but 100-200ms is obviously better.
  10. WP Hosting Benchmark also tests hosting performance (here are my results).

SiteGround Cloud Jump Start Plan Kinsta Starter Plan Cloudways Vultr HF (2GB) Starter Plan
Type Cloud Cloud Cloud Private cloud
Server Apache + Nginx Apache + Nginx Apache + Nginx Apache + Nginx
Nginx reverse proxy $50/mo
Cores/RAM 4 cores + 8GB 12 cores + 8GB 1 core + 2GB 32 cores + 128GB
Storage 40GB SATA 10GB SATA 64GB NVMe 10GB NVMe
Object cache Memcached $100/mo Redis Redis Pro Redis (Redis Pro on Business plan)
PHP processor FastCGI FastCGI FPM LiteSpeed
PHP workers Not listed, but CPU limits are common 2 No limit No limit
Memory limit Adjustable 256MB Adjustable 1GB
Database MySQL MySQL MariaDB MariaDB
Bandwidth + visits 5TB/mo 25k/mo 2TB/mo 50GB + 250k/mo
CDN $14.99/mo SiteGround CDN Cloudflare APO + firewall rules (read) $5/mo Cloudflare Enterprise + challenge pages Free Cloudflare Enterprise (details)
CDN locations 176 300 300 300
Full page caching
Smart routing Anycast x Argo Argo
Image optimization Limited x Mirage/Polish Mirage/Polish
DNS Google deindexed 2M SG domains Amazon Route 53 $5/mo DNS Made Easy Cloudflare
Cache plugin SG Optimizer Use FlyingPress Breeze Use FlyingPress
Data centers 10 35 44 Served from Cloudflare’s edge
Control panel Site Tools MyKinsta Custom (difficult) Mission Control
Email hosting x x x
Support C B C A
Migrations $30/site Unlimited free 1 free + $25/site Unlimited free
TrustPilot rating 4.8/5 4.2/5 4.6/5 4.9/5
How it starts costing more High initial price, CPU limits, CDN, price increases, internal incidents PHP workers, add-ons, monthly visits, bandwidth, price increases Scaling CPU/RAM, CPU limits, CDN, backups, price increases Bandwidth
Monthly price $100 + CDN $29 when paying yearly + add-ons $30 + CDN $25 when paying yearly (no add-ons)

*Here’s a table comparing vs. WP Engine, WPX, and Flywheel.

Aside from my biased opinions, they’ve blown up in Facebook groups where Ben Gabler (CEO) did an AMA. They have all 5/5 star TrustPilot reviews where you’ll see people who switched to from other hosts (but not the other way around) even when you search SG’s 13,000 TrustPilot reviews. You can see more migration results if your search their TrustPilot for “TTFB.”

Move to rocket. Net from sitegroundSiteground cloud cpu usage upgrades
Kinsta to rocket. Net resultsRocket. Net vs cloudways cpu usageRocket. Net no competitionRocket. Net trustpilot review
Siteground to cloudways to rocket. Net 2Rocket. Net vs siteground commentMoved to rocket. Net vs sitegroundSiteground cloud hosting bad reviewKinsta to rocket. Net ttfb redisRocket. Net vs kinstaRocket. Net vs kinsta priceRocket. Net faster than cloudwaysRocket. Net vs. Cloudways comparisonBluehost to cloudways to rocket. NetSiteground to rocket. Net post 2Rocket. Net vs cloudways vultr hf trustpilot review

Rocket. Net woocommerce elementor

Rocket. Net 2023 wordpress hosting benchmarks was a top performer in Kevin Ohashi’s 2023 WP Hosting Benchmarks

Here’s an interview I did with Ben (he also did one with Admin Bar).


  • CDN integrations – Cloudflare Enterprise is arguably the fastest CDN for improving TTFB between it’s large network and robust features. However, most hosts only use free Cloudflare, only have a few Enterprise features (incomplete integration), or claim their own CDN is better. Rocket has the closest thing to true Cloudflare Enterprise due to Ben’s experience as StackPath’s Chief Product Officer.
  • LiteSpeed PHP – not to be confused with LiteSpeed servers, but LiteSpeed’s PHP is “similar to FCGI, but is more efficient” according to the official website.
  • Mirage/Polish – automatically optimize images (compression, WebP, etc) using Cloudflare without adding bloat or using resources like plugins do (1 less plugin).
  • WooCommerce optimized – is specifically good for WooCommerce with Redis Object Cache Pro‘s Relay integration, APO, Argo Smart Routing, NVMe SSDs, no PHP worker limits, and smart caching uses less resources when purging.
  • DNS – uses Cloudflare’s DNS which is consistently a top performer on SiteGround’s CDN makes you use their internal DNS which caused 2 million domains to be blocked by Google. Kinsta uses Amazon Route 53 DNS, and Cloudways charges for DNS Made Easy… which are both slower than Cloudflare’s.
  • Does a close data center matter? – with a 100ms global TTFB, not really. If you use a CDN without features like full page caching and smart routing, then it does.

It’s $1 your 1st month with free migrations. Or reach out to Ben and schedule a demo. The dashboard is easy and Cloudflare Enterprise is automatic… the only thing I did initially was upgrade PHP versions, ask support to add Redis, and remove CDN/image optimization plugins.


Conclusion: Divi Is Making Improvements, But It’s Still Slow

My blog is all about performance and I can tell you, I would never use Divi (I’m using GeneratePress if you must know). Divi is too slow and has too many bugs. A lot of people use page builders because they’re easy, but it ain’t so easy when you constantly run into problems.

This post is old but still relevant:

Divi rant


Frequently Asked Questions

Why is Divi slow?

Divi adds extra CSS/JavaScript and requires more memory than block editors. This extra bloat can lead to PageSpeed errors and lack of memory when using cheap/shared hosting.

Why is the Divi backend slow?

Divi's backend is usually slow because of bad hosting configurations, lack of server resources with your hosting plan, or plugins that eat up memory with background tasks.

Why is Divi slow on mobile?

If your Divi mobile site is slow, try serving smaller images to mobile (using an adaptive images plugin or CDN) and reducing latency with a faster DNS/CDN. Mobile users are specifically prone to latency. Otherwise, most desktop optimizations carry over to mobile.


You Might Also Like:


  1. Hi I have a question on why you chose those settings for Divi performance? Would it not make it faster by enabling all of those items?

    • Hey Theresa,

      Whether you turn them on/off really depends on your site, which optimization plugin(s) you use, etc.

      Most cache plugins do critical CSS, disable emojis, and optimize Google Fonts. Third-party scripts should usually be delayed, not deferred. If you’re not using Gutenberg, the CSS should be ideally removed, not deferred.

      Just depends on the tools you’re already using.

  2. WOW, what an immersive post! Already found many improvements here which doubled the load speed. Keep up the great work!


Leave a Comment