Mobile Usability issues with Litespeed guest mode

@habeebcom

As @qtwrk has said, please try go to page optm -> tuning -> UCSS URI Excludes , add?/?into the list , purge all and purge UCSS

Please go to litespeed plugin page optimisation tab. Last one is tunning. In tunning find UCSS URI Exludes. In this box type just type / and save the changes. After that press Purge all button and then Purge UCSS button. This method really works. My problem got solved with this method.

Thanks

Thank you very much for your feedback..
I will try to follow the same steps you did
I hope things go well

Thank you again
all love for you

Hello again gulatisanjeev2
I tried the same steps..
I’ve read something about this in the support documentation
But there is one thing I don’t quite understand…

In your comment you mentioned an important sentence (look for UCSS URI exceptions)
And it seems that it is the culprit and the cause of the problems .. and therefore it should be excluded from the optimization when activating the guest mode .. (or at least that is what I understood) ..
Well.. but I also wonder.. how do I search for the culprits? And where do I find them exactly?
Do I search for it, for example, through the developer tools in Google Chrome??
Can you explain me more…

With sincere thanks for your wonderful person

@habeebcom

Your cache plugin configuration seems to have mismatched settings. The first thing you notice is that your home page’s cache has been declassified as “private”. This gives each visitors their own private cache and means the home page is almost never cached. From my point of view, you have made settings without knowing what effects these settings have. I can therefore only strongly recommend that you set all settings to default and use one of the presets. Please don’t choose the aggressive mode, but start with the recommended mode. It is also important that you purge the quic.cloud cache, as it appears to have an outdated cache status.

Hello.. I apologize for any inconvenience..

As you said .. I chose the default mode, and I never went for the strong and violent modes..
I tried to try the basic first settings.. but it is of no use to improve the speed of the site..

The default mode is to choose the guest mode automatically..and this causes the problem to appear, and as soon as you press the button to disable the guest mode, Google warnings are fulfilled and the pages become mobile-friendly..

The thing that caught my attention is that when you turn off guest mode, or deactivate the entire plugin..the result is the same..
As if the entire plugin is based on this task only..

But in conclusion…
Do I understand from your previous response .. that things are going well for you .. just because you set the plug-in to default mode only .. and you did not perform any other action inside the box (UCSS URI Excludes)

If @qtwrk suggests using UCSS URI excludes, then that’s generally a good recommendation, but with caveats. The problem with page optimization is that there is an unlimited number of different theme constellations. No theme is like the other. The same applies to the installed plugins. A page optimization function can only try, I repeat try, to fix the bugs of a badly programmed theme and the consequences of too many plugins. This succeeds in 9 out of 10 cases, but not in all cases. However, this does not mean that the cache plugin is insufficient or that it is not possible to achieve the desired optimization. In case of doubt, this means that you have to make individual settings, which differ from case to case. But an expert needs to take the time to do this. However, the plugin support cannot afford this individual effort. In order to help you anyway, he gave you this recommendation, because it helps in most cases. However, this recommendation is equivalent to deactivating the guest mode, because the actual advantages of the guest mode are significantly reduced. This recommendation can also cause new problems to arise as a result.

I am aware that the many words do not give you any real help. I just want to make you aware that the best possible optimization cannot always be achieved. But you have to be aware that the cache plugin is not the problem, but a badly programmed theme and possibly too many installed plugins are the cause of your problem. If the best possible optimization cannot be achieved, then this inevitably means that you cannot use all of the plugin’s features. And in case you don’t know, no feature of the cache plugin makes any promise that this feature can work on all themes.

Hi..
I highly appreciate all your words..and understand them very well..
Indeed, there may be many overlaps already.
It is likely that the theme I using could be a big part of the problem… if not all of it.
I’ll try to fix some issues when I get the time..

I’ve already exhausted you with me.. to the point that I feel ashamed..
You are beautiful and wonderful, my friend
See you soon

@habeebcom

You do not have to be ashamed. The LScache plugin and every other plugin for page optimization is both a blessing and a curse. Personally, I see the original problem with WordPress because it fools every user into thinking that running a blog is child’s play. Writing content yes, but not according to the criteria for the best possible optimization of a page. It is made too easy for you inexperienced users. Regardless of whether it is a new theme or another plugin, in most cases only 1 click is enough and that is catchy, because neither a theme developer nor a plugin programmer gives much thought to doing his work according to the criteria of good page optimization . And an optimization plugin should then correct these errors again?! Feel free to criticize, but don’t complain to LiteSpeed, but to the creator of your theme or the installed plugins.

Yes, definitely ..
Every letter you write is highly appreciated by me.
Thank you for your elegant spirit, And your patience, too
You are great

I have exactly the same problem. It took me weeks before I could pin down the problem and find that it it Litespeed guets mode that is causing Pagespeed to give an error on mobile. Also mobile compatibility fails in Google when guest mode is active. When I disable Guest mode the site is mobile friendly again and pagespeed does not give “unknown error” anymore.
However: there must be a secondary element that causes this. I run another website which has guest mode ON and this problem does not appear at all.

Has a cause or solution been found?

hi! I have exactly the same issue. If guest mode + Guest Mode Optimisations are enabled , i get this error in Google speed test:

Oops! Something went wrong.

generic::internal: APP::1: Abnormal renderer termination, status = crashed exit_code = 1

any thoughts? No errors in console. Cant figure out what can cause it. And i am a very experienced WP developer.

I have exactly the same problem. It took me weeks before I could pin down the problem and find that it it Litespeed guets mode that is causing Pagespeed to give an error on mobile. Also mobile compatibility fails in Google when guest mode is active. When I disable Guest mode the site is mobile friendly again and pagespeed does not give “unknown error” anymore.

Me too. It took me ages to pin down the culprit. I now run my website without the guest mode since I really need to work on other things but my site is not performing well without the guest mode :(. My pagespeed score dropped from 95 to 70.

Help from the developers would be appreciated, this issue affects multitude of people.

@rblrblrbl,

This solution disable rendering the mobile menu which has no CSS due to async CSS loading.

Try this: Page Optimisation -> Tuning CSS. Paste a CSS code into Critical CSS Rules box. I use this with Astra theme:

@media only screen and (max-width:1149px){
#ast-mobile-header .content-align-flex-start {
  display: none;
}
}

This CSS will loaded first while other CSS loading async. Use your CSS selector for your page.

All of my page is good regarding to Google Seach Console.

Best regards,
Estalhun

Hi @estalhun, I will try out your suggestion – thanks for the help!