Svetoslav Vasev

Hello @1prosopo ,

You can easily exclude JS scripts from js.prosopo.io from being combined by adding this filter into the functions.php script of the site’s theme:
add_filter( 'sgo_javascript_combine_excluded_external_paths', 'js_combine_exclude_external_script' );
function js_combine_exclude_external_script( $exclude_list ) {
$exclude_list[] = 'js.prosopo.io';
return $exclude_list;
}
You can alternatively insert the filter via any plugin that provides custom code insertion.

If you’re a SiteGround client, please submit a support request via our Help Desk if we can be of any further assistance.

Best Regards,

Svetoslav Vasev

Hello @incoog ,

You can try excluding the external JS script from being combined by using the following filter:
add_filter( 'sgo_javascript_combine_excluded_external_paths', 'js_combine_exclude_external_script' );
function js_combine_exclude_external_script( $exclude_list ) {
$exclude_list[] = 'script-host.com';
$exclude_list[] = 'script-host-2.com';
return $exclude_list;
}
In your case, the filter should look like this:
add_filter( 'sgo_javascript_combine_excluded_external_paths', 'js_combine_exclude_external_script' );
function js_combine_exclude_external_script( $exclude_list ) {
$exclude_list[] = 'js.klarna.com';
return $exclude_list;
}
In case this solution doesn’t yield the expected result, please submit a support inquiry via your SiteGround account and we’ll gladly review the matter further.

Best Regards,

Svetoslav Vasev

Hello @warrensamu ,

The WebP conversion feature of the Speed Optimizer creates .webp copies of the images in your Media Library, without affecting the original images. The image paths stay the same and, whenever suitable, the WebP versions of the images are served to the visitor, instead of their non-WebP variants.

If the conversion process has become stuck, you can try forcing the WebP conversion cron by connecting via SSH to your site and running the following command inside the public_html folder:
wp cron event schedule siteground_optimizer_start_webp_conversion_cron now
Of course, please feel free to contact us by submitting a support inquiry from your SiteGround account and we’ll review the issue further.

Best Regards,

Svetoslav Vasev

@titowhisky ,

I’d like to thank you for taking the time to investigate this problem and we’ll gladly bring the case to the attention of the plugin’s developers. However, for this purpose, we’ll need to replicate the problem first and gather enough information which can be used for further troubleshooting.

During my troubleshooting, I made sure to check both the PHP error log inside the public_html folder and the one inside the wp-admin folder as well. None of them recorded any of the errors/messages that you reported in this thread.

In order for us to proceed with debugging the problem in more detail, please log into your SiteGround account and submit an inquiry via our Help Desk.

Best Regards,

Svetoslav Vasev

Hello @titowhisky ,

I have attempted to replicate the problem on a fresh WordPress application with the only active plugins being the latest versions of the Speed Optimizer and WooCommerce. However, none of the reported errors were logged into the application’s PHP error log. This leads me to believe that the errors are most likely related to a custom setting on your site or another plugin/theme.

In order for us to the review the reported problem further, please submit a support inquiry in our Help Desk from your SiteGround account.

Best Regards,

Svetoslav Vasev

Hello @gagnieray ,

Thank you for the detailed information. It has already been passed to the plugin developers and a fix is expected to be released with the next plugin update.

You can follow the plugin’s?updates and changelog?for any development regarding this case.

Best Regards,

Svetoslav Vasev

Hello @screenup ,

The issue has been brought to the attention of the plugin’s developers and a fix is expected to be deployed in the next plugin update. You can follow the plugin’s changelog here.

If you need additional assistance or the issue continues to persist after the fix is released, please get in touch with our support team from your Help Desk if you are a SiteGround client and we will review the matter further.

Kind Regards,

Svetoslav Vasev

Hello @dominique_delcourt_com ,

The warning you’ve encountered – Cannot modify header information – can be suppressed in most cases by setting the value of the PHP variable output_buffering to 1.

If you are a SiteGround customer, please contact us by?posting a ticket request?and we will assist you further in case the warning persists after enabling the PHP output buffering.

Kind Regards,

Svetoslav Vasev

The various plugins that allow you to link a WordPress site to Google Analytics don’t generally use cookies, but rather rely on Google Tags to track the analytical data for the site. Nonetheless, it’s possible that some of these plugins offer other features that do utilize cookies.

However, you’re correct in your assessment that the Dynamic Cache won’t work on sites/pages that use cookies. Caching such pages might lead to security and functionality issues, which is why the Dynamic Cache doesn’t cache such pages by default.

Best Regards,
Svetoslav Vasev

Hello @azzam9396,

The File-based cache depends on the Dynamic Cache to be activated and working. Since the Dynamic Cache itself is not caching the site, the File-based cache is also not creating the static HTML files.

The value of the header “x-proxy-cache: BYPASS” and the following header – “cache-control: no-cache, must-revalidate, max-age=0, no-store, private” – indicate that the site most likely has a cookie on its pages. Pages containing cookies are not suitable for caching, since they contain sensitive data, that is unique to each visitor. As such, these pages are automatically excluded from the Dynamic Cache.

The slight decrease in the Google PageSpeed Insights score can be attributed to the plugin adding some overhead to the site’s total loading time, without effectively caching it. Once the Dynamic Cache (and the File-based cache) are configured to work correctly, the score (which is already quite high) should at the very least be preserved or improved.

For the specific issues you’re experiencing, we recommend submitting a support request through your SiteGround account. Our Technical Support team will be able to review your case and provide further information and assistance.

Best Regards,
Svetoslav Vasev