Your content is not lost. Access your files by FTP or the cPanel File Manager, go to wp-content/plugins/ and rename the cache-lat-client folder to cache-lat-client-off: WordPress deactivates the plugin and the site comes back. If the 500 error persists, the cache.lat block has to be removed from .htaccess. Step by step in WordPress site recovery. Before installing or updating any plugin, make sure you have that access and a backup.

It generates a static HTML copy of your WordPress site's public pages and configures your own Apache server (via .htaccess) to serve that HTML directly, without WordPress or PHP running on every visit. The generated file always stays on your own hosting.

Use the free speed test: enter your site address and in about 20 seconds you see how it responds today (server time, page weight, unoptimized images, blocking scripts) and an estimate of the improvement with cache.lat. It is an estimate calculated from what was measured, not a promise; the real result shows up once you install the plugin (free for up to 10 pages) and test again, either there or with the plugin's own "Performance test".

Yes, always. Any site can install it and cache up to 10 pages at no cost and with no expiration, no card or account required. A license only removes that 10-page limit and enables "whole site" mode with exclusions — it's not a "lite" version that stops working. There are two licenses: WordPress (no WooCommerce, ideal for blogs) and Advanced (with WooCommerce); the plugin is the same and the license decides the type. See pricing.

Yes. cache.lat serves the static HTML from your own hosting's Apache, so a CDN in front only forwards or caches those responses, and it works very well for your images, CSS, JS and fonts. There are three things to watch: (1) keep the CDN from caching the HTML (to generate, cache.lat requests each page live with the X-TNL-Bypass header, and a CDN holding an edge copy would give it old content); (2) keep it from blocking the engine with bot challenges (allow the CacheLat-Generator User-Agent); (3) make sure no "Cache Everything" rule reaches the cart, checkout, account or URLs with a query string. On Cloudflare, turn off Rocket Loader and do not combine it with APO. Today cache.lat does not purge the CDN automatically. Full guide in the documentation.

No. You can convert your license from the plugin panel and trade in the time you already paid for. Each license is worth its price ÷ 365 per day, so your remaining days convert as: remaining days × WordPress price ÷ Advanced price, plus 30 bonus days for converting. Example with $19.99 and $39.99: 200 days left on WordPress equal 99 days of Advanced + 30 bonus = 129 days of Advanced. The plugin shows you the exact calculation before you confirm. The conversion is one-way and can be done once per license.

WooCommerce shop, product and category pages are not cached, and the plugin shows a notice (which you can mark as intentional). The cart, checkout and account are never cached on any plan. If you later need your store cached, you move to the Advanced license by paying the difference, with nothing to reinstall.

Selling and managing cache.lat licenses is exclusive to TuNegocioEnLinea.net (TNL), the company that owns the cache.lat brand. There is no other purchase channel or authorized reseller. See our refund policy.

One year from when you activate it on a site, not from when you purchase it. Each license starts counting its own year only when it's connected to a site, so you can buy ahead and activate it when you need it.

Yes. It automatically detects product and category pages to cache them, and always excludes — without exception — cart, checkout and "My account", since those depend on each visitor's session.

cache.lat detects it automatically on activation and on every panel load. If it finds one active, it shows a notice recommending you keep only one, and meanwhile switches to "safe mode": it keeps generating and serving the static HTML (the essential part), but turns off its own optimizations (fonts, deferred JS, minification, AVIF/WebP images) so two different manipulations don't mix on the same page. Your preferences stay saved and resume on their own once the conflict is resolved.

Nothing bad. Generation is chained to WP-Cron as a second path: it keeps moving forward on its own with every visit the site receives, without needing the panel to stay open. If you reopen the panel with a job pending, it resumes the progress bar where it was. You can also use the "Abort" button if you'd rather cancel it: whatever was already generated stays as is.

Yes. Publishing, editing, unpublishing or deleting content (and changing stock, approving comments, or moving categories) instantly clears the affected static file and regenerates just that one. Broader changes — menu, theme, customizer, widgets — regenerate the whole site. You can also schedule an automatic refresh every 6h, 12h, 24h, 7 days, or monthly.

Yes, optionally: it converts your media library to AVIF or WebP (using Imagick or GD, whichever your hosting has) and rewrites images in the generated HTML to use the lighter format, always keeping the original as a fallback.

Only what's needed to generate the HTML of the pages you choose to cache (each page's URL and the public content that page returns) plus technical license data (domain, site key). No other information from your WordPress install is sent to external servers. More detail in our privacy policy.

No. Just Apache with mod_rewrite enabled — something practically any shared hosting already has. It doesn't depend on LiteSpeed, Nginx, or any exotic modules.

Yes, anytime. The panel has a "Back to free plan" button that downgrades your plan server-side without deleting the cache already generated. Uninstalling the plugin removes its settings and generated files; deactivating it (without uninstalling) leaves everything intact.