usrobotx
Forum Replies Created
-
This is the different error, suggesting the link anchor to be descriptive text instead of “Click here” or “Learn More”. This is on home page and about page only. The error that I want to fix happens only when LSCWP enabled, and on every page, as the error seems coming from the logo image in the header.
Can I do something now or there is still some process going on?
Forum: Plugins
In reply to: [LiteSpeed Cache] Problem – Browser errors were logged to the consoleYep, paradoxical. I agree with you, UX is more important then rankings, but on my case – my site is really tiny, its speed improvements can improve like <0.1 seconds, and on the other hand better ratings mean better ranking. Between these two I have to go for optimizations.
The only thing that I am not sure is wheter 97 speed (and 92 SEO and Best Practices) is better or whetever another caching platform will lead to (I think 90+ and 100 both SEO and BP)
I just tested another one. Currently it is disabled.
Forum: Plugins
In reply to: [LiteSpeed Cache] Problem – Browser errors were logged to the consoleEverything I do, I do for ranking 😀
At this moment I do not know which to choose – LiteSpeed with “SEO Score 98” and Best Practices Score “92”, but with performance “97+” or other caching plugin, which most probably will have SEO and Best practices 100, but I do not know what will be the performance.
Forum: Plugins
In reply to: [LiteSpeed Cache] Problem – Browser errors were logged to the consoleI see. Thank you very much for your detailed explanation. It seems a tough choice for a perfectionist person.
Forum: Plugins
In reply to: [LiteSpeed Cache] Problem – Browser errors were logged to the consoleOk, I see. At this point I will not be able to sort it out, I have just finished building the website and I want to launch it and then get back to further improvements. Unfortunately, CDN and changing the hosting do not seem as an options for me at this moment.
As I understand, I have two options – either go on using LiteSpeed Cache (With great results), but knowing the errors it causes OR findind some other caching plugin that may not requried LiteSpeed web server (that my hosting does not support).
Forum: Plugins
In reply to: [LiteSpeed Cache] Problem – Browser errors were logged to the consoleSo if I configure quic.cloud, I will not need to change hosting, and my problem will be solved?
Forum: Plugins
In reply to: [LiteSpeed Cache] Problem – Browser errors were logged to the consoleHello,
I googled a little bit, and I think now I understood. Bluehost has not enabpled LiteSpeed (At least for common, shared hosting that I am using).
Thus, if I cannot disable a specific component of the cache causing the issue, I have to either
- Stay with “LiteSpeed Cache” (Which I like very much) – but have that specific error, or
- Stay with “LiteSpeed Cache”, but with caching disabled (it will not be like the performance that I liked), or
- Move to another hosting, with support of LiteSpeed web server, or
- Choose another caching plugin.
Forum: Plugins
In reply to: [LiteSpeed Cache] Problem – Browser errors were logged to the consoleIf I undestood correctly:
- This problem happens because I am using bluehost hosting, and it has not enabled LiteSpeed.
- If I move to another hosting (Quite an effort for me from the technical standpoint) – the site will become much faster, and the problem of 404 will be solved.
- If I stay on the bluehost, I can disable a specific cache, so that all other performance improvements remain, only the one with 404 error will not be working (thus not causing problems).
Am I right? Especially with the third point?
If yes – which cache should I disable, in order to keep all other performance improvements and just solving 404?
I have deactivated it.
Ok. Waitig for further instructions.
We are also discussing another issue on another topic. If there is no need to have an active plugin (for that topic). I will disable it.
Forum: Plugins
In reply to: [LiteSpeed Cache] Problem – Browser errors were logged to the consoleIf you check any page with google lighthouse, you’ll see that Best Practices shows score of 92, because of 2 problems. Screen attached. https://imgur.com/gkKyoOW
That’s the issue that I want to solve. This issue was not there before activating plugin.