Caching and page speedPro
Check which Swift Performance edition your site runs
GoBuildWP treats Swift Performance and Swift Performance Lite as two drivers, swift_performance and swift_performance_lite, which share one option prefix and one purge method. A Swift Performance MCP session can clear everything through Swift_Performance_Cache::clear_all_cache() and read or write the plugin's own rows, but nothing is mapped onto GoBuildWP's shared cache vocabulary, because the option layout is not stable across the two editions.
GoBuildWP Pro is required. Supported Swift Lite and Pro use separate driver keys and plugin folders; check the actual detected registration.
swift_performance / swift_performance_lite- Layer
- page
- Declared purge scopes
all- Shared keys
- None
- Detected by
- swift-performance / swift-performance-lite plugin folders
Installed class, method or listener checks and per-layer results determine whether a purge ran. Neither a declaration nor a returned ran flag proves public freshness.
- Edition
- Pro
- Abilities
- 16
- Requires
- WordPress 6.9+, PHP 8.0+
Before changing cache settings, inspect captured drivers and not_captured. After reverting, inspect restored, deleted, not_restored, verified and purged_layers. Use a separate cache-purge result when you need details for each layer. Storage verification checks captured values; it does not establish functional recovery or public freshness. Revert may overwrite later settings, and vendor configuration regeneration or a re-save can still be required.
Check each measurement run’s fetched_via before treating it as public-path evidence. cache-verify-in-browser supplies checks and does not operate a browser. Automatic purge coalesces targets within the request and runs on shutdown; it is not necessarily one immediate flush per call. Verify generated files, object/page/edge caches and actual visitor behavior separately.
Abilities
Swift under each cache ability
| Ability | What it does here | Undo and limits |
|---|---|---|
cache-check-setup | Names swift_performance or swift_performance_lite depending on which folder is active, with purge_scopes.all true when Swift_Performance_Cache and its clear_all_cache method exist. | Use the driver key it reports. Asking for swift_performance on a Lite site is refused as no matching active layer. |
cache-purgecache-warm | clear_all_cache() for every scope, with widening reported. The hook guessed in an earlier GoBuildWP build existed in neither edition; the static method is shared by both. Warm then refills the pages you list. | No single-page purge. Swift's own automatic clear on post update covers the post and its archives, according to its documentation. |
cache-get-settingscache-set-native | Read and change swift_performance rows by exact name; confirm=true is required and the stored type is kept. | GoBuildWP does not know what any field inside Swift's rows means, so the user has to identify the setting. |
cache-set-settingscache-apply-presetcache-list-presets | Report every key unsupported for both editions. | Unmapped by design, not by oversight. |
cache-list-actionscache-run-action | Declare nothing for Swift, so its database optimiser and critical-CSS generation are not run through GoBuildWP. | Run them from Swift's dashboard. |
cache-begin-experimentcache-revert-experimentrollback-change | Restore swift_performance rows exactly and purge. | Merged and minified files already written to the cache folder are replaced only as pages rebuild. |
cache-measure-pagecache-verify-in-browser | Measure the page and hand back browser checks, which matter most after a merge change. | Swift's documentation suggests disabling merge scripts and styles when a site breaks. Browser checks provide clues and a way to compare the change; they do not establish merging as the cause on every installed stack. |
Reference: /docs/reference/cache
Shared cache module; do not add this count across drivers. Edition and effect labels describe the source catalogue. The installed schema, dependency versions, licence, WordPress capability, safety profile and per-ability policy determine availability; labels alone do not prove confirmation or recovery.
Worked example
Recover a slider broken by script merging
Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.
The slider works again on a freshly cached page, and rollback-change can restore the earlier row if needed. GoBuildWP cannot identify Swift's merge field on its own, so the step that picks it depends on the user.
The shared cache abilities form a common interface across cache plugins, not all Swift functionality. Preserve other array values in the before/after slider test, inspect actual interaction after warm and revert if the result is inconclusive.
Since I turned on script merging in Swift, the home page slider is broken. Help me confirm it and undo it.
wppilot/cache-verify-in-browserReadReturns browser checks for the home page; run in a real browser, a console error from the merged script points at merging.
wppilot/cache-get-settingsReadDriver swift_performance (or swift_performance_lite) with include_native lists the rows so the user can point at the merge setting.
wppilot/cache-set-nativeConfirm firstWith confirm=true, writes the row with merging off; the ledger keeps the before-image and the layer is cleared afterwards.
wppilot/cache-warmWriteRequests the home page so an unmerged copy is cached.
A suggested sequence from the ability reference, not a recorded run.
Data model
Two editions, one prefix
Swift caches pages, including AJAX and dynamic requests, merges and minifies CSS and JavaScript, generates critical CSS, optimises the database and organises plugins; the Pro edition adds the Compute API, an image optimiser, remote cron and white-labelling. Its cache sits under wp-content/cache/ by default, a location Pro can move with SWIFT_PERFORMANCE_CACHE_BASE_DIR, and SWIFT_PERFORMANCE_DISABLE_CACHE switches caching off.
Both editions store options whose names start with swift_performance. GoBuildWP tells them apart by plugin folder, swift-performance or swift-performance-lite, and gives each its own driver key, but the rows each may touch are identical. When a row holds an array, the value you send replaces the entire array, so read it in full and send it back with only the one field changed.
Because no option contract holds across editions, GoBuildWP will not claim that any Swift key means the same as a WP Rocket or LiteSpeed key. Presets and risk tiers therefore never touch Swift.
Option name prefixes
swift_performance
No stable option contract across its editions, so nothing is mapped. Its option rows are readable and writable by name.
Limits
Swift limits
- No canonical keys and no presets for either edition.
- Purging is all-or-nothing through clear_all_cache().
- SWIFT_PERFORMANCE_DISABLE_CACHE and the cache path are constants, outside any ability.
- Row writes are undoable with rollback-change; a clear is not.
Questions
Swift Performance questions
Does GoBuildWP support Swift Performance Lite as well as Pro?
Yes. Each has its own driver, swift_performance_lite for Lite, and both clear through the same Swift_Performance_Cache class.
Can the agent clear only one page in Swift?
No. Every purge becomes clear_all_cache(); Swift's own clearing on post update is the targeted path.
How do I stop Swift caching if the site breaks?
Swift documents the SWIFT_PERFORMANCE_DISABLE_CACHE constant, and suggests disabling merge scripts and styles first when a layout breaks.
Why are presets unavailable for Swift?
Its option layout differs between editions, so GoBuildWP will not map any Swift key onto the shared vocabulary that presets rely on.
Where these facts come from
GoBuildWP behaviour is taken from the plugin source and the ability reference; third-party details from the vendor documentation below, checked by the GoBuildWP team.
- Swift Performance Lite on WordPress.org
- Swift Performance: cache path
- Swift Performance: constants
- Swift Performance: clear cache
Swift Performance is a separate product; no partnership or endorsement is implied.