Performance Recommendations

The Recommendations panel looks at your current xSpeed Cache settings and server state, then lists configuration changes that would speed up your site. Many can be applied with one click.

What this does

xSpeed Cache runs a set of rules against your current configuration. Each rule checks one thing, like whether page cache is on or whether GZIP is enabled. When a rule matches, it adds a recommendation to the list with:

• A title and a short explanation.
• A severity — high, medium (med), or low.
• For most rules, a patch that the Apply button can write for you. Some recommendations are informational only and have no one-click apply.

Recommendations are sorted by severity, highest first.

Why use it

It is an easy way to find speed wins you have not turned on yet. Instead of reading every settings panel, you get a short, ranked list of what to change and, in most cases, a button to change it.

Requirements

• xSpeed Cache Pro must be active. Recommendations is a Pro feature.
• The rules read your xSpeed Cache Free module settings, so the matching modules need to be present.

How to use it

1. Open the xSpeed Cache dashboard and go to the Recommendations panel (the lightbulb icon).
2. Review the list. Items are ordered by severity.
3. For a recommendation with a one-click option, select Apply to write the change.
4. After applying, the list refreshes so you can see what is left.

Note: Applying a recommendation updates the relevant xSpeed Cache module settings. Recommendations that suggest manual steps, like installing a persistent object cache, do not have an Apply button.

What the rules check

These are the recommendations xSpeed Cache can surface, based on the rule set in the source:

Recommendation	Severity	One-click apply
Page cache is off	High	Yes
GZIP / Brotli compression off	High	Yes
HTML minification disabled	Medium	Yes
CSS or JS minification disabled	Medium	Yes
Image lazy-loading disabled	Medium	Yes
Browser cache headers not set	Medium	Yes
No persistent object cache	Medium	No (manual)
Cache preloader not running	Low	Yes
WordPress heartbeat at default frequency	Low	Yes
Database auto-cleanup disabled	Low	Yes

A few notes on specific rules:

• No persistent object cache appears only when WordPress is not already using an external object cache. It is informational. xSpeed Cache can generate the wp-config snippet, but there is no one-click apply for it.
• Cache preloader not running appears only when the page cache is already enabled. There is no point preloading a cache that is off.
• Database auto-cleanup disabled appears when the database cleanup schedule is unset or set to manual. Applying it sets a weekly schedule.

Severity, in short

• High — the biggest wins. Page cache and compression sit here.
• Medium — solid improvements, like minification, lazy-loading, and browser cache headers.
• Low — smaller tune-ups, like preloading, heartbeat throttling, and database cleanup.

Best practices

• Work top to bottom. The list is already ordered by impact.
• Apply the high-severity items first, since they give the largest improvement.
• After applying changes, re-check the Health panel and, if you have it, run a fresh PageSpeed Insights audit to confirm the effect.

Troubleshooting

A recommendation has no Apply button. That recommendation is informational and needs a manual step. The clearest example is the persistent object cache suggestion.

An item is still in the list after I applied it. The list refreshes after an apply. If an item remains, the underlying setting may not have changed, or another condition for that rule is still met.

I do not see the preloader recommendation. It only appears when the page cache is already enabled. Enable the cache first.

FAQ

Does Apply change my settings? Yes. For recommendations with a one-click option, Apply writes the change to the relevant xSpeed Cache module settings.

Will the list ever be empty? Yes. When no rules match your current configuration, there are no recommendations to show.

Note: Recommendations works by scanning your configuration against a fixed set of rules and offering a one-click fix where one applies. It does not auto-heal, resolve plugin conflicts on its own, run background cleanups on a schedule, or let you write custom rules. Those are not part of this feature.

Related

• Reading the Cache Health Dashboard
• PageSpeed Insights Integration
• Real-User Monitoring (Core Web Vitals)