cache.lat
Your WordPress site takes a long time to load and the first thing you think is "I need to optimize the theme" or "there are too many plugins." Sometimes that's true. But many times the bottleneck is the server, and no front-end optimization will fix it. This guide helps you distinguish a site problem from a hosting problem.
The main signal: a high and erratic TTFB
Time to first byte (TTFB) measures how long the server takes to start responding. If it's high even on simple pages, the problem is usually before the browser renders anything. If it also varies a lot from one visit to another, suspect the shared server. You can see how to measure it properly in our article about TTFB in WordPress.
Five symptoms that the server is the bottleneck
- Slowness at certain times: if it runs fine at dawn and drags in the mid-afternoon, you're probably sharing resources with other sites.
- Intermittent 503 or 508 errors: they usually indicate CPU, memory, or simultaneous process limits reached.
- The admin panel is slow: if wp-admin takes longer than the public site, the problem is PHP execution or the database, not images.
- An empty site is also slow: install a default theme in a test environment, without plugins. If it's still slow, the plugin is not the culprit.
- Traffic spikes bring it down: a campaign or a mention on social media and the site stops responding.
How to do a simple diagnosis
1. Measure several times, at different hours
A single measurement says nothing. Test the home page and a post, three times a day for a few days, and note the TTFB. Look for patterns, not isolated values.
2. Isolate plugins and theme
In a staging environment, deactivate all plugins and activate a default theme. If the response improves a lot, reactivate them one by one. If it doesn't improve, the limit is in the hosting.
3. Check the resources your plan gives you
Look in the panel at how much CPU, RAM, and concurrent PHP processes you have assigned and how much your site consumes. Many hostings show usage graphs: if they hit the ceiling, you already have the answer.
4. Check the PHP version
Using a PHP version with active support matters for both security and performance. If you haven't migrated yet, check our migration guide.
Page caching reduces server load
Every visit to a dynamic page forces the server to execute PHP and query the database. If the same page is delivered already generated as HTML, the server works much less per visit. That's why page caching helps so much on hostings with limited resources.
cache.lat works exactly like that: a lightweight plugin on your WordPress and an external engine that generates static copies of your URLs. You can see the process details in how cache.lat works and the technical aspects in technical data.
However, caching is not magic: if your hosting is overloaded even to serve a file, or if the pages that are not cached (cart, account, administration) are what you use most, you will still feel the limit. Caching alleviates, it does not replace an adequate plan.
When should you change plans or hosting?
- When resource usage hits the limit steadily, not just at occasional peaks.
- When you have already applied caching, cleaned up plugins, and use a current PHP version, and the symptoms persist.
- When your site generates income and outages cost you sales.
Before migrating, try the cheap stuff first: page caching, plugin cleanup, and a current PHP version. If after that the server is still the limit, you already have data to justify the change and choose the right plan.
Summary
Variable slowness depending on the time, 503 errors, a heavy wp-admin, and an empty site that still responds slowly are clues to a hosting problem. Measure, isolate, check resources, and only then decide. If you want help evaluating your case, you can contact the TNL team.