Fred

Did you check your site in private browser? If you disable Normalize Static Resources in Settings-General-Tweaks, does that make any difference?

It might be a false warning. Sometimes Swift is unable to read timeout, but if the caching is working, you can simply ignore it.

In general, timeout shows how long can PHP run on your server. Ideal is about 300s, however even if you have shorter time usually it won’t cause any issues, only the prebuild process can be a bit slower.

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?

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

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.

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.

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.

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?