Fred

Start with (and check each time if that solve your issue after clearing cache).
1.disabling Normalize Static Resources
2 disabling merge Scripts
3 disabling merge Styles
4.disable Lazyload images

also, did you set Auto Purge for Cloudflare in CDN tab?

Can you provide the page URL where this is happening? Which widget doesn′t load?

@roofer1982 Please open a new thread for (every) new issue.
@wilhelm-ahrendt did you disable Normalize Static Resources?

Checking your site, it currently isn`t cached by Swift.
Did you check your site in private browser? If you disable Normalize Static Resources does that make any difference?

Probably this is caused by an improper order of htaccess rules or forced www/non-www rule in htaccess. Please remove these rules from .htaccess, and insert them in Settings > General > Tweaks > Custom .htaccess.

example you migh use: (don`t forget to change example.com with your site domain).

# Redirect non-www to (ssl) www
RewriteEngine On
RewriteCond %{HTTP_HOST} ^example\.com [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301]
# Redirect non-SSL to SSL
RewriteCond %{HTTPS} !on
RewriteCond %{SERVER_PORT} !^443$
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]

The old folders you may remove manually.

Swift cache will be cleared when:
– a post/page was modified
– a post/page was deleted/moved to trash

Are you sure there is no other cache layer active, such as Varnish?
If you enable Development Mode in Cloudflare, does that make any difference?

Thank you for your review. I’m sorry to hear about you encountered issues while using our plugin!

We take our client support tickets seriously, so please provide us your ticket number where we have treated you unfairly.You may also open a support ticket here
https://swiftperformance.io/my-account/support/
and I’ll look at it immediately.

In general, it is possible that your issue was related to hosting, wether you like it or not. Swift is using more aggressive optimization/preload functions than any other plugin on the market. That makes it better and faster, but can occasionally lead to some issues as there are so many unique server and WordPress environments running….

In my personal opinion It is odd to rate our plugin with just 2 stars, when using it on 30 sites.

If you really want to get pro version, you should go for it as it comes with non questionable 14 days refund policy. With Pro version you have unlimited access to our support desk and one year of free updates. Lite support is limited as WP forum rules don`t allow us to ask for login credentials.

Is wp-cron disabled? Can you provide also one URL of a site which is experiencing this issue.

Fastest solution, Cache pages on first visit, so second visitor get served cached pages.This is how most cache plugins work.
To achieve this:
– disable Prebuild Cache Automatically in Settings->Caching->Warmup
– enable Optimize in Background in Settings->Optimization->General

Regarding prebuild, you should check if there is any other cache layer active and if wp-cron isn`t disabled.

The correct link is
https://swiftperformance.io/documentation/how-to-check-for-plugin-conflicts/

there’s not a fixed set of options that should be activated on every website.
Every site is different, and even if they might have Divi in common, several factors can influence the choice of the best Swift Performance settings. If you disable
Normalize Static Resources, does that fix the issue?

is .htaccess writable? Is there any error in Debug Log?

Did you clear cache in Swift? What is the URL of your site?

I′m affraid you have set some incorrect rules in Plugin Organizer, which causes this issue. The only solution is to search for swift_performance_plugin_organizer in wp_options of your database and delete the content.

After that you may reinstall Swift.

WARNING: Enabling or disabling plugins can have catastrophic affects on your site. It can cause issues with plugins and can render your site inaccessible. Make sure you know what you are doing and always make a backup of your database before making any changes!

You might try if reinstalling Swift fix your issue.