Fred

We’re not able to reproduce this from our side, so maybe it’s a third party plugin issue? Either way, contact us over at our support center ([email protected]) and one of our technicians can experience this first-hand for your site and help to figure out why this is happening for your installation.

Backend or frontend? Anyway, when you disable merge Styles, does that solve your issue?

Please provide site URL and also the page where this issue occurs.
Also, how did you exactly exclude that page?

For pro version support please contact us directly and open a support ticket at https://swiftperformance.io/my-account/support/. This includes any feature questions as well. Thanks.

It looks like those POST requests get cached by Swift.
Check if following features are disabled.
– Dynamic Caching
– Discover New Pages
– Ignore Query String

and make sure that you enable
– Optimize Prebuild Only

Hope it helps.

For cookies you can use the swift_performance_is_cacheable filter, but it needs some custom code or you may upgrade to pro version, which contain an easy way to exclude cookies from caching.

Sorry, that feature is only available in Pro version of Swift Performance plugin.

I see. Try disabling merge Scripts.

As you say, maybe I misunderstood your question, but with the kind of accusations you end up with, it is not really motivating to support you further here.

If you disable Merge Styles in Settings->Optimization->Styles, deos that solve your issue?

In order to use Geolocation in combination with Swift Performance Lite, you need to enable additional geocaching option in Woocomerce settings or upgrade to Pro version of Swift, which contain Ajaxify feature for Woocommerce.

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

No, not yet.
Implementing Native Lazy Loading is too early. There are currently too many issues.

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.

Yes, If you want to keep merge Scripts enabled, you′ll need to find the conflicting file(s) and exclude those from combining.

So you have to learn what elements to exclude. Merge can break certain things because the mechanism doesn’t always load them in the exact perfect order. You would have this problem with other merge plugins as well.