| 开发者 |
asif2bd
wpdevteam seakashdiu tushar284 hurayraiit alimuzzamanalim |
|---|---|
| 更新时间 | 2026年11月12日 21:25 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp xspeed purge, wp xspeed preloader status, wp xspeed score run, wp xspeed optimize and wp xspeed settings list|get|updateoptimize_site tool measures the site, applies recommended settings one at a time, re-checks the page after each change and reverts anything that breaks it/cart, /checkout and /my-account?ver= query strings from asset URLs (generated files under wp-content/uploads keep theirs, so a page-builder or consent-banner edit still reaches returning visitors)font-display: swap so text is visible immediately while fonts loadCache-Control and Expires headers for images, CSS and JS, with no manual configuration/wp-json/xspeed/v1/, developer filters (xspeed_skip_minify, xspeed_strip_asset_version, xspeed_cache_skip_for_post, xspeed_cache_expiry_for_post), WP_DEBUG awareness, and a React 18 and TypeScript admin UI.
Agencies: Use the xspeed_branding filter to white-label the dashboard for clients.
Private By Default
xSpeed Cache stores no IP addresses and sets no tracking cookies. Out of the box, the only request it makes is a check to your own site's home URL to confirm GZIP is active, at most once an hour.
Usage analytics is optional and off by default. If you turn it on in the setup wizard or in xSpeed Cache → Settings → Privacy & usage data, it sends your email address and display name, your site's setup and which xSpeed Cache features you use. Page content is never sent. See the External services section below for every service the plugin can contact.
If xSpeed Cache makes your site faster, please leave a review on WordPress.org.
xspeed folder to the /wp-content/plugins/ directory, or install the plugin through the WordPress Plugins screen directly.Yes. xSpeed Cache works on Apache, nginx, LiteSpeed, IIS and any standard PHP host. GZIP auto-configures on Apache and LiteSpeed, and a ready-to-paste config snippet is provided for nginx and IIS.
No. xSpeed Cache detects the LiteSpeed Cache server module and steps back to avoid conflicts.
Yes. Logged-in customers and checkout pages are never cached, and you can exclude specific URLs such as /cart, /checkout and /my-account.
Yes. Each site in the network gets its own cache and settings.
Not exactly. A WordPress MCP adapter usually exposes core WordPress data. The xSpeed Cache MCP server exposes the performance tools this plugin owns, such as cache purging, preloader status, score runs and settings reads and writes, so an assistant works on speed rather than on content.
Yes. A WordPress MCP Claude connection uses OAuth discovery, and the MCP server appears on the Overview as a capability card so you can set it up without hunting for a panel. Read-only connections stay read-only.
That is for you to judge, but here is the honest basis for comparison. The static-file rewrite path serves cached pages before PHP loads, across Apache, nginx and LiteSpeed, which most free plugins do not do. Object caching, CDN support and database cleanup are included rather than reserved for a paid tier.
In most cases yes. Page caching, minification, GZIP, lazy loading, font optimization, browser caching, object caching, WordPress CDN support and database cleanup are all in one plugin, so you are not stacking a WordPress page speed plugin on top of a cache plugin on top of a database tool.
It targets the parts a plugin can influence. The static cache improves server response time, the LCP preload picks the largest image on the page rather than the first, lazy loading defers offscreen media, and the automatic Cumulative Layout Shift fix stops the layout jumping. Page weight and DOM size are reported to you, since only a person can fix those.
The MCP server lets an AI assistant connect to your site and use the same tools the dashboard uses, such as purging cache, checking preloader status, running a score and reading or updating settings. Read-only connections stay read-only, and credentials cannot be written unless you explicitly grant that permission when connecting.
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.
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.
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.
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.
By default, no. The only request is a check to your own site's home URL to confirm GZIP is active. Everything else, including usage analytics, speed tests, xSpeed Scan, Cloudflare and click-to-play video posters, runs only after you turn it on or press a button. Each service is listed in the External services section.
:443 in the host, now get the cached file instead of going to PHP. Copy the updated nginx snippet to apply it.xspeed_preloader_request_timeout.
Object Cache:
wp xspeed objcache status reports how that went.
xspeed_cache_write_hold).fetchpriority="high" and is not lazy-loaded.