Search results

Don't let users believe a "simple script" can warmup the LScache. TTL for CF cache is only 1 week and only available to the node that is next to user location. CF has ~ 165 nodes, so have fun with trying to warmup. The same with quic.cloud, but TTL is only 24h.

Is Google PageSpeed Just an Illusion? For nearly 20 years, the industry has treated Google PageSpeed as a proxy for "website speed". Agencies sell it. Clients demand it. Developers optimize for it. But here’s a simple question: Does PageSpeed actually measure speed? The real speed, not...

How to really Fix "Reduce Unused JavaScript" in WordPress: A Deep Dive into Asset Management Introduction: The Persistence of the PageSpeed PSI Warning One of the most frustrating warnings in Google PageSpeed Insights (PSI) is "Reduce Unused JavaScript." Even after installing top-tier caching...

WordPress multisite is unsupported

Did you know that every WooCommerce store loses money in the checkout? No? Or maybe you suspect it — but you can’t quite prove it? Then keep reading. Especially if you’re using LiteSpeed and an optimization plugin. The checkout is the most sensitive moment in the entire sales process. This is...

WordPress Optimization promises speed. - Minification. - Script deferral. - Lazy loading. - Asset reordering. But what if none of that reduces the actual workload of your system? This video explains why most “optimization” in WordPress does not eliminate execution — it only restructures...

LiteCache Rush has been released and is ready for testing. If you are ready to start the Rush Speed Engine then take a tour. But be warned. The Rush Speed Engine Tour is not for the faint of heart. Accessing the linked page below is at your own risk! https://www.cachecrawler.com/Rush:::45.html

The request method doesn't matter. The fact is, however, that only 1 _lscache vary cookie with the correct hash is now being set, and this was only possible by deactivating and reactivating guest mode at least once. I'm sorry I could help you....

"Not free" means that you cannot expect to receive knowledge that others have invested a lot of time in acquiring. The only important thing regarding your actual problem is that it was solved after you followed my advice.

Cookie yes, but not session cookie. It's the _lscache _vary cookie that has a unique value for each WP installation. OLS and the cache plugin are open source, but not everything is free. If you don't know how LScache works and which parameter is needed for which function you don't know what...

FYI: https://www.cachecrawler.com/Blog/LiteSpeed-Guestmode-An-Optimization-Feature-That-Misleads-WordPress-Users::6589.html

There are no fixed parameters as it depends on plugin settings. As long as you have guest mode enabled, curl won't work correctly.

You should read what I have previously posted.

@Majorlabel 1. Do not use curl without additional parameters to verify if caching works. This is especially true as you have the Guestmode fetaure enabled that needs Javascript enabled to set the _lscache_vary Cookie for the Guestmode. 2. Disable the Guestmode feature for time being as this...

@neikoloves I've created a special FAQ for you so you can get an idea of what LiteCache Rush is and what it's good for. If you have any further questions, please be patient for a few more days until Rush is available. What is Rush? Rush is a plugin-loading controller for WordPress. It does not...

Open your mind. ;) The internet provides other indicators to distinguish between good and bad guys. Using IP addresses for filtering is not only insecure, but actually outdated.

LiteCache is a registered trademark, and most LiteCache solutions are either based on or designed exclusively for LiteSpeed. LiteCache for Enterprise CMS is a replacement for LiteSpeed LiteMage.

It's not a question of trust. You're trying to protect yourself, and that's fine, but the method you're using to protect yourself is wrong. If you want to stick with this method, then by all means, continue to feel safe. But be aware that server security isn't based on outdated client-side...

I wish you the best of luck in your search for alternatives. However, you probably won't have any luck, because the WordPress community still hasn't grasped the root cause of the problem. So don't waste any more time, disable ESET and learn how to truly solve WordPress performance issues.

While concealing your identity through various means might enhance your safety, it also increases the risk of being identified as a "bad guy" and consequently blocked incorrectly. Traditional methods may work to disguise your identity, but they rely on flawed and outdated criteria. ESET is good...