Compatibility & Runtime Health
See whether the current host is ready, avoid duplicate optimisation work, and let background jobs yield safely under pressure
New in 1.6.0: Free runtime integration
Runtime Readiness
Open ProRank SEO → Performance → Database & Server and find Server Information. The Runtime readiness panel is diagnostic only: viewing it does not change server settings or enable an optimisation.
Ready
Required checks passed. Optional capabilities remain visible below.
Review recommended
One or more warnings deserve attention, but no required check is blocked.
Action required
A required runtime check failed, such as an unavailable cache runtime or unwritable generated-file storage.
What ProRank Checks
| Check | Meaning |
|---|---|
| PHP runtime | Reports whether the server meets ProRank’s supported PHP runtime. |
| PHP memory | Warns when the configured PHP memory limit is below 128 MB for larger background batches. |
| Page cache runtime | When page cache is enabled, checks its drop-in, WP_CACHE setting, and writable cache directory. |
| Background scheduler | Checks for WordPress Cron or Action Scheduler and explains what to verify when neither can run work. |
| Generated-file storage | Checks whether the uploads directory can store generated image, CSS, and binary assets. |
| Background workload guard | Reports whether current host load, memory headroom, or the request-time budget is making work yield. |
| Local image encoders | Reports available WebP, AVIF, or JPEG XL output when local modern-image generation is requested. |
| Optional capabilities | Reports OPcache, a persistent object cache, and validated CDN origins without treating them as hard requirements. |
39 Capability-Level Compatibility Profiles
Suppress overlapping work
When a recognised cache, asset, or image-optimisation plugin is active, ProRank suppresses only the modules listed for that profile. A page-cache overlap does not automatically disable unrelated features.
Keep control explicit
The catalogue covers 39 built-in plugin profiles and can be extended by WordPress filters. Profile decisions are separate from builder-specific protections and automatic rollback safeguards.
Background Workload Safeguards
Yield, then retry
The workload guard evaluates host load, PHP memory use and headroom, and the current request runtime. When a configured budget is reached, guarded cache work—and the Pro link index where applicable—pauses and reschedules instead of forcing the current batch through.
A temporary workload warning is expected during a busy period. Recheck after traffic or another maintenance task settles; investigate if the same reason remains continuously.
Using an Override
Performance Module Overrides apply only to eligible, non-strict builder and stack guidance. They do not bypass the 39 known-plugin catalogue, competitor safe mode, an automatic rollback, or the builder-and-commerce hard safety layer.
- Confirm that diagnostics identify an eligible builder or stack suppression rather than a strict known-plugin conflict.
- Open ProRank SEO → Support & Account → Advanced Settings.
- Under Performance Module Overrides, enable only the tested CSS Optimisation, JS Optimisation, Critical CSS, or Unused CSS Removal override.
- Clear caches and test public templates, forms, menus, and builder interactions again.
Expert controls