grevillea859

Thank you for your prompt replies and reassuring not from your plugin and not from overdue cron jobs. Yes I have also seen reports of various commands out of sync errors (but different to those above) while searching for possible solutions. Everything seems to be working alright otherwise.

Thank you for raising the options table issue. The LS Database Summary shows my Autoload size is 314.78K with 753 Autoload entries, which was the case before the above errors occurred. Recently I reduced the size and number of entries following a warning in SiteHealth. But still got the Commands out of sync errors anyway.

Thank you both for your time. I will close the ticket for the time being until further information sheds light on the problem.

Thank you for the fast response. I have now setup cron jobs in cPanel. Hopefully that resolves it and this closes the ticket.

Hi @bsfherman,

I have been trying to fix the above issues with but can’t see what the problem is. I have been looking into causes of CLS and saw that it can also be caused by async loading of CSS.

CSS stylesheets on my site are delayed. I don’t understand any of this, it seems all hit and miss. However when I excluded the /wp-content/themes/astra/assets/css/minified/style.min.css stylesheet from delay, the CLS reported above disappeared on mobile and desktop views (and reduced the render blocking) on Google PSI.

While that issue is fixed I now have some unused CSS although not much. Fix one thing and another pops up. As far as the CLS is concerned I will now close this ticket, thank you.

Hi @bsfherman,

Thank you for your fast reply. There were no layout shifts or non-composited animations on the roll-back to the previous version.

Returning to the latest update there is on mobile:

• one layout shift: <div class=”wp-block-columns is-layout-flex wp-container-core-columns-is-layout-1 wp-b…”> and
• Two animations that are not composited as before, the unsupported CSS Property: color for a block cover text and the unsupported CSS Property: flex-grow for the top search bar.

On the desk top version there are 12 layout shifts, all to do with the search box button. The other layout shift is the whole block: <div class=”wp-block-columns is-layout-flex wp-container-core-columns-is-layout-1 wp-b…”>. It makes no sense as I have not seen these before.

Also on the desk top view as for mobile there are the two non-composited animations as above.

Any ideas, suggestions on fixing these would be greatly appreciated. I cannot see what to do, and have no idea what flex-grow means or “color” in terms of fixing the problem.

Thank you for your time and I look forward to your response.

Hi @rsouzaam,

Thanks so much for replying, for your attempts to reproduce the problem, helpful advice and links. Thank you for mentioning that about optimization plugins re-ordering scripts, it hadn’t occurred to me but now makes sense.

Thank you also for testing the form – it is great to know that it works! I have not had issues submitting the form with the alerts present but seeing them made me wonder if something was amiss all the same. Thank you for providing the code snippet, much appreciated. I have now added it to my functions.php file in my child theme and the alerts have gone. And the form works!

I was able to fix an aspect of the security plugin which was causing the 403 forbidden errors. The wpforms scripts above I have delayed and that seemed to clear up the blocking effect.

So everything is working fine now, many thanks for your time and prompt replies – and this closes this ticket.

Hi @rsouzaam,

Thank you for replying.

As well as LiteSpeed Cache I have an optimizing plugin: Perfmatters. When I removed some js scripts from being deferred the WP Forms message disappeared so now have resolved that.

But the 403 forbidden and blocking alerts remained. It seems there is a conflict with a security plugin is involved and I am looking at that.

However all of the scripts above are render-blocking which I used to do with defer. How can stop these from blocking the render?

Thank you

Hi @erania-pinnera and @lerrtle

My apologies, I have recently upgraded my site to more memory and dealing with some issues (not Jetpack) with that.

At the moment it is looking alright. I will get back in touch if I need help.

Thank you again for your time.

Hi @rsouzaam,

Thank you for replying. I am sorry you were blocked. I must have inadvertently blocked your ip or something and will need to look into that.

Thank for providing helpful links. I have followed those instructions and cleared the cache but still get the same message.

When I ran a Google Page Speed test I got these messages logged to the console for each of the 6 urls below: “failed to load resource, the server responded with a 403 forbidden error”.

/wpforms-lite/assets/js/frontend/wpforms.min.js?ver=1.8.9.2
/wpforms-lite/assets/lib/mailcheck.min.js?ver=1.1.2
/wpforms-lite/assets/lib/punycode.min.js?ver=1.0.0
/wpforms-lite/assets/js/frontend/wpforms-modern.min.js?ver=1.8.9.2
/wpforms-lite/assets/lib/jquery.validate.min.js?ver=1.20.0
/wpforms-lite/assets/js/share/utils.min.js?ver=1.8.9.2

In addition for each url above I saw this:

“Refused to execute script from ‘mysite/wp-content/plugins/wpforms-lite/assets/js/frontend/wpforms-modern.min.js?ver=1.8.9.2’ because its MIME type (‘text/html’) is not executable, and strict MIME type checking is enabled.”

I have no idea what the above means. But before sending screenshots I was thinking these might be an issue for my host, at server level? Whether the above urls need to be whitelisted?

I look forward to your comments,

Thank you again.

Hi (@lerrtle),

Thank you for replying. I am a bit confused as to what is happening.

Connections to the server seem variable. For example Site Health reports everything is good, connecting to the REST API then other times not when there are 50 or so cron jobs overdue.

I am not sure how to check that JSON API authentication is disabled? I understand that running https://example.com/wp-json/wp/v2 in the browser can reveal whether JSON API is working or not.

I disabled Jetpack and saw that I am now getting similar errors indicating a timing issue?

WordPress database error Commands out of sync; you can’t run this command now for query SELECT option_value FROM wp_options WHERE option_name = ‘action_scheduler_lock_async-request-runner’ made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_OptionLock->set, ActionScheduler_OptionLock->get_existing_lock

Today I tried to reinstall WordPress but it timed out. I have been experiencing 503 server errors and my host has advised I should upgrade to more memory. I am reaching the limits of my I/O usage when I have Jetpack running and another plugin which also relies on REST API. When I disable them the usage falls.

Since posting my ticket and issues since I will upgrade as advised and hope that resolves things, if not I will be back!

Thank you for your time.

Hi @macmanx,

Thank you for your prompt reply, most appreciated.

I couldn’t see any missing white space or lines in the offending line above. However from the linked information you provided I did find a number of blank lines near the top of wp.config.php. I deleted them and hope that resolves it.

Hello James,

Thank you so much for your prompt reply and all those suggestions, very helpful. Greatly appreciated when trying to work with server admin as a novice!

Kind regards

So I presume at the end of the line there shouldn’t be any unused, render-blocking CSS. I will wait for that to occur and now will close this thread. Thank you for your time.

Hi, what is a reasonable time for UCSS regeneration?

PSI still reports 3 Critical Request Chains from litespeed CSS to avoid:

/litespeed/css/62332fd….css?ver=4dc3d, /litespeed/css/cf3350c…css?ver=90249 and /litespeed/css/e196a50…css?ver=5a9f8

And 3 long chain main thread tasks, one from litespeed /js/….js?ver=60afc and 2 from my domain.

How do I avoid these? What settings should I use in litespeed cache?

I sent another report, 08/29/2023 22:31:11, Report number: CNSIAJEF.

Thank you.

Okay thanks. With UCSS I have warning to avoid 3 critical requests from being chained:

https://willshub.com.au/wp-content/litespeed/css/e196a50b6dcf48b44634d1dd55480129.css?ver=5a9f8

https://willshub.com.au/wp-content/litespeed/css/62332fde8439807b45ec05c02b15676d.css?ver=4dc3d

https://willshub.com.au/wp-content/litespeed/css/cf3350c383a0b3851307feaea037f8c5.css?ver=90249

How do I fix that?

On running pagespeed insights again I find the tested pages are failing Core Web Vitals Assessment, and turned off UCSS.