Title: xSpeed Cache – AI-Powered Performance Hub with MCP, Caching &amp; CDN
Author: WPDeveloper
Published: <strong>27 mai 2026</strong>
Last modified: 24 august 2026

---

Caută module

![](https://ps.w.org/xspeed/assets/banner-772x250.png?rev=3642074)

![](https://ps.w.org/xspeed/assets/icon-256x256.png?rev=3642074)

# xSpeed Cache – AI-Powered Performance Hub with MCP, Caching & CDN

 De [WPDeveloper](https://profiles.wordpress.org/wpdevteam/)

[Descarcă](https://downloads.wordpress.org/plugin/xspeed.1.2.0.zip)

 * [Detalii](https://ro.wordpress.org/plugins/xspeed/#description)
 * [Recenzii](https://ro.wordpress.org/plugins/xspeed/#reviews)
 *  [Instalare](https://ro.wordpress.org/plugins/xspeed/#installation)
 * [Dezvoltare](https://ro.wordpress.org/plugins/xspeed/#developers)

 [Suport](https://wordpress.org/support/plugin/xspeed/)

## Descriere

Your visitors decide to stay or leave in under 3 seconds. **xSpeed Cache** makes
sure they stay.

Most caching plugins bury you in settings, charts, and upgrade popups. xSpeed Cache
does the opposite — install it, flip one switch, and your site loads faster. No 
bloat, no upsells nagging you, no PhD required.

Built by the team at **WPDeveloper** — trusted by over 7 million WordPress users
worldwide.

#### What Does xSpeed Cache Do?

xSpeed Cache is a full-site performance plugin. It caches your pages, shrinks your
code, compresses your files, and serves everything as fast as your server physically
can — including an AI-powered audit that tells you exactly what’s slowing your site
down.

The result: pages that load in milliseconds, not seconds. Better Google PageSpeed
scores. Happier visitors. Better SEO rankings.

#### The Speed Advantage No Other Free Plugin Offers

When xSpeed Cache caches a page, it doesn’t just save it — it serves it directly
from the server, bypassing PHP entirely.

That means:

 * **With xSpeed static cache:** 5–15ms response time
 * **Without it (PHP-served cache):** ~85ms response time

That’s up to **17× faster** page delivery on cache hits. No other free caching plugin
does this across Apache, nginx, and LiteSpeed automatically.

#### Features at a Glance

**Page Caching**

Your pages are saved as static HTML files and served instantly to visitors — before
WordPress even loads. The cache rebuilds itself automatically whenever you publish
a post, switch themes, or update a plugin. You never have to think about it.

 * Static-file rewrite path (bypasses PHP entirely — 5–15ms TTFB)
 * Auto-purge on publish, update, comment, theme change
 * One-click cache purge from the admin bar
 * Exclude specific URLs (e.g. `/cart`, `/checkout`, `/my-account`)
 * Set your own cache expiry (1–720 hours)
 * Separate mobile cache for phone and tablet visitors
 * Per-post cache rules — custom expiry or disable caching for individual posts

**Code Minification**

Strips all the unnecessary whitespace, comments, and characters from your HTML, 
CSS, and JavaScript without breaking anything.

 * Minify HTML, CSS, and JavaScript
 * Combine CSS and JS files to reduce HTTP requests
 * Defer or delay JavaScript so it doesn’t block page rendering
 * Async CSS loading
 * Removes `?ver=` query strings from asset URLs
 * Safe-minify: automatically skips already-minified files and falls back if anything
   looks off

**GZIP Compression**

Makes every file your server sends smaller — so browsers download them faster.

 * Auto-configures GZIP on Apache and LiteSpeed
 * Shows a ready-to-paste config snippet for nginx and IIS
 * Detects if your server already has GZIP active — no double-configuration

**Lazy Load**

Images, videos, and iframes load only when a visitor scrolls to them — not all at
once on page load.

 * Lazy load images, iframes, and videos
 * Automatic CLS (Cumulative Layout Shift) fix so your layout doesn’t jump

**Fonts Optimization**

Web fonts are one of the most common causes of slow-loading pages.

 * Adds `font-display: swap` so text is visible immediately while fonts load
 * Preloads above-the-fold font files for instant rendering
 * Removes the blank-text flash caused by slow Google Fonts responses

**Browser Cache**

Tells browsers to remember your static files (images, CSS, JS) so returning visitors
load your site even faster.

 * Sets proper `Cache-Control` and `Expires` headers
 * Works automatically — no manual configuration needed

**Cache Preloader**

Warms up your cache automatically so the very first visitor after a purge still 
gets a fast page.

 * Sitemap-driven cache warmer
 * Auto-warms cache when you publish or update content

**Object Cache (Redis / Memcached)**

Speed up database-heavy WordPress installs with server-side object caching.

 * Connect Redis or Memcached in seconds
 * View status and flush cache from the dashboard

**CDN Support**

Serve your static files from a CDN for faster global delivery.

 * Pull-zone URL rewriting for any CDN provider
 * Built-in Cloudflare integration: connect your zone, auto-purge on publish, toggle
   dev mode

**Database Optimization**

A bloated database slows down every page load. xSpeed Cache keeps yours clean.

 * Optimize database tables
 * Remove post revisions, spam, trash, transients, and orphaned meta
 * Schedule automatic cleanup so it runs on autopilot

**Disable Bloat**

Turn off WordPress features you don’t use — each one is a request your server doesn’t
have to make.

 * Disable dashicons on the frontend
 * Remove oEmbed, RSS feeds, XML-RPC, jQuery Migrate, REST API authentication headers

**AI-Powered Site Audit (Pro)**

xSpeed Pro scans your specific site and tells you exactly which performance features
will help the most — with severity ratings and concrete reasons, not generic advice.

#### Smart Enough to Stay Out of Trouble

xSpeed Cache handles the edge cases other plugins miss:

 * **Multisite ready** — each site in the network gets its own cache and settings.
 * **LiteSpeed server?** — xSpeed Cache detects LiteSpeed Cache’s server module 
   and steps back to avoid conflicts.
 * **WooCommerce?** — logged-in customers and checkout pages are never cached.
 * **WordPress Site Health** — xSpeed Cache adds its own health check under Tools
   Site Health so you always know your cache config is working correctly.
 * **Works on any server** — Apache, nginx, LiteSpeed, IIS, and any standard PHP
   host.

#### Designed for Everyone

**Non-technical users:** A 3-step setup wizard walks you through first-time configuration
in under 2 minutes. Settings auto-save — there’s no Save button to forget.

**Developers:** REST API at `/wp-json/xspeed/v1/`, developer filters (`xspeed_skip_minify`,`
xspeed_cache_skip_for_post`, `xspeed_cache_expiry_for_post`), `WP_DEBUG` awareness,
and a React 18 + TypeScript admin UI under 80 KB gzipped.

**Agencies:** Use the `xspeed_branding` filter to white-label the dashboard for 
clients.

#### Private By Default

xSpeed Cache never collects personal data, stores IP addresses, or uses tracking
cookies. Every optimization runs locally on your server. By default it makes no 
calls to any third-party server — the only request is a quick check to your own 
site’s home URL to confirm GZIP is active, rate-limited to once per hour.

xSpeed Cache also includes **optional usage analytics**. The setup wizard shows 
a clearly-labeled consent control for it (enabled by default, untick to opt out),
and nothing is sent until you confirm your choices in the wizard. When enabled, 
xSpeed Cache shares anonymous, non-sensitive diagnostics — your WordPress & PHP 
version, active theme & plugins, server type, site language, and which xSpeed Cache
features you have switched on — so we know what to keep fast and compatible. No 
personal data and no page content are ever sent, and you can turn it off again at
any time from your dashboard. (See „External services” below.)

#### Backed By a Team You Trust

xSpeed Cache is developed by the trusted team at WPDeveloper, a leading WordPress
marketplace used and loved by millions of users.

#### Loved xSpeed Cache?

If xSpeed Cache makes your site faster, please leave a review on WordPress.org —
it really helps!

### External services

xSpeed Cache contacts your own site (the gzip probe below); when usage analytics
is enabled, an analytics service; only if you choose to submit the optional deactivation
survey, that same service; and — only if you turn it on — one external performance-
score provider. The setup wizard shows a clearly-labeled consent control for analytics(
enabled by default, untick to opt out), and nothing is sent until you confirm your
choices there. The deactivation survey is separate and never sends anything unless
you explicitly click Submit. External scores are off by default and never run on
their own.

#### Self-hosted gzip probe

 * **What it does:** Issues a single `GET` request to your site’s home URL (`home_url('/')`)
   with an `Accept-Encoding: gzip` header to detect whether your web server is already
   serving gzipped responses. The response body is discarded; only the `Content-
   Encoding` header is read.
 * **When it runs:** On demand when the admin dashboard loads server status, throttled
   to once per hour via a transient (`xspeed_gzip_active`).
 * **Where the request goes:** Your own site (`home_url()`). This request goes only
   to your own server.
 * **What is sent:** No personal data, no site identifiers, no payload — just a 
   standard HTTP `GET` from your server back to your server.

#### Usage analytics (opt-in, off by default)

 * **What it does:** When usage analytics is enabled, xSpeed Cache periodically 
   sends anonymous, non-sensitive diagnostics to help us keep the plugin fast and
   compatible with real-world WordPress environments. Data sent: site URL, site 
   name, WordPress version, PHP version, site language & charset, multisite flag,
   server software, your list of active & inactive plugins, active theme & version,
   text direction, and your xSpeed Cache feature usage (which optimization features
   you have switched on and their numeric settings — e.g. cache lifetime, minification,
   lazy-load). This is feature-usage data only: it tells us which features are actually
   used so we can focus on what matters. **We never send any values you enter** —
   no API keys, tokens, passwords, license keys, email addresses, URLs, brand names,
   or logos — and **no page content, no visitor data, and no personal data** (your
   email is never collected in the free plugin).
 * **When it runs:** It runs at most once per day via WP-Cron, only after you confirm
   your choices in the setup wizard. Untick the consent control (or disable it later
   from the dashboard) and nothing is ever sent.
 * **Where the request goes:** WP Insights, WPDeveloper’s usage-analytics service—`
   https://send.wpinsight.com/process-plugin-data`. ([Privacy Policy](https://wpdeveloper.com/privacy-policy))
 * **How to turn it off:** Untick the consent control in the wizard, or disable 
   it later from the xSpeed Cache dashboard. Opting out stops all data collection
   and clears the scheduled task.

#### External performance scores (opt-in, off by default)

 * **What it does:** Lets you run a performance audit of one of your own pages from
   the dashboard and shows the score alongside xSpeed Cache’s internal TTFB benchmark.
   Two providers are supported: Google PageSpeed Insights (works without an API 
   key; you may add your own key to raise Google’s anonymous rate limit) and GTmetrix(
   requires your own API key — it has no anonymous mode).
 * **When it runs:** Only when you press **Test now** on the dashboard, or run `
   wp xspeed score run`. There is no schedule and no background call. If the feature
   is left off — which is the default — no request is ever made.
 * **Where the request goes:** Google PageSpeed Insights — `https://www.googleapis.
   com/pagespeedonline/v5/runPagespeed` ([Terms](https://developers.google.com/speed/docs/insights/v5/about),
   [Privacy Policy](https://policies.google.com/privacy)) — or GTmetrix — `https://
   gtmetrix.com/api/2.0/tests` ([Terms](https://gtmetrix.com/terms-of-service.html),
   [Privacy Policy](https://gtmetrix.com/privacy.html)).
 * **What is sent:** The URL you are testing (your own page, which the provider 
   then fetches publicly) and, if you supplied one, your own API key for that provider.
   No personal data, no visitor data, and no site content are sent by the plugin.
 * **How to turn it off:** Switch „Enable external scores” off in the xSpeed Cache
   dashboard (Health  PageSpeed). Past results stay in your database until you clear
   them.

#### Deactivation feedback (optional, only when you submit it)

 * **What it does:** When you deactivate xSpeed Cache, a short optional survey asks
   why, so we can fix problems and prioritize the right features. Nothing is sent
   unless you pick a reason and click **Submit & Deactivate**.
 * **What is sent:** the reason (or reasons) you selected and any note you type.
   If usage analytics (above) is enabled, that reason is attached to your regular
   analytics report. If usage analytics is disabled, only a minimal message is sent—
   the reason, your optional note, your site URL, the xSpeed Cache version, and 
   your WordPress & PHP version — and nothing else (no plugin list, no theme data,
   no personal data, no page content).
 * **When it runs:** Only on the deactivation screen, and only when you click **
   Submit & Deactivate**. Choosing **Skip & Deactivate**, closing the dialog, or
   pressing Esc sends nothing at all.
 * **Where the request goes:** WP Insights, WPDeveloper’s service — `https://send.
   wpinsight.com/process-plugin-data`. ([Privacy Policy](https://wpdeveloper.com/privacy-policy))
 * **How to avoid it:** Click **Skip & Deactivate** (or close the dialog) instead
   of Submit — deactivation works exactly the same, with no data sent.

### Third-party libraries

This plugin bundles the following GPL-compatible third-party libraries:

#### matthiasmullie/minify

Used for CSS and JavaScript minification.

 * Source: https://github.com/matthiasmullie/minify
 * License: MIT

#### matthiasmullie/path-converter

Dependency of `matthiasmullie/minify`.

 * Source: https://github.com/matthiasmullie/path-converter
 * License: MIT

#### React / React DOM / Scheduler

Used for the xSpeed Cache admin interface bundle.

 * Source: https://github.com/facebook/react
 * License: MIT

#### lucide-react

Used for admin interface icons.

 * Source: https://github.com/lucide-icons/lucide
 * License: ISC

## Capturi ecran

[⌊Cache panel — master toggle, status, and live stats (cached pages, cache size,
last purge).⌉⌊Cache panel — master toggle, status, and live stats (cached pages,
cache size, last purge).⌉[

Cache panel — master toggle, status, and live stats (cached pages, cache size, last
purge).

[⌊Minification — minify and combine HTML, CSS, and JavaScript with defer/delay options.⌉⌊
Minification — minify and combine HTML, CSS, and JavaScript with defer/delay options
.⌉[

Minification — minify and combine HTML, CSS, and JavaScript with defer/delay options.

[⌊Lazy Load — defer images, iframes, and videos until they scroll into view, with
CLS-fix.⌉⌊Lazy Load — defer images, iframes, and videos until they scroll into view,
with CLS-fix.⌉[

Lazy Load — defer images, iframes, and videos until they scroll into view, with 
CLS-fix.

[⌊Cache Preloader — sitemap-driven cache warmer that keeps the first visitor fast.⌉⌊
Cache Preloader — sitemap-driven cache warmer that keeps the first visitor fast.⌉[

Cache Preloader — sitemap-driven cache warmer that keeps the first visitor fast.

[⌊Object Cache — connect Redis or Memcached, view status, and flush from the dashboard.⌉⌊
Object Cache — connect Redis or Memcached, view status, and flush from the dashboard
.⌉[

Object Cache — connect Redis or Memcached, view status, and flush from the dashboard.

[⌊CDN — pull-zone URL rewriting for faster global static-asset delivery.⌉⌊CDN — 
pull-zone URL rewriting for faster global static-asset delivery.⌉[

CDN — pull-zone URL rewriting for faster global static-asset delivery.

[⌊Cloudflare — connect your zone, auto-purge on publish, and toggle development 
mode.⌉⌊Cloudflare — connect your zone, auto-purge on publish, and toggle development
mode.⌉[

Cloudflare — connect your zone, auto-purge on publish, and toggle development mode.

[⌊Custom Cache Rules — per-URL and per-post caching rules with custom expiry.⌉⌊Custom
Cache Rules — per-URL and per-post caching rules with custom expiry.⌉[

Custom Cache Rules — per-URL and per-post caching rules with custom expiry.

[⌊Disable Bloat — switch off unused WordPress features (dashicons, oEmbed, RSS, 
XML-RPC, and more).⌉⌊Disable Bloat — switch off unused WordPress features (dashicons,
oEmbed, RSS, XML-RPC, and more).⌉[

Disable Bloat — switch off unused WordPress features (dashicons, oEmbed, RSS, XML-
RPC, and more).

[⌊Heartbeat Control — throttle the WordPress Heartbeat API to reduce admin-ajax 
load.⌉⌊Heartbeat Control — throttle the WordPress Heartbeat API to reduce admin-
ajax load.⌉[

Heartbeat Control — throttle the WordPress Heartbeat API to reduce admin-ajax load.

[⌊AI-Powered Site Audit (Pro) — site-specific recommendations with severity ratings
and concrete reasons.⌉⌊AI-Powered Site Audit (Pro) — site-specific recommendations
with severity ratings and concrete reasons.⌉[

AI-Powered Site Audit (Pro) — site-specific recommendations with severity ratings
and concrete reasons.

## Instalare

 1. Go to **Plugins  Add New** in your WordPress admin and search for **xSpeed Cache**.
 2. Click **Install Now**, then **Activate**.
 3. Navigate to **xSpeed Cache** in your sidebar.
 4. The setup wizard will guide you through the rest — it takes about 2 minutes.

That’s it. Your site is now faster.

## Întrebări frecvente

### Will this break my site?

Very unlikely. xSpeed Cache includes safety checks for every optimization: minification
falls back to the original if anything looks off, and the cache bypasses logged-
in users, admin pages, AJAX, and REST requests automatically. If something ever 
looks wrong, you can toggle any feature off individually.

### Does it work with WooCommerce?

Yes. Add `/cart`, `/checkout`, and `/my-account` to the Excluded URLs list and xSpeed
Cache will skip caching those pages. Logged-in customers are never served cached
pages regardless.

### Does it work with my server?

xSpeed Cache works on Apache, nginx, LiteSpeed, IIS, and any standard PHP host. 
Static-cache rewriting and GZIP auto-configuration work out of the box on Apache
and LiteSpeed. For nginx and IIS, xSpeed Cache shows you a ready-to-paste config
snippet.

### Does it support WordPress Multisite?

Yes. Each site in the network has its own independent cache and settings.

### Will it conflict with LiteSpeed Cache?

No. xSpeed Cache detects LiteSpeed’s server-level caching module and steps back 
automatically to avoid double-caching. Otherwise, only run one page-cache plugin
at a time.

### How do I exclude a page from being cached?

Go to **xSpeed Cache  Settings**, paste the URL path (e.g. `/cart`) into the Excluded
URLs field — one path per line. Changes save automatically.

### How do I clear the cache?

Click **Purge** in the xSpeed Cache dashboard, or use **Purge xSpeed Cache** in 
your admin bar. The cache also clears itself automatically whenever you publish 
or update content.

### Can I use xSpeed Cache alongside Cloudflare?

Yes. The built-in Cloudflare module connects your zone and auto-purges Cloudflare’s
cache whenever xSpeed Cache purges its own — so both caches stay in sync.

### Can I disable minification temporarily for debugging?

Yes. Either toggle the option off in the admin UI, enable `WP_DEBUG` (xSpeed Cache
automatically skips HTML minification when debug is on), or use the `xspeed_skip_minify`
filter.

## Recenzii

![](https://secure.gravatar.com/avatar/ce30a9998828a8ef8b2348b48d787e03a472ef608f7d4f756c3d4a618e61f492?
s=60&d=retro&r=g)

### 󠀁[A Seriously Impressive Performance Plugin](https://wordpress.org/support/topic/a-seriously-impressive-performance-plugin/)󠁿

 [ecoverme](https://profiles.wordpress.org/ecoverme/) 25 august 2026

We’ve started using xSpeed Cache on several client websites at ECoverMe and have
been very impressed so far. It brings caching, performance optimization, CDN features,
and newer AI/MCP capabilities together in one place without making the setup feel
overly complicated. Performance plugins can sometimes create more problems than 
they solve, but xSpeed has been a smooth experience for us. Definitely a plugin 
worth watching as it continues to develop. Five stars from our agency.

![](https://secure.gravatar.com/avatar/01e1aa48f9cd5369c38a2e5f650c66075c26e24cbd193795b8a6dd92adefd8d5?
s=60&d=retro&r=g)

### 󠀁[Exactly what I’ve been searching for](https://wordpress.org/support/topic/exactly-what-ive-been-searching-for-5/)󠁿

 [mikefury](https://profiles.wordpress.org/mikefury/) 20 august 2026

I already own all products created by Wpdeveloper team, and once again, they did
not disappoint. If you want a blazing-fast WordPress site backed by an amazing team,
xSpeed Cache is a must-have. Highly recommended!

![](https://secure.gravatar.com/avatar/b3dc3973f78880adb1d87688d2b76013dce3dbb59d03c2d2f8087c0e74b6830e?
s=60&d=retro&r=g)

### 󠀁[Great team at WPDevelopers](https://wordpress.org/support/topic/great-team-at-wpdevelopers/)󠁿

 [ahitmarketing](https://profiles.wordpress.org/ahitmarketing/) 6 august 2026

I’ve been using WPDeveloper plugins for several years, and XSpeed continues that
same high standard of quality. The plugin is well-built, reliable, and clearly maintained
by a team that genuinely cares about performance and user experience. It’s a must-
have if you want your site to load fast and run smoothly. What I appreciate most,
though, is the support I’m getting. The support team has been friendly, responsive,
and truly helpful whenever I’ve needed assistance. It’s rare to find a plugin that
delivers both a great product and such excellent support. Highly recommended.

![](https://secure.gravatar.com/avatar/33fadaf8aef05d4f5ce5153c47ec1ecc45fa47b6bb54f6c06825ee4abfe32321?
s=60&d=retro&r=g)

### 󠀁[Excellent Plugin and Outstanding Support](https://wordpress.org/support/topic/excellent-plugin-and-outstanding-support-39/)󠁿

 [Vassos Hadjivassiliou](https://profiles.wordpress.org/more2think/) 4 august 2026

I’ve been using plugins from WPdeveloper for several years, and XSpeed continues
that same high standard of quality. The plugin is well-crafted, reliable, and clearly
maintained by people who care about their work and their users. This is a plugin
every website needs if the care about performance. What truly sets WPdeveloper apart
is their support team. They are always friendly, responsive, and genuinely helpful
whenever assistance is needed. It’s rare to find both a quality product and such
dedicated support behind it. Highly recommended! ⭐⭐⭐⭐⭐

![](https://secure.gravatar.com/avatar/e9ab2624742c1b0bf39a0197ab3718ad5e114ce795ee8a40f6086a0fc97b7c69?
s=60&d=retro&r=g)

### 󠀁[Excellent RTL FlipBox Support for Arabic PDF Books](https://wordpress.org/support/topic/excellent-rtl-flipbox-support-for-arabic-pdf-books/)󠁿

 [buhejji](https://profiles.wordpress.org/buhejji/) 2 iulie 2026

I would like to express my sincere appreciation for the excellent new feature recently
introduced by EmbedPress through the latest update. The ability to display PDF files
using the FlipBox view with proper RTL support is a wonderful and highly valuable
improvement, especially for Arabic books and right-to-left reading formats.This 
feature allows Arabic PDF books to be browsed naturally from right to left, which
greatly enhances the reading experience and makes EmbedPress even more suitable 
for Arabic content publishers.I also wish to extend my highest appreciation and 
respect to the EmbedPress support team for their outstanding responsiveness and 
professionalism. Their quick attention to customer requests and continuous efforts
to improve the plugin truly reflect a strong commitment to quality and user satisfaction.
Thank you to the entire EmbedPress team for this excellent update and for your continued
support.

![](https://secure.gravatar.com/avatar/642cc1fdbfcb5ea36041a666b1a53ae93f9b05eb1df88f0bf9f991516cbacc19?
s=60&d=retro&r=g)

### 󠀁[help with wordpress](https://wordpress.org/support/topic/help-with-wordpress-7/)󠁿

 [dubblocker](https://profiles.wordpress.org/dubblocker/) 9 iunie 2026

brill plugin!

 [ Citește toate cele 6 recenzii ](https://wordpress.org/support/plugin/xspeed/reviews/)

## Contributori și dezvoltatori

„xSpeed Cache – AI-Powered Performance Hub with MCP, Caching & CDN” este un software
open-source. La acest modul au contribuit următoarele persoane.

Contributori

 *   [ WPDeveloper ](https://profiles.wordpress.org/wpdevteam/)
 *   [ M Asif Rahman ](https://profiles.wordpress.org/asif2bd/)
 *   [ Akash Mia ](https://profiles.wordpress.org/seakashdiu/)
 *   [ Nahid Hasan ](https://profiles.wordpress.org/tushar284/)
 *   [ Abu Hurayra ](https://profiles.wordpress.org/hurayraiit/)

[Tradu „xSpeed Cache – AI-Powered Performance Hub with MCP, Caching & CDN” în limba ta.](https://translate.wordpress.org/projects/wp-plugins/xspeed)

### Te interesează dezvoltarea?

[Răsfoiește codul](https://plugins.trac.wordpress.org/browser/xspeed/), vezi [depozitarul SVN](https://plugins.svn.wordpress.org/xspeed/),
sau abonează-te la [jurnalul de dezvoltare](https://plugins.trac.wordpress.org/log/xspeed/)
prin [RSS](https://plugins.trac.wordpress.org/log/xspeed/?limit=100&mode=stop_on_copy&format=rss).

## Istoric modificări

#### [1.2.0] – 2026-08-24

**One command now measures your site, applies the settings that help, and undoes
anything that breaks. Four cache-poisoning routes are closed, importing from W3 
Total Cache carries settings across faithfully instead of a handful, and combined
JavaScript keeps running in the order the page expects.**

Security:
 – Fixed: A page rendered with a query string is no longer stored under
the bare URL’s cache key, where it would then be served to every visitor asking 
for the plain URL. – Fixed: Percent-encoded query keys can no longer poison the 
cache. Two spellings of the same key resolved to different cache keys, so a crafted
URL could seed the entry a normal request would later read. – Fixed: An allow-listed
tracking parameter no longer lets a crafted URL overwrite a cached page. – Fixed:
A search-results page no longer poisons the homepage through the cache key.

Optimization:
 – Added: `wp xspeed optimize` and the `optimize_site` AI tool make
the whole tuning loop one command. It measures the site, applies the recommended
settings one at a time, re-checks the page after each change, and reverts anything
that breaks it — then reports what it applied, what it undid and why, and what it
could not reach at all (page weight, hotlinked images, DOM size) rather than claiming
a win it did not make. – Added: Images hosted on another domain get their real dimensions
resolved, so lazy loading and the preloader no longer skip them.

Migration:
 – Fixed: Importing from W3 Total Cache brought across 8 of 510 settings.
Page cache, browser cache, object cache, exclusions and compression now map to their
xSpeed equivalents. – Fixed: Disabling W3 Total Cache’s master Minify switch is 
now respected. Its child CSS/JS settings stay populated while the master is off,
so reading them alone imported minification and combination as enabled on a site
that had deliberately turned them off. – Fixed: An encrypted Redis password that
cannot be read is now reported rather than silently dropped, so the object cache
no longer fails to connect with nothing on screen to explain why. – Fixed: An object-
cache endpoint written as `tls://host:port` imported a host that could never resolve.
The host and port are now imported and the dropped transport is stated, since xSpeed
connects over plain TCP. – Fixed: Compression enabled only for „other” file types
no longer imports GZIP as switched off. – Fixed: A partial import no longer switches
off the plugin it imported from, and no longer shows a finished „Imported” state
with no way to retry. – Fixed: WP Super Cache is detected and imported. Its settings
are stored under different keys than the importer looked for, so it reported nothing
to import. – Fixed: Page caching is actually enabled by an import that says it is.

Caching:
 – Fixed: Ignored query parameters are matched by whole name rather than
as substrings, so `utm_source` no longer matches an unrelated parameter that merely
contains it. – Fixed: Purging a URL on a non-standard port deleted nothing. – Fixed:
Query-string requests skip only the cache write, not the HTML transforms, so those
pages keep their minification and lazy loading.

CSS and JavaScript:
 – Fixed: Combined JavaScript is split by print group, so scripts
registered for the footer are no longer hoisted into the head and run before first
paint. – Fixed: The combined bundle is carried on an existing handle rather than
a new one, preserving inline payloads attached to it and the surrounding cascade
order. – Fixed: Configuration a page builder attaches late — Elementor writes `elementorFrontendConfig`
on `wp_footer`, long after combining runs — now prints ahead of the combined bundle
instead of behind it, so scripts no longer initialise against a config that does
not exist yet.

CDN:
 – Fixed: Changing the CDN URL clears Elementor’s render caches, which stored
the previous URLs in their markup.

Interface:
 – Fixed: The setup wizard and the ⌘K search palette no longer render
underneath the WordPress admin menu. – Fixed: Opening a panel no longer shifts the
page behind it when the dashboard is scrolled away from the top. – Fixed: The Apply
button on a Pro recommendation works instead of failing silently. Free and Pro name
their recommendations differently, and only Free’s were understood by the button
both of them use. – Added: The MCP server appears on the Overview as a capability
card, so an AI connection can be set up without hunting for the panel.

MCP server:
 – Fixed: OAuth discovery keeps working when another plugin claims `/.
well-known/`.

Server configuration:
 – Fixed: URL exclusions are mirrored into the generated nginx
snippet, so nginx no longer serves cached copies of pages xSpeed was told to exclude.

#### [1.1.8] – 2026-08-20

**Importing settings from another caching plugin no longer switches that plugin 
off without asking. Purging CSS or JavaScript now also clears the pages that link
them, a failed save no longer reports success, and another MCP plugin’s AI connections
keep working alongside xSpeed.**

**Migration:**

 * Fixed: Importing settings no longer deactivates the plugin you imported from 
   as an unavoidable side effect. The panel now offers both outcomes: “Import & 
   switch to xSpeed” and “Import settings only.” Previously, the only way to decline
   was Cancel, which also abandoned the import. WP-CLI and MCP did the opposite 
   and left both plugins running silently; all three now behave consistently.
 * Fixed: On a multisite network, a single site’s administrator can no longer switch
   off a network-activated caching plugin for every site on the network. WordPress
   refuses the same action from its own Plugins screen.
 * Fixed: Choosing to leave the other plugin running now raises a Health item naming
   the plugin and the risk, so two page caches competing for the drop-in don’t go
   unnoticed. It clears itself once the plugin is switched off.
 * Fixed: LiteSpeed’s exclusion lists are stored as JSON and were imported literally,
   causing imported exclusions to never match anything.

**Caching:**

 * Fixed: Purging CSS or JavaScript now also purges the pages that link those files.
   Cached pages could keep pointing to deleted combined assets, leaving them unstyled
   until another page purge occurred.
 * Fixed: A single POST request no longer keeps a visitor on the uncached path for
   the rest of their visit. Previously, one form submission or comment could cause
   every later page to be generated from scratch.
 * Fixed: Cache now purges when any module’s settings change, not only the cache
   module’s.

**CSS and JavaScript:**

 * Fixed: “Defer” and “Delay” now apply to the external script itself rather than
   an inline block queued before it, preventing execution order issues.
 * Fixed: Combined JavaScript keeps its declared dependencies, so scripts no longer
   run before the libraries they need.
 * Fixed: Inline style and script blocks are now minified, and anything deliberately
   skipped clearly indicates why.

**Settings and interface:**

 * Fixed: A failed save no longer shows the green “Settings saved” toast. The failure
   now stays visible instead of disappearing with the toast.
 * Fixed: Settings writes with keys that would be silently dropped are now refused
   instead of being accepted and discarded.
 * Fixed: A cleared URL field stays cleared instead of reverting to its previous
   value.
 * Fixed: Sub-sections of a disabled feature now collapse with it.
 * Fixed: A failing server snippet now identifies the problem instead of showing
   only a status code.

**MCP server:**

 * Fixed: xSpeed no longer answers another MCP plugin’s OAuth discovery URLs. Previously,
   its rule could match every .well-known discovery address on the site and return
   xSpeed’s details, preventing AI assistants from connecting correctly to other
   MCP plugins.

**Security:**

 * Fixed: The MCP server’s dynamic client registration is now bounded with limits
   on stored clients, redirect URIs, name and URI length, plus per-IP rate limiting
   on the registration endpoint.
 * Fixed: MCP and WP-CLI settings writes are now gated by the Pro license, matching
   the dashboard.

#### [1.1.7] – 2026-08-17

**On a multisite network, a change to one site no longer wipes every other site’s
cache. Cache cleanup no longer deletes stylesheets a live page is still using, and
a consent banner styled by another plugin stays styled.**

Caching:
 – Fixed: On a multisite network, each site’s cache is now cleared on its
own. Changing a setting, publishing a post, or clicking Purge on one site previously
deleted the cached pages of every other site on the network, so the cache was rarely
warm for anyone. – Fixed: Cache cleanup no longer deletes a combined stylesheet 
or script that cached pages are still pointing at. Those pages carried on being 
served while their CSS and JavaScript returned „not found”, leaving a site unstyled
and unresponsive — and invisible to the owner, whose own browser still held the 
old copy.

CSS and JavaScript:
 – Fixed: „Load CSS Asynchronously” no longer breaks a stylesheet
another plugin has already made non-render-blocking. A cookie-consent banner in 
that position loaded with none of its styling applied, in both logged-in and logged-
out states.

Settings:
 – New: List settings — cache exclusions, ignored parameters and the rest—
now show the stock value beside the box you edit, with a Reset action to restore
it. These are lists where one wrong entry can quietly stop a whole section of the
site being cached, and there was previously no way to see how far a list had drifted.–
Improved: The box you edit is now labelled, and Reset sits on it rather than beside
the defaults.

Accessibility:
 – Fixed: Hint text, captions and status pills now meet the AA contrast
minimum in light mode. The worst affected was the „Off” state pill — the only thing
communicating whether a feature was on.

#### [1.1.6] – 2026-08-13

**A search-results page could be cached and served as your home page. Combining 
CSS no longer strips a site’s styling, Pro settings can no longer be changed without
an active licence, and an AI assistant now reports this site’s tier and audits the
page you actually asked for.**

Security:
 – Fixed: A single search request could replace your cached home page.
With search caching on, one visit to a search URL was stored as the site’s front
page, so every later visitor — and search engines — were served those results instead.
The cached copy was handed out by the web server without WordPress running, so it
kept being served until the cache was cleared. Search pages are now kept out of 
that store entirely.

CSS and JavaScript:
 – Fixed: Combining CSS files could leave a site completely 
unstyled — no missing files, no errors, just the theme’s styling gone. WordPress
can inline a stylesheet it considers small, and doing so dropped the combined file
that every other stylesheet had been folded into. Combining now happens on the finished
page, after WordPress has made those decisions, so what you see in the browser is
what was combined. – Fixed: A stylesheet saved with a byte-order mark — common in
files edited on Windows — no longer breaks the styling of every file combined after
it. – Fixed: Fonts and stylesheets brought in by an `@import` rule are no longer
dropped when their file is combined with others.

AI assistants and WP-CLI:
 – Fixed: On a site without an active Pro licence, Pro
settings can no longer be changed through WP-CLI or an AI assistant. The dashboard
already showed them locked; four write routes and the image recommendation did not
enforce it, so a change made that way appeared to succeed. – Fixed: A refused change
is now reported as a refusal. It previously returned success over settings it had
not written, in both the REST response and the command’s exit code. – New: `run_score`
runs an external performance audit from any install, and honours the provider you
configured — asking for GTmetrix no longer silently runs PageSpeed Insights instead.–
Fixed: An AI assistant asking what this site is now gets the truth about its tier.
On a Pro site with a lapsed licence it previously reported the licence as active.–
Improved: A PageSpeed audit started from an assistant now measures the page you 
asked for. It previously measured the home page whatever URL was given, and reported
success.

Cache:
 – Fixed: Turning the page cache off, or uninstalling xSpeed, now removes
the `WP_CACHE` setting it added to your `wp-config.php`. It was only removed when
written exactly one way, so most sites kept a stale setting behind after the cache
was switched off — including after the plugin was deleted.

Compatibility:
 – Fixed: `wp xspeed purge` no longer clears the page cache on Apache
servers without mod_headers, where the cache could not be served from disk anyway.

Accessibility:
 – Fixed: Two buttons — the nginx snippet’s copy control and the 
MCP panel’s tool list — now show a focus ring again when reached by keyboard. They
suppressed the outline entirely, which left anyone navigating by Tab with no indication
of where they were.

Settings:
 – Improved: Duration fields now show what the number means in plain words—„
6 hours”, „1 day 12 hours” — for every value, not only round ones.

#### [1.1.5] – 2026-08-11

**AI assistants can change your settings again, and the cache preloader works on
sites without a readable sitemap.**

AI assistants and WP-CLI:
 – Fixed: An AI assistant can read and change your xSpeed
settings again. The two tools that do this were dropped from the catalog on every
site, so an assistant — including the one connected through the Hub — was told they
did not exist and could only fall back to raw commands. – New: `wp xspeed settings
list|get|update` — read and change any module’s settings from the command line, 
and from an AI assistant through the same commands. – Improved: Settings for Pro
features are no longer readable or writable over WP-CLI or an AI connection on a
site without an active licence. The dashboard already hid them; these two surfaces
did not. – Improved: Credentials still cannot be set from the command line or an
AI assistant. Asking to now names the field it refused rather than reporting success
over an unchanged key.

Preloading:
 – Fixed: On a site whose sitemap can’t be read, the preloader now warms
your most recent pages straight from your content instead of silently queueing nothing.
This affected two common setups that are not misconfigurations: sites discouraging
search engines (where WordPress disables the sitemap outright, standard on staging
and pre-launch sites), and SEO plugins that serve their own sitemap at a path we
were never told about. – Fixed: When a crawl can’t start at all, the preloader panel
now says „Couldn’t start” and names the reason, rather than reporting „Ready” over
an empty run. – Improved: The explanation appears while the crawl is running, not
only once it finishes — on a large site that is the difference between watching 
an unexplained crawl for hours and knowing why on the first tick. – Fixed: `wp xspeed
preloader status` no longer fails with an internal error after a crawl that ended
with nothing queued. An AI assistant asking why a preload failed now gets the actual
reason instead of a type error.

Branding:
 – Improved: New xSpeed Cache logo and wordpress.org banners.

#### [1.1.4] – 2026-08-09

**Stored credentials are now encrypted, exclusions are enforced by the server itself,
and the cache cleans up after itself.**

Security:
 – Fixed: Stored credentials — API tokens, keys, and object-cache passwords—
are now encrypted at rest and never returned in full by the dashboard, REST API,
or an AI assistant. They were previously readable in plain text by anyone who could
reach those endpoints. Existing values are encrypted automatically on upgrade; nothing
needs re-entering. – Improved: An AI assistant can no longer write credentials unless
you explicitly grant it that permission when connecting. – Improved: Cloudflare 
settings are verified when you save them, so a wrong token or zone is reported straight
away instead of failing silently on the next purge.

Caching:
 – New: Expired cache entries and orphaned minified assets are now collected
on a schedule, so the cache directory no longer grows without bound on a busy site.–
Fixed: Excluded cookies and bypassed user agents are now enforced on the fast path
the web server serves directly. Previously they applied only while a page was cold,
so a warm page could serve the shared anonymous copy to carts, members and bypassed
bots. – Fixed: Sites using TranslatePress now cache the translated page rather than
the untranslated one. – Improved: Response headers now distinguish a cache miss 
from a deliberate bypass, so a quick header check shows whether a page is about 
to be cached or was skipped on purpose. Previously both came back with no header
at all. – Improved: With debug mode on, a bypassed response also names which rule
skipped it — logged-in, excluded URL, query parameter, and so on. – Fixed: Cache
hits are now counted on every server, not only nginx, so Apache and LiteSpeed sites
no longer show a permanent 0% hit ratio. – Improved: The static-rewrite check now
reports a known blocker (such as Separate Mobile Cache) instead of a bare „inactive”,
and says the same thing in the dashboard, WP-CLI, REST and MCP. – Improved: The 
hit ratio now excludes 404s and bot traffic, and reports the origin only when a 
CDN sits in front — so the number reflects what your visitors actually experience.

Compression:
 – Fixed: GZIP is no longer reported as inactive when the check itself
couldn’t complete. A blocked loopback request is not evidence that compression is
missing, and telling you your server was misconfigured because we couldn’t reach
it was the bug. Only a check that positively proves GZIP is absent now warns.

Optimization:
 – Fixed: The CDN now serves CSS, JavaScript and fonts, not just images
from post content. Font files also get the CORS header they need when loaded cross-
origin. – Fixed: LCP preload now picks the largest image on the page instead of 
the first one, so the preload helps the image that actually decides your LCP score
rather than competing with it. – Fixed: Brotli is detected on nginx by asking the
server, so a host with ngx_brotli installed is no longer told to install it. A check
that can’t complete now says so rather than reporting Brotli as unavailable. – Fixed:
The Compression page no longer promises an nginx snippet that isn’t on it — it links
to the snippet instead, and the link is there whether or not compression is already
working.

Dashboard & Admin UX:
 – Fixed: Enter now inserts a newline in the „one per line”
settings fields (Excluded URLs, Excluded Cookies, and the rest). Typing a list previously
merged every line into one. – Fixed: The Setup Wizard starts from your site’s real
settings, so re-running it and pressing Apply no longer silently switches off options
you had turned on. A cache expiry that isn’t one of the presets is shown as its 
own option and named before anything overwrites it. – Fixed: The Recent activity
feed shows setting names as they appear on screen instead of internal storage keys,
and no longer writes connection details or account identifiers into the log. – Fixed:
Links to Tools  Migration now open that page rather than dropping you on the Overview.–
New: Settings fields can now link to their documentation; the PageSpeed API key 
field points at the setup guide. – Fixed: External Score now lives in one place,
under Health & insights. It previously rendered a second copy of the same settings
and run history inside the Health page’s PageSpeed tab.

AI & agents:
 – Fixed: A read-only MCP connection can now read status through every
per-command tool. It previously refused the whole tool if any of its actions could
write, so an assistant with read-only access could not inspect state at all. Write
actions are still refused, and an unrecognised action is refused rather than allowed.

#### [1.1.3] – 2026-08-05

**A redesigned dashboard, a homepage cache-poisoning fix, and caching that survives
a plugin update.**

Security:
 – Fixed: A crafted URL could poison the homepage cache, causing search-
results content to be served to every visitor from the cached homepage.

Caching:
 – Fixed: Updating the plugin no longer silently disables page caching 
until the next admin login — the drop-in is restored on activation. – Fixed: Cache
hits served statically by Apache are now reported and counted, instead of showing
a permanent 0% hit ratio. – Improved: Health now explains when the fast static-cache
path is unavailable because the server lacks mod_headers, and what to change, instead
of suggesting a fix that cannot work. – Improved: Fresh installs now start on the
recommended profile, so sites set up by WP-CLI or a skipped wizard get compression,
browser caching, and minification by default.

Dashboard & Admin UX:
 – New: Redesigned dashboard — new typography, colour system,
navigation rail, and top bar, with grouped navigation and a consistent module-settings
layout. – New: Command palette for jumping to any setting. – New: A dedicated Pro
page describing what each Pro feature does. – New: „Avg saved” card on the Overview,
showing the real per-request time saved from your latest benchmark. – Improved: 
License, Branding, and Multisite are now cards of their own, so the license form
is one click away instead of three. – Improved: Fonts now lives in one place under
Optimization, and the page that used to host it is now „Media Optimization”. – Fixed:
Recommendation links on the Overview now open the screen they point at, and „Get
the snippet” opens the snippet. – Fixed: The brand mark no longer renders black 
against the dark rail in light mode.

Optimization:
 – New: Delay JavaScript now also covers scripts printed directly 
into the page — analytics, pixels, and chat widgets that previously bypassed it 
entirely. – New: The delay-JavaScript failsafe timer is now configurable, so it 
can be tuned or switched off instead of firing mid-measurement. – Fixed: Delayed
scripts are now matched correctly when minification rewrites their URLs. – Fixed:
HTML minification now says when it is deliberately suppressed by debug mode, instead
of reading as on while changing nothing.

AI / MCP:
 – New: Stored PageSpeed Insights and GTmetrix history is now readable
from your AI assistant. – Fixed: Removed fifteen duplicate tools that shadowed the
typed ones, trimming the tool list. – Fixed: An unrecognised migration command now
reports an error instead of silently succeeding.

#### [1.1.2] – 2026-07-30

**A new Overview dashboard, click-to-play video embeds, and a full audit trail for
AI actions.**

Dashboard & Admin UX:
 – New: Overview screen is now the landing page, showing cache
status, key stats, recommendations, and recent activity at a glance. – New: PageSpeed
and GTmetrix scores on the dashboard. – New: Stat cards open into drill-downs so
you can see what is behind each number. – Improved: Notice buttons now take you 
straight to the control they refer to. – Improved: Deactivating the plugin now asks
for feedback, so problems reach us instead of going unreported.

Optimization:
 – New: Click-to-play facade for YouTube and Vimeo embeds — the player
loads only when a visitor presses play, cutting page weight. – Fixed: Minified HTML
no longer loses the space between inline elements, which could run words together.

AI / MCP:
 – New: Audit trail recording every AI tool call, with an activity panel
showing what was run and whether it changed anything. – New: Every xSpeed CLI command
is now available as its own MCP tool. – Fixed: AI tool calls failed with a server
error instead of running. Every tool works again.

Onboarding:
 – Improved: Account connection moved to the final step, so caching 
is set up before you are asked to sign in. – Fixed: Returning from account setup
now resumes on the right step. – Fixed: Each „next step” card in the wizard now 
goes to its own destination.

Health:
 – Fixed: No longer tells you to configure your server when the check could
not reach a verdict.

#### [1.1.1] – 2026-07-28

**Actionable dashboard insights, richer AI tooling, and smarter health detection.**

Dashboard & Admin UX:
 – New: Impact hero showing the real-world speed gain your
cache is delivering, with a one-click next-best-action to apply the top recommendation.–
New: Benchmark history and daily hit-ratio trend charts, annotated with the setting
changes that moved them.

AI / MCP:
 – New: Purge a single URL, read site health, test the object cache connection,
and verify Cloudflare credentials directly from your AI assistant.

Health:
 – New: Detects third-party cookies that would poison the page cache and
names the plugin responsible. – New: Warns when the cache lifetime is shorter than
the preloader interval, which would leave pages permanently uncached.

Optimization:
 – New: Delay individual scripts by name instead of all-or-nothing,
so you can defer heavy third-party embeds while leaving critical scripts alone. –
Fixed: Lazy-loaded images now get correct width and height even when the theme strips
WordPress’ image size class, preventing layout shift.

Caching:
 – Improved: Benchmark now reports the real compressed transfer size alongside
the uncompressed page weight.

Object Cache:
 – Fixed: A failed write to Redis or Memcached no longer leaves a 
stale value served from the backend.

#### [1.1.0] – 2026-07-22

**New xSpeed Hub — connect one AI assistant to manage caching across all your sites.**

xSpeed Hub:
 – New: „xSpeed Hub” tab in the MCP Server panel — connect this site
to your xspeedcache.com account so a single AI connection can manage caching across
all your WordPress sites. – New: Setup wizard now opens with a „Connect your free
account” step — create a free account in one click right after install, so one AI
connection can manage caching across every site. Skippable; caching works fully 
without an account. – New: One-click „Connect via xspeedcache.com” — sign in and
approve, no token to copy. – Improved: The connect flow carries your admin email
so account setup is one click for new users.

Dashboard & Admin UX:
 – Improved: Benchmark and AI audit now sit above the cache
settings for a clearer, action-first layout. – Improved: The dashboard menu now 
reads „xSpeed Cache”.

#### [1.0.9] – 2026-07-16

**Redesigned dashboard navigation, improved settings experience, and caching reliability
fixes.**

Dashboard & Admin UX:
 – New: Redesigned settings navigation with dedicated pages
for Optimization, Cache, Compression, Cloudflare, Health, and AI & Agents. – New:
Branded loading skeleton for a smoother dashboard loading experience. – Improved:
Clearer and searchable settings navigation. – Improved: Enhanced search with tab
and section-level results. – Improved: Cleaner Free dashboard with streamlined Pro
sections.

Optimization:
 – Fixed: Improved CSS combination compatibility with page builders.–
Fixed: Resolved frontend rendering issues on block themes.

Caching:
 – Fixed: Admin bar cache purge issue. – Fixed: Hit counter reset reliability.

#### [1.0.8] – 2026-07-14

**MCP support for AI assistants, LCP optimization, and admin experience improvements.**

AI / MCP:
 – New: MCP server support for Claude and other MCP-compatible AI assistants.–
New: Secure OAuth 2.1 connection for remote AI assistants. – New: MCP dashboard 
with available tools and permissions.

Performance:
 – New: Resource Hints with LCP image preload and font preconnect. –
Fixed: Improved LCP image loading by preventing lazy loading on the hero image.

Dashboard & Admin UX:
 – New: Settings shortcut from the WordPress Plugins page.–
Improved: Updated admin menu organization and dashboard navigation. – Improved: 
Better Pro license messaging and settings search experience. – Fixed: Checkbox rendering
in both light and dark mode.

Reliability:
 – Fixed: Improved cache permission handling on non-NGINX servers.

#### [1.0.7] – 2026-07-05

**Improved reliability, granular cache management, Redis compatibility, and asset
optimization fixes.**

Caching:
 – New: Granular cache purge options for Page/Static, CSS/JS, Object Cache,
and REST Cache. – Fixed: Improved compatibility with previously installed caching
plugins. – Fixed: Purge All now properly clears optimized assets, object cache, 
and triggers CDN/edge purges.

Object Cache:
 – Fixed: Redis 6+ ACL compatibility for managed hosting environments.–
Improved: Object cache write verification for better reliability. – Improved: Site-
specific object cache flushing for shared Redis environments. – Improved: Persistent
object cache group flushing.

Asset Optimization:
 – Fixed: Combined CSS now preserves inline styles and stylesheet
order. – Fixed: Combined CSS files are regenerated correctly after cache purge. –
Fixed: Relative asset paths are preserved in optimized CSS.

Dashboard & Admin UX:
 – Fixed: Dashboard layout issue with large WordPress admin
menus. – Fixed: Admin menu and toolbar overlay issues. – Fixed: Pro sidebar item
ordering.

Migration:
 – Fixed: Mobile cache migration compatibility for NGINX static cache.

#### [1.0.6] – 2026-06-25

**New caching capabilities, smarter settings, Pro cache warming, and major reliability
improvements.**

Caching:
 – New: REST API response caching with per-route TTL. – New: Feed, search
results, and 404 page caching. – New: `xspeed_should_cache` filter for advanced 
cache control. – New: Maintenance-aware cache serving to prevent stale maintenance
pages. – Improved: Feed handling with conditional GET (304 Not Modified) support.–
Fixed: Cache metadata handling for feeds, 404 pages, and content types. – Fixed:
Automatic cache purging for user and taxonomy changes. – Fixed: Versioned cache 
drop-in to ensure updates are applied correctly.

Settings:
 – New: Conditional settings with dependency support (AND/OR logic). –
Fixed: Preserved custom option keys during schema-driven saves. – Fixed: Image URL
validation for media fields.

White Label:
 – Fixed: Footer credit and Help & Support link controls. – Fixed: 
Fallback to the default logo when a custom brand logo is unavailable.

Migration:
 – New: One-Click Profiles and Save & Share with an improved import experience.–
Fixed: Import now counts and migrates only enabled source settings.

Reliability:
 – Fixed: Improved REST API error handling to prevent broken JSON responses.

Admin UX:
 – New: Opt-in usage analytics (WP Insights). – Improved: Sidebar navigation,
conditional Pro settings, …

## Meta

 *  Versiunea **1.2.0**
 *  Ultima actualizare **Acum 3 zile**
 *  Instalări active: **50+**
 *  Versiune WordPress ** 6.0 sau mai recentă **
 *  Testat până la **7.1**
 *  Versiune PHP ** 7.4 sau mai recentă **
 *  Limbă
 * [English (US)](https://wordpress.org/plugins/xspeed/)
 * Etichete
 * [caching](https://ro.wordpress.org/plugins/tags/caching/)[minify](https://ro.wordpress.org/plugins/tags/minify/)
   [optimization](https://ro.wordpress.org/plugins/tags/optimization/)[performance](https://ro.wordpress.org/plugins/tags/performance/)
   [speed](https://ro.wordpress.org/plugins/tags/speed/)
 *  [Vizualizare avansată](https://ro.wordpress.org/plugins/xspeed/advanced/)

## Evaluări

 5 din 5 stele.

 *  [  6 5 – recenzii (stele)     ](https://wordpress.org/support/plugin/xspeed/reviews/?filter=5)
 *  [  0 4 – recenzii (stele)     ](https://wordpress.org/support/plugin/xspeed/reviews/?filter=4)
 *  [  0 3 – recenzii (stele)     ](https://wordpress.org/support/plugin/xspeed/reviews/?filter=3)
 *  [  0 2 – recenzii (stele)     ](https://wordpress.org/support/plugin/xspeed/reviews/?filter=2)
 *  [  0 1 – recenzii (stele)     ](https://wordpress.org/support/plugin/xspeed/reviews/?filter=1)

[Recenzia ta](https://wordpress.org/support/plugin/xspeed/reviews/#new-post)

[Vezi toate recenziile](https://wordpress.org/support/plugin/xspeed/reviews/)

## Contributori

 *   [ WPDeveloper ](https://profiles.wordpress.org/wpdevteam/)
 *   [ M Asif Rahman ](https://profiles.wordpress.org/asif2bd/)
 *   [ Akash Mia ](https://profiles.wordpress.org/seakashdiu/)
 *   [ Nahid Hasan ](https://profiles.wordpress.org/tushar284/)
 *   [ Abu Hurayra ](https://profiles.wordpress.org/hurayraiit/)

## Suport

Ai ceva de zis? Ai nevoie de ajutor?

 [Vezi forumul pentru suport](https://wordpress.org/support/plugin/xspeed/)