Search results

  1. LiteCache

    AI crawlers vs WordPress/OLS – real server impact vs missing return

    I came across an interesting pattern while analyzing traffic on several WordPress setups behind OLS. AI crawlers don’t behave like normal users: - they rarely hit warm cache - they trigger full PHP + plugin stack - they generate real CPU/load At the same time, unlike traditional search...
  2. LiteCache

    OpenLiteSpeed 1.8.4 / Wordpress Performance

    You should check this: https://www.cachecrawler.com/Rush:::45.html
  3. LiteCache

    Are Thousands of WordPress Users Being Misled by PageSpeed on Performance?

    This post is not against optimization itself. It is against a false understanding of optimization. More specifically, against the idea that classical WordPress optimization can improve actual loading time where the delay is really created. I consider Google PageSpeed the main pacemaker of that...
  4. LiteCache

    Custom error codes and access logging

    Congratulations! Sue LiteSpeed for violating the RFC! ;)
  5. LiteCache

    Custom error codes and access logging

    That's a given, but don't try to apply your "personal logic" to how something should work.
  6. LiteCache

    Custom error codes and access logging

    I appreciate your efforts to block scrapers and other unwanted requests. However, be aware that this isn't possible with conventional methods. The challenge lies in identifying these unwanted requests, but you only have known HTTP parameters at your disposal, which are very easy to mask. So...
  7. LiteCache

    Custom error codes and access logging

    LSE = LSWS (LiteSpeed Enterprise Web Server) also follows RFC, but you should use LSWS support for related questions or issue. The behaviour is different. https://www.litespeedtech.com/support/forum/
  8. LiteCache

    Custom error codes and access logging

    OLS is not Apache. If OLS doesn't use status code 500 if a status code outside the valid range is used this is just an undefined case in OLS. You can complain about this, but before you do, you should first familiarize yourself with RFC. btw. Blocking requests by IP address is extremely...
  9. LiteCache

    Custom error codes and access logging

    Any status code smaller 100 and higher 599 is invalid. Using status codes outside this range causes error 500, so this is not a OLS bug or malfunction. https://www.rfc-editor.org/rfc/rfc9110.html
  10. LiteCache

    Alternative to LiteSpeed Cache Warmup Crawler

    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.
  11. LiteCache

    Is Google PageSpeed Just an Illusion?

    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...
  12. LiteCache

    How to really Fix "Reduce Unused JavaScript" in WordPress

    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...
  13. LiteCache

    Alternative to LiteSpeed Cache Warmup Crawler

    WordPress multisite is unsupported
  14. LiteCache

    How to prevent losing money in WooCommerce checkout

    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...
  15. LiteCache

    WordPress Optimization for Nothing – And the Speed Not for Free

    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...
  16. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    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
  17. LiteCache

    Best strategy for caching Woocommerce products and ESI debugging

    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....
  18. LiteCache

    Best strategy for caching Woocommerce products and ESI debugging

    "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.
  19. LiteCache

    Best strategy for caching Woocommerce products and ESI debugging

    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...
  20. LiteCache

    Best strategy for caching Woocommerce products and ESI debugging

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