cache.lat
You installed a cache plugin, the panel says "active" and everything looks fine. But is your site really serving pages from cache? Many times the answer is "halfway", and nobody notices until a traffic spike hits. This guide shows how to check it in five minutes, without paid tools.
Why "active" doesn't mean "working"
A cache system can be installed and still be skipped by many visits. The most common causes are cookies that force WordPress to generate the page again, parameters in the URL that create different variants, pages excluded by mistake, or a server that ignores the saved file. The symptom is always the same: the page is generated with PHP and the database on every visit, exactly what you wanted to avoid.
Test 1: look at the response headers
From a terminal, request only the headers of your homepage:
curl -sI https://yoursite.com/
Look for cache-related headers (Cache-Control, Age, Last-Modified, ETag or one specific to the plugin). Repeat the command two or three times: if the content is static, the response should be stable and fast. If the timestamps change every time, it is probably being generated dynamically.
Test 2: look for the mark in the HTML
Many cache systems leave a comment or a signature in the final HTML. With curl -s https://yoursite.com/ | grep -i cache you can confirm whether the page came from the saved file. At cache.lat, for example, the footer of the pages indicates that they were served as a static file, something explained on the how it works page.
Test 3: compare the time to first byte
TTFB (time to first byte) is the metric most sensitive to cache. Measure it with curl:
curl -s -o /dev/null -w '%{time_starttransfer}' https://yoursite.com/
Run it several times on the homepage and on a URL with an invented parameter, for example ?test=1. If the second one is much slower, your configuration treats each variant as a new page, and that affects your campaigns with tracking parameters.
Test 4: test as an anonymous visitor and as a user
Open the site in an incognito window and compare it with your administrator session. It is normal for logged-in users to receive dynamic content; what is not normal is for an anonymous visitor to receive session cookies or personalized content. Check the cookies in the browser tools (Application or Storage tab): if a session cookie appears on an anonymous visit, some plugin is creating it and it is probably breaking the cache.
What to do if you find failures
- Unnecessary cookies: deactivate or configure the plugin that creates them so it only acts where needed (cart, account, checkout).
- Variants by parameters: define which tracking parameters are ignored so that a URL with
utm_serves the same saved page. - Excessive exclusions: review the list of excluded URLs; it is common for an old rule to be left that leaves out entire sections.
- Regeneration after editing: confirm that when publishing or updating a post, the static version is renewed and no old content remains.
A simple habit: repeat the test after every change
Every time you install a new plugin, change themes or touch the server configuration, repeat these tests. They take minutes and prevent you from discovering the problem when an ad or a viral post is already sending visits. If you want to go deeper into the technical details of how static files are served, review the technical data and the documentation.
Summary
Verifying your cache is as important as installing it. With headers, a search in the HTML, TTFB measurements and a cookie review you have a clear diagnosis. And if something doesn't add up and you need a hand, you can write to the TuNegocioEnLinea.net team.