WordPress operations
OPcache and hosting performance
OPcache off, no object cache, slow TTFB — Health finding and what to fix with hosting.
Typical symptom
High TTFB even after Pulse/Images, opcache_disabled, shared host without Redis.
Puluno modules
Health
Undo change
No — info / hosting only
Issue codes
opcache_disabled, object_cache_missing
What you see
opcache_disabledorobject_cache_missing.- PageSpeed: Server response time long, LCP OK after HTML arrives.
- Client on cheap shared — “WP is slow” with no specific plugin.
- Health recommends OPcache / object cache.
Why it happens
PHP without OPcache compiles scripts every request. Without Redis/Memcached object cache repeats DB queries.
Typical situations:
- Host disabled OPcache on old PHP.
- Missing
object-cache.phpdrop-in (Redis plugin not installed). - Too many plugins on 512 MB RAM.
- Not OPcache but slow DB on shared.
What Puluno does
| Phase | Module | Action |
|---|---|---|
| Diagnose | Health + Explorer | OPcache state, TTFB hint |
| Apply | Pulse | micro optimizations, not server OPcache |
| Verify | Lab / Explorer | TTFB improves only partly without host |
Puluno does not toggle OPcache in FastComet panel — hosting ticket.
Step by step
- Health report — OPcache / object cache findings.
- Host panel — PHP 8.2+, OPcache enabled.
- Redis object cache (if offered) — drop-in + plugin.
- Pulse — trim autoload bloat, not a second cache plugin.
- Verify: TTFB in Explorer / Lab — realistic target (<600 ms shared).
- If not enough: plan upgrade or managed WP.
Related: Slow site LCP — different layer than TTFB.
Rollback — undo the change
Enabling OPcache on host has no Puluno rollback.
Object cache drop-in — backup wp-content before install.
When it is not Puluno
- Server geography far from users — CDN, not plugin.
- DB lock during import — temporary, not OPcache.
- Client measures logged-in admin bar — always slower.
Related situations
Module manual