Fred

More likely it is related to Lazyload or avoid mixed content feature. What is the URL of your site? However, if it is a merge issue, you′ll need to find the conflicting file(s) and exclude those from combining.

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,
because we do not opt for a safe standard configuration for our users.

Sounds like a theme/plugin conflict. This guide may useful.

Hi,

Most likely Merge Scripts/Styles causes your issue. Disable Merge and see if that solve your issue.

I’m sorry to hear about you encountered issues while using our plugin. Did you report back that your issue still wasn`t solved? Without provide us with a ticket number, I am not able to check what exactly happened. Anyway, For pro version support please open a support ticket at https://swiftperformance.io/my-account/support/
Our support team is waiting to support you!

Hi,

We take our client support tickets seriously, however support for Swift Lite is limited.

That said, I can’t find any support thread from you here. Did you contact Swift Performance support directly? If so, what’s your ticket number so I may take a look into it?

Most likely this is due to a plugin conflict or lack of resources. I noticed that your site is cached by Swift.

You may go to settings and proceed configuring the plugin manually.

Hi luis,

Look at the source of a page (at the end), eg
view-source:https://pecas-moto.agracing.pt/

or check header through browser console, developer tools, network tab.

Currently your (home)page isn`t cached at all, so Pagespeed test is useles. Most likely there is another cache layer active which prevent Swift from cache pages.

Our website is currently under maintenance. Below the article:

The average size of a cached page should be about 200-400Kb. That means if you have 1.000 pages the normal cache size will be about 200-400 Mb.
This usually happens if there are a very large number of pages or if there is a dynamic part in JS or CSS – some themes/plugins creates dynamic js and that is why the folder is filled up.

Be sure to manually remove the entire contents of the cache folder and do the following steps:
a) enable separate CSS (styles) and separate JS (Scripts) in Optimization settings:
Settings > Optimization > Scripts: Separate Scripts
Settings > Optimization > Styles: Separate Styles

b) exclude unnecessary post types: autoconfig should find most and exclude them automatically but you can add them manually: Settings > Caching > Exceptions> Exclude Post Types

Afterwards rebuild the cache and see if the problem is solved.
If you still don’t have enough space for this you should maybe consider to exclude some pages from cache, or upgrade to a larger hosting package.

It means that server ran out of memory. Probably you need more RAM.

Hey there,
Since this topic has been inactive for a while, I’m going to go ahead and mark as resolved. Don’t hesitate to reopen or create a new topic if you still need help!
Thanks for understanding!.

Hey there,
Since this topic has been inactive for a while, I’m going to go ahead and mark as resolved. Don’t hesitate to reopen or create a new topic if you still need help!
Thanks for understanding!.

To avoid misunderstanding, support for Swift Lite is limited. Configuration is not included.

Most likely you need to disable cache enabler by KeyCDN and let Swift cache pages. If you prefer optimizing assets done by Autoptimize, then you should disable Merge Scripts and Styles in Swift Settings. Make sure not to use same features with multiple plugins because it leads to conflicts and errors.

Hey there,
Since this topic has been inactive for a while, I’m going to go ahead and mark as resolved. Don’t hesitate to reopen or create a new topic if you still need help!
Thanks for understanding!.

Hey there,
Since this topic has been inactive for a while, I’m going to go ahead and mark as resolved. Don’t hesitate to reopen or create a new topic if you still need help!
Thanks for understanding!.