The Ideal SiteGround Optimizer Settings For Core Web Vitals: Disable Most Settings And Use FlyingPress Or Perfmatters (2023)

Siteground optimizer settings

Ugh, SiteGround Optimizer.

I’ll show you how to configure SiteGround Optimizer’s settings, just know it does a poor job with web vitals, especially LCP and CLS. You can’t preload images, remove unused CSS, delay JavaScript, specify image dimensions, host fonts locally, and it still doesn’t support critical CSS.

For better results, you should also use FlyingPress or Perfmatters (you could even use WP Rocket, but I recommend FlyingPress). I’ll also show you how to configure both of these with SiteGround Optimizer including duplicate settings + new features to optimize your site. You’ll still use SiteGround Optimizer’s dynamic caching + Memcached, but not for most other settings.

For a CDN, Cloudflare’s APO is faster, cheaper, and more reliable than SiteGround’s CDN, especially since you have to use their DNS to use it which caused 2M domains to get deindexed.

Another reason not to use it is compatibility issues which support often blames on third-party plugins. Just search their support forums for “Elementor” or other plugins/themes you’re using.

I left SiteGround and suggest you do the same. ChemiCloud is faster with LiteSpeed servers + NVMe storage + Redis (several people already moved from SiteGround). For international/WooCommerce sites, I use who has a <100ms global TTFB average (here are more people who moved from SiteGround). If you haven’t heard of these, it’s because SiteGround controls many Facebook groups and are promoted by admins, affiliates, and they threaten people who write bad reviews. But if you want to pay $25/mo+ for their shared hosting or $100/mo+ for cloud hosting… it’s your money.

Siteground no value


1. Dashboard

Here’s why you don’t need perfect scores (4/4/, 3/3, 6/6, 3/3):

When using other cache/optimization plugins (WP Rocket, FlyingPress, Perfmatters), it should look more like (3/4, 3/3, 3/6, 1/3) mainly because of these overlapping features: file-based caching, browser caching, CSS settings, lazy load.

File-based caching overlaps with page caching in other cache plugins, so only enable it in 1 (browser caching also overlaps and is usually easier to disable using SiteGround Optimizer). Dynamic caching can have compatibility issues when using APO, but leave on otherwise. All SiteGround’s CSS settings should be left off when using “remove unused CSS” in plugins like Perfmatters/FlyingPress. SiteGround Optimizer’s lazy load settings lack many features with frequent compatibility issues. For this, I recommend either Perfmatters or FlyingPress which can also preload critical images (for better LCP scores) and lazy load CSS background images.

Other common overlapping features are Heartbeat control, defer JavaScript, and minifying CSS/JS. You can use SG Optimizer for these, then disable them in other optimization plugin(s).

FlyingPress/Perfmatters also have many lacking features not found in SiteGround Optimizer: delay JavaScript, font-display: swap, add missing image dimensions, and host fonts locally. FlyingPress can also lazy render HTML elements and self-host YouTube placeholders while Perfmatters can remove bloat, preload CSS/JS files, and includes a script manager to reduce CSS/JS by disabling plugins on pages/posts they’re not used. For best results, I suggest both.

Finally, use WP-Optimize to clean your database which can remove tables left behind by old plugins, take backups, and keep a few post revisions (instead of deleting them all). All that said, SG Optimizer works best when combined with FlyingPress, Perfmatters, and WP-Optimize.

There’s still 1 key lacking feature which can improve mobile/LCP scores, and that’s resizing images for mobile which SiteGround Optimizer (and their CDN) don’t support. You can try ShortPixel Adaptive Images or image CDNs like Bunny Optimizer or Cloudflare’s image resizing.

I know it’s confusing, but with so many lacking features, you’re forced to compensate by using other plugins to get the best results. If you have any questions about this, leave me a comment.

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
Local YouTube placeholder x x x
Local Gravatars x x
Local fonts x x
Font-display: swap x
Preload links x
Bloat removal 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 Delete all Keep some
CDN Google Cloud StackPath BunnyCDN
CDN PoPs 187 73 120 83
Full page caching x x
CDN permanent storage x x x
CDN image optimization x x
CDN mobile image resizing x x
CDN DDoS protection x x
CDN bandwidth Unmetered Very limited Unlimited Unlimited
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 $3/100GB $.02-.08/GB
Plugin price Free $59/year $60/year Free
Renewal price Free $59/year $42/year Free

Siteground optimizer dashboard 1


2. Caching Settings

If you’re using another cache plugin with SiteGround Optimizer, disable file-based caching and only use it for dynamic cache/Memcached. With Perfmatters or only SG Optimizer, enable all 3.

Siteground optimizer caching settings

  • Dynamic Caching: On – leave dynamic caching on unless you use Cloudflare APO, then leave it Off since there have been several compatibility issues which SiteGround denies.
  • File-based Caching: On – leave Off if you’re using FlyingPress or WP Rocket. You could also disable WP Rocket’s caching using their helper plugin, but the first option is easiest.
    • Cleanup Interval: 1 week – expiration for file-based caching until it’s purged.
    • Preheat CacheOn – artificially fills the cache so visitors get a better cache hit ratio (similar to preloading in WP Rocket). Once the cache is purged, it’s preloaded using your sitemap and is executed with cron. This can increase CPU usage if you’re not careful and leaves little customization room, so keep an eye on your CPU usage.
    • Logged-in Users Cache: Off – only enable if you have user-specific content where visitors need their own cached version (membership sites for example). There are no customization settings / helper plugins and this also increases the stored cache size.

Siteground optimizer preheat cache

  • Memcached: On – enables Memcached object cache which speeds up database queries. You will first need to activate Memcached in Site Tools (Speed →  Caching → Memcached).
Siteground memcached site tools
Activate Memcached in Site Tools before activating it in SiteGround Optimizer
  • Automatic Purge: purges the cache when specific changes are made to your website according to SiteGround’s rules. There’s been several reports of this not working, so make sure it is. A full purge is done during larger changes (updating WordPress plugins/core or deleting a category) while a smart purge is done for smaller updates (modifying a post or adding a comment). Dynamic and file-based caching must both be enabled for it to work.
    • Purge WordPress API Cache: On – also purges the Rest API which is used on many websites including the block editor. If you don’t use Rest API, you can leave this off.
  • Manual Cache Purge: usually only needed when automatic purge isn’t working for you.
  • Exclude URLs From Caching: exclude URLs from dynamic and file-based caching. The documentation shows the example of the /cart/ page being excluded, so I assume they don’t automatically exclude URLs and you will need to do these manually. You can also use wildcards to exclude specific sections of your site, such as:*
  • Browser-Specific Caching: Off – SiteGround recommends only enabling this if you’re having issues with plugins or things like generating the mobile version of your website.
  • Testing the cache – I recommend for testing the cache in SiteGround Optimizer and your CDN. They also have some documentation on testing the CDN cache.

Siteground cache test


3. Environment Settings

I recommend disabling scheduled database maintenance and use WP-Optimize instead. Also make sure you only use one plugin for Heartbeat Optimization, then disable it in other plugins.

Siteground optimizer environment settings

  • HTTPS Enforce: On – automatically force visitors to use a secure HTTPS connection. I assume most of you will be using the free Let’s Encrypt SSL you get through Site Tools.
  • Fix Insecure Content: Off – if you see mixed content warnings in your browser when using SSL, it means you’re loading both HTTPS + HTTP. This can fix it, leave off otherwise.
  • GZIP Compression: On – compress pages (Brotli is only available on SiteGround’s CDN).
  • Browser Caching: On – stores static files in the browser so they can be accessed quicker. This should be left off when using other cache plugins which also have browser caching.
  • WordPress Heartbeat Optimization: Disabled, 120s, Disabled – the only place you usually want Heartbeat is the post editor (posts and pages) since it handles things like autosaves to prevent you from losing work. Then disable it in the admin and frontend. Otherwise, the WordPress Heartbeat API will run every 15-60s and increases CPU usage.
  • Scheduled Database OptimizationOffWP-Optimize does a better job since you can take database backups via UpdraftPlus, keep a few post revisions (instead of deleting them all) and remove tables left behind by old plugins you deleted. When viewing tables, you may also notice certain plugins/modules add overhead, so consider disabling those.
Wp optimize unused database tables
Use WP-Optimize to remove tables left by old plugins marked as “not installed”
Wp optimize schedule database cleanups
WP-Optimize keeps a few post revisions (unlike SiteGround Optimizer which deletes them all)


4. Frontend Settings

Minify files, but don’t combine them.

SiteGround Optimizer can’t remove unused CSS or delay JavaScript while plugins like Permfatters, FlyingPress, and WP Rocket can. I recommend enabling “remove unused CSS” in one of those plugins and disabling all CSS settings in SiteGround Optimizer. I also recommend enabling “delay JavaScript” and configure SiteGround Optimizer’s JavaScript settings normally.

Siteground optimizer css settings

Perfmatters remove unused css inline vs. File
SiteGround Optimizer can’t remove unused CSS, so use other plugins (screenshot is Perfmatters)

Siteground optimizer javascript settings

Siteground optimizer frontend general settings

  • Minify CSS/JavaScript/HTML: On – even when using Cloudflare’s APO, you should use your cache plugin to minify files which removes whitespaces and makes the files smaller.
  • Exclude From Minification: if certain minify settings break your website, you’ll need to view your source code, find the problematic files, then exclude them from minification.
  • Combine CSS/JavaScript: Off – most websites shouldn’t combine files for several reasons. It can often result in slower load times and have issues with HTTP/2 + HTTP/3.
  • Exclude From Combination: no need to do anything here unless the combine setting is turned on and you need to exclude specific CSS, JavaScript, or HTML files from combining.
  • Preload Combined CSS: Off – if you combined CSS, this preloads the file to load faster. But again, since most websites shouldn’t combine, this setting should also be disabled.
  • Defer Render-Blocking JavaScript: On – fixes render-blocking resources but can break your site, in which you’ll exclude files. You can both defer JavaScript (in SG Optimizer) and delay JavaScript (in your other optimization plugin) since they’re different optimizations.
  • Exclude From Deferral Of Render-Blocking JS: if deferring JavaScript breaks your site, exclude broken files. Check support threads for issues with WooCommerce/page builders.

Siteground optimizer exclude from deferral of render blocking js

  • Web Fonts Optimization: On – combines fonts, loads them inline asynchronously, preloads them, and preconnects third-party fonts. I highly recommend opening your Waterfall chart and make sure fonts are self-hosted (not using, using woff2, and font-display: swap for lower CLS. Font icons can also create requests and page builders (Elementor) can disable unused fonts/font icons, or use custom fonts/font icons.
  • Fonts Preloading: only self-hosted fonts can be preloaded. Look at the font files in your GTmetrix Waterfall chart, copy the URLs of all fonts loading above the fold (or mentioned in CSS files), then preload them. Test results since preloading too many fonts can have a negative effect. Retest your site and your font’s blocking time (brown bar) should go down.

Siteground optimizer fonts to preload

  • Remove Query Strings From Static Resources: Ondeprecated GTmetrix item.
  • Disable Emojis: On – removes JavaScript code needed to convert emojis (if you need them, just use Unicode). Most optimization plugins disable emojis, so only use 1 plugin.
  • DNS Pre-fetch For External Domains: Usually Empty – delaying JavaScript is more effective. Third-party fonts and CDN URLs should use preconnect instead, so the only third-party domains you should prefetch are those not being delayed/preconnected.
Third party code
Most third-party code should be hosted locally or delayed (faster than prefetch)
Siteground optimizer manage external domains
Only prefetch third-party domains if they’re not being delayed or preconnected
Perfmatters delay javascript
SiteGround Optimizer can’t delay JavaScript, so use other plugins (screenshot is Perfmatters)

### Popular JavaScript Files To Delay In Other Optimization Plugins ###

Lacking Features

  • Delay JavaScript: often done for third-party code and plugins loading below the fold (social sharing or comment plugins). Flying Scripts, Perfmatters, FlyingPress and WP Rocket do this. WP Rocket is automatic while other plugins require you to manually add each file you want to delay. I listed common JS files above, but you want to read your plugin’s documentation since it can be different for each plugin.
  • Remove unused CSS: ideally use Perfmatters or FlyingPress since they load used CSS in a separate file (as opposed to WP Rocket’s inline method which is slower).
  • Critical CSS: this has been a feature request for years and SiteGround said they are working on it, but it’s still not here. You could try Autoptimize with Critical CSS power up, but I haven’t tried it on SiteGround Optimizer. Use it at your own risk.
  • Host fonts locally: self-hosted fonts are faster and can be preloaded (instead of pulling them from external websites like You can host fonts locally using Perfmatters, FlyingPress, OMGF, or you can try doing this manually.
  • Font-display: swap: fixes the “ensure text remains visible during webfont load” recommendation in PSI. Most optimization plugins (and Elementor) support this.
  • Preload CSS/JS files: SiteGround Optimizer can only preload your combined CSS files, but you may want to preload other CSS/JS files like wp-block-library if you’re using Gutenberg. I recommend Perfmatters which supports dynamic preloading.
  • Script manager: Perfmatters can disable plugins on specific pages with the script manager (for example, disabling your social sharing plugin everywhere but posts).


5. Media Settings

SG Optimizer lacks many image optimizations (see full list at the bottom of this section).

Using a plugin to optimize images also uses server resources, as well as disk space when backing up images. You’re better off using Cloudflare Pro or Bunny Optimizer which not only supports more optimizations, but optimize them “on the fly” without using server resources or creating backups. However, these cost money so if it’s not in your budget, use Optimole instead.

FlyingPress/Perfmatters have several other image optimizations like lazy loading background images, preloading above the fold images, replacing YouTube iframes with a preview image, and adding missing image dimensions (none of which are supported by SiteGround Optimizer).

Imagify ShortPixel Optimole SiteGround CDN Bunny Optimizer Mirage/Polish
AVIF support x x x
Serve images from CDN x SP Adaptive Images Cloudfront Google Cloud
No server use x x x x
No bloat x x Offloading 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 $14.99/mo $9.5/mo or $.03/GB w/ FlyingCDN Free with

Siteground optimizer media settings

I don’t recommend SiteGround Optimizer for optimizing images, but if you want to use it, here are the settings.

  • Image Compression: Disable –  only enable when using SiteGround Optimizer for image optimization. PSI tests images at an 85% compression level – so that’s what I recommend.

Siteground optimizer image compression settings 1

  • Use WebP Images: On – if you’re using an image CDN like Cloudflare + Polish, it doesn’t always serve images in WebP, so I suggest converting them with SiteGround Optimizer, another plugin, or uploading them in WebP manually. SiteGround Optimizer’s default WebP quality is 80% and can be changed by adding the code to your functions.php file.
add_filter( 'sgo_webp_quality', 'webp_quality' );
function webp_quality( $quality ) {
    // Add the value you want to adjust as Webp image quality.
    $quality = 80;

    return $quality;
  • Lazy Load Media: Off – can’t lazy load backgrounds, replace YouTube iframes with a preview image, and has ongoing compatibility issues. Perfmatters and FlyingPress support both so I recommend using one of those for lazy loading, then disable it here.
  • Exclude CSS Classes From Lazy Load – “preload critical images” in FlyingPress & Perfmatters already excludes above the fold images from lazy load automatically for better LCP. But if you’re using SiteGround Optimizer’s lazy load, you’ll need to exclude above the fold images by CSS classes or media types. It also includes a “skip-lazy” class.

Siteground optimizer skip lazy class

  • Exclude Media Types From Lazy Load – I’m not really sure why things like iframes, videos, and mobile are excluded from lazy load by default. These should be lazy loaded.

Siteground optimizer exclude media types from lazy load 1

  • Maximum Image Width: Off – uploaded images over 2560px will be resized for smaller dimensions. Useful if you have clients who upload huge images and don’t know better. To specify a custom maximum image width, add the code below to your functions.php file.
add_filter( 'sgo_set_max_image_width', 'max_image_width' );
function max_image_width( $max_allowed_width ) {
    // Add the value you want to adjust as max image width.
    $max_allowed_width = 1250;

    return $max_allowed_width;

Lacking Features

  • Lazy load background images: Elementor supports this in the Experiments settings, otherwise use CSS background images in Perfmatters or the lazy-bg helper class in FlyingPress. Optimole can do this by CSS selectors and WP Rocket makes you move background images to inline HTML (first 3 options are easiest).
  • Preload above the fold images: above the fold images should be excluded from lazy load and preloaded. Perfmatters and FlyingPress make it easy by setting a specific number of images that typically load above the fold (usually 2-3). Even if you use another plugin for lazy loading, you can still use both the “preload critical images” + “CSS background images” features in Perfmatters (confirmed w/ Brian).
  • Resize images for mobile: improves mobile LCP/load times and is supported by Cloudflare’s image resizing, Bunny Optimizer, and ShortPixel Adaptive Images.
  • Add missing image dimensions: most speed plugins let you specify image dimensions which can improve your CLS score, but SiteGround Optimizer doesn’t.
  • Replace YouTube iframe w/ preview images: most speed plugins do this too, or use WP YouTube Lyte. FlyingPress is the only plugin I know that can self-host YouTube placeholders which will prevent third-party requests from
  • Replace picture tags for WebP: you can read the support thread on it if you want.


6. Speed Test

Instead of SiteGround’s speed test, use these:

  • KeyCDN’s Performance Test – measures TTFB in 10 global locations instead of only 1 location in PageSpeed Insights. SpeedVitals also tests TTFB in 40 locations [screenshot].
  • WP Hosting Benchmark – measures hosting performance, whether object cache is working, and runs tests related to CPU/memory, filesystem, and database [screenshot].

Siteground optimizer speed test


7. SiteGround Optimizer + FlyingPress

Configure SiteGround Optimizer normally except:

  • Disable file-based caching and browser caching.
  • Use 1 plugin to disable emojis.
  • Use 1 plugin to control Heartbeat.
  • Use 1 plugin to clean your database.
  • Use 1 plugin to minify/defer JavaScript.
  • Use 1 plugin for lazy loading (I recommend FlyingPress).
  • Use 1 plugin to preload fonts.
  • Leave SG’s CSS settings off and use FlyingPress’ CSS settings with remove unused CSS.

Configure FlyingPress normally while taking advantage of these features:

  • Remove unused CSS.
  • Lazy render HTML elements.
  • Preload links.
  • Delay JavaScript.
  • Bloat removal.
  • Optimize Google Fonts to host them locally.
  • Image optimizations (lazy load, add missing dimensions, preload critical images).
  • Lazy load iframes and use placeholder images.


8. SiteGround Optimizer + Perfmatters

Configure SiteGround Optimizer normally except:

  • Keep all 3 caching layers on.
  • Use 1 plugin to disable emojis.
  • Use 1 plugin to control Heartbeat.
  • Use 1 plugin to clean your database.
  • Use 1 plugin for lazy loading (I recommend Perfmatters).
  • Use 1 plugin to defer JavaScript (you can both delay/defer it).
  • Use 1 plugin to preload fonts and prefetch to external domains.
  • Leave SG’s CSS settings off and use “remove unused CSS” in Perfmatters.

Configure Perfmatters normally while taking advantage of these features:

  • General settings (bloat removal, etc).
  • Asset settings (script manager, delay JavaScript, remove unused CSS).
  • Preloading (instant page, preloading CSS/JS files, preloading critical images).
  • Lazy load: images, iframes, add missing dimensions, CSS background images, etc)
  • Fonts (add font-display: swap and use local Google Fonts).
  • CDN settings should be off unless using something like BunnyCDN.
  • Analytics settings should be off since Google Analytics is usually delayed.


9. SiteGround Optimizer + WP Rocket

Configure SiteGround Optimizer normally except:

  • Disable file-based caching and browser caching.
  • Use 1 plugin to disable emojis.
  • Use 1 plugin to control Heartbeat.
  • Use 1 plugin to clean your database.
  • Use 1 plugin to minify/defer JavaScript.
  • Use 1 plugin for lazy loading (I recommend WP Rocket).
  • Use 1 plugin to preload fonts and prefetch to external domains.
  • Leave SG’s CSS settings off and use WP Rocket’s CSS settings with remove unused CSS.

Configure WP Rocket normally while taking advantage of these features:

  • Remove unused CSS.
  • Preload links.
  • Delay JavaScript.
  • Image optimizations (lazy load, add missing dimensions).
  • Lazy load iframes.
  • Leave cache preloading disabled.


10. Cloudflare APO

I recommend Cloudflare’s APO over SiteGround’s CDN.

Regardless of what Hristo says, Cloudflare APO is not the same as SiteGround’s dynamic caching. Cloudflare’s network has 100+ more PoPs than SiteGround’s, so to basically say they’re the same is a lie. They just want you to sign up for their CDN and pay them instead of Cloudflare.

Cloudflare apo siteground optimizer
This is not true (Cloudflare has a larger network and way more speed/security features)

Setting Up Cloudflare APO On SiteGround

  • Sign up for Cloudflare through their website.
  • Change nameservers to the ones Cloudflare assigned you.
  • Change your website from DNS only to proxied in Cloudflare’s DNS settings.
  • Enable minification in SiteGround Optimizer, then disable in Cloudflare.
  • Purchase APO in your Cloudflare account.
  • Disable dynamic caching in SiteGround Optimizer.
  • Install the Cloudflare plugin.
  • Create an API token and add it to the plugin.
  • Purge cache in SiteGround Optimizer, then in Cloudflare.
  • Confirm APO is working using

Test cloudflare apo
CF-Cache-Status: HIT, cf-apo-via: tcache, cf-edge-cache: cache, platform=wordpress.

Another reason not to use SiteGround’s CDN is you have to use their DNS to use it. And if you haven’t read about the Google blocking fiasco, SiteGround’s DNS was blocked by Google for 4 days which they blamed on Amazon/Google, but came out with a “fix” just a few days later. All while their client’s Google rankings plummeted or even got completely deindexed from Google.


SiteGround Optimizer Isn’t Stable

SiteGround Optimizer constantly runs into compatibility issues with Elementor, Divi, WooCommerce, and other themes/plugins.

Instead of fixing them, they like to push the blame on the themes/plugins. Which also means there’s little to no documentation about known compatibility issues. They also don’t thoroughly test updates before releasing them, making the plugin extremely unstable. There, I warned you.

Siteground optimizer denial of compatibility issue

Siteground optimizer third party compatibility issue

Siteground optimizer envira gallery compatibility issue

Siteground optimizer woocommerce compatibility issue

Best performance plugin on siteground

Siteground optimizer theme plugin compatibility issue


Why ChemiCloud + Are Faster/Better Than SiteGround

ChemiCloud uses faster technology like LiteSpeed servers, NVMe SSDs, Redis, and the free LiteSpeed Cache plugin which does a better job with core web vitals. You get more resources (CPU/RAM/inodes) and if your traffic grows, you can scale CPU/RAM with the Turbo Boost add-on. They’re cheaper, have better support (5/5 on TrustPilot), and do free migrations. LiteSpeed hosting with NVMe SSDs + LiteSpeed Cache + Redis + Cloudflare’s APO = faster than SiteGround.


  • LiteSpeed is faster than Apache.
  • LiteSpeed is more CPU/memory efficient.
  • LiteSpeed’s PHP is more efficient than FastCGI.
  • LiteSpeed Cache is faster (and better supported) than SG Optimizer.
  • NVMe SSDs are faster than SATA SSDs, often with 6x faster read/write speeds.
  • MariaDB is more powerful than MySQL (here’s a Facebook poll taken on the two).
  • Redis is more powerful than Memcached, especially for WooCommerce/dynamic sites.
  • Cloudflare has a larger network with more speed/security features than SiteGround’s CDN.
SiteGround GrowBig Cloudways Vultr HF (2GB) NameHero Turbo WordPress ChemiCloud WordPress Turbo Starter Plan
Type Shared Cloud Shared Shared Private cloud
Server Apache + Nginx Apache + Nginx LiteSpeed LiteSpeed Apache + Nginx
Cores/RAM Not listed 1 core + 2GB 3 cores + 3GB 3 cores + 3GB – scalable to 6/6 32 cores + 128GB
Storage (SSDs) 20GB SATA 64GB NVMe Unlimited NVMe 40GB NVMe – 10/11 locations 10GB NVMe
Object cache Memcached Redis Pro Redis Redis (details) Redis
PHP processor FastCGI FPM LiteSpeed LiteSpeed LiteSpeed
Database MySQL MariaDB MariaDB MariaDB MariaDB
CDN $14.99/mo SiteGround CDN $5/mo Cloudflare Enterprise QUIC (but use Cloudflare APO) QUIC (but use Cloudflare APO) Free Cloudflare Enterprise (read)
CDN locations 187 300 83 83 300
Full page caching
Cache plugin SG Optimizer Breeze LiteSpeed Cache LiteSpeed Cache x (use FlyingPress)
Data centers 10 44 US only 11 Served from Cloudflare edge
Control panel Site Tools Can be complex cPanel cPanel Custom (easy)
Email storage 10GB x Unlimited Unlimited x
Incidents History of TTFB + DNS + CPU issues, price increases Acquired by DigitalOcean, price increases 2011 node outage None None
Support C C B A A
Migrations $30/site 1 free + $25/site 1 free 10-200 free Unlimited free
TrustPilot rating 4.8/5 4.6/5 4.7/5 5/5 4.9/5
Monthly price $3.99 $26 $10.97 $5.99 $25
Renewals $24.99/mo $26/mo $19.95/mo $19.95/mo $25/mo
Chemicloud gtmetrix reportWhich web server do you use recommendLitespeed cache litespeed serverLitespeed litespeed cache quic. CloudLitespeed pagespeed scores
Chemicloud trustpilot
People who moved from SiteGround to ChemiCloud
Chemicloud vs sitegroundChemicloud pro feedbackChemicloud speed ui supportSiteground vs chemicloud comparisonWhich web server do you useLitespeed on litespeed serverLitespeed cache vs. Wp rocketDivi litespeed
Rocket. Net trustpilot
People who moved from SiteGround to

I use who averages a 100ms global TTFB. They’re a big reason for my PSI scores (since TTFB is 40% of LCP) and why my site loads instantly no matter where you are. Their free Cloudflare Enterprise is specifically good for international audiences and WooCommerce with full page caching, Argo Smart Routing, and Mirage/Polish for image optimization. This can also mean 3 less plugins since you don’t need CDN/image optimization/security plugins. Compared to SiteGround, they have 8-16x more CPU cores/RAM, NVMe SSDs, Redis/Redis Pro, and no PHP worker limits. Their support is incomparable to SiteGround with unlimited free migrations and $1 your 1st month. The main con is low bandwidth + storage, but if TTFB is important, they’re a major upgrade from SiteGround Cloud + Cloudways + Kinsta + WPE… who all have worse specs.


  • uses NVMe SSDs, Redis, MariaDB.
  • Redis Object Cache Pro is available on higher plans.
  • Cloudflare Enterprise is free and setup automatically.
  • This uses APO, Argo, Mirage/Polish, WAF, other features.
  • No CDN, image optimization, or security plugins are needed.
  • Top performer in Kevin Ohashi’s 2023 WP Hosting Benchmarks.
  • No PHP worker limits (a common restriction with other cloud hosts).
Average ttfb speedvitals
Test your site in SpeedVitals to see average TTFB of 40 locations (run 3 tests to ensure caching/CDN are working)
Siteground to rocket. Net
Other people saw a 500% faster TTFB and 200% faster LCP

Kinsta to rocket. Net migrationSiteground to cloudways to rocket. Net 2Rocket. Net no competitionRocket. Net vs kinstaKinsta to rocket. Net ttfb redisRocket. Net is amazingRocket. Net trustpilot review

Rocket. Net facebook review 1Rocket. Net vs siteground commentSiteground to rocket. Net post 2Moved to rocket. Net vs sitegroundRocket. Net positive reviewBluehost to cloudways to rocket. NetRocket. Net vs cloudways vultr hf trustpilot review

If you search SiteGround’s 13,000+ TrustPilot reviews, you won’t find 1 person who moved from ChemiCloud (same with That’s because most people who think SiteGround is good came from Bluehost, GoDaddy, Hostinger, and even worse hosts. Popular does not mean better.

Final Thoughts

SiteGround Optimizer can quickly turn into a mess or yield bad results if you only stick to SiteGround products. Think twice before using their cache plugin, CDN, and their hosting.

Avoid siteground


You Might Also Like:


  1. Mate, I can’t really tell you how thankful I am. I have been struggling with slow websites for YEARS. Your tutorial was the breakthrough. I use Siteground + Beaver Builder + Wp Astra + Sg Optimiser + Perfmatters with your recommendations.

    I have 95+ now on MOBILE PageSpeed. Whenever you are around Bristol, UK, the first beer is on me! Thank you!

    • Awesome! Yeah, SiteGround Optimizer alone isn’t enough.

      I would take you up on that beer. Leaving SiteGround works too ;)


Leave a Comment