Works with your stack
Cookie consent for Swift Performance Lite
the server sends it too
Swift Performance Lite caches and merges scripts. One of its options replaces the Google tag with its own script and sends the visit to Google Analytics from your server. The plugin is no longer maintained.
By Swift Performance · swiftperformance.io · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
Swift Performance Lite
WordPress plugin
- Tested version
- 2.3.7.5
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 2.3.7.5 tested
- Active installs
- 6,000+
What Swift Performance Lite adds to your visitors’ browser
No trackers In our test of Swift Performance Lite 2.3.7.5 on 7 November 2026, the plugin itself added no tracker and no cookie. What you place in your pages with it, such as a video or a map, still counts.
What matters for consent with Swift Performance Lite
Bypass Google Analytics
With this option on, Swift sets a cookie of its own and your server sends the visit to Google Analytics. Cookie Rocks holds Swift’s script, but no banner can hold what your server sends. Turn the option off and use the normal Google tag.
Merged scripts
Swift leaves scripts held by a banner in place. Its setting to keep third-party scripts out of the merge has no effect, so an unknown tracker can lose its original address in the merged file.
The banner runs first
Cookie Rocks marks its own tags so Swift does not merge or delay them, and clears Swift’s cache when its settings are saved.
What our tests found on Swift Performance Lite
Sent from your server · Swift Performance LiteSwift Performance Lite sends visits to Google Analytics from the server
setting “Bypass Google Analytics” · by default: off
Bypass Google Analytics swaps the Google tag for its own script, which sets spcid for 180 days. Cookie Rocks 2.5.1 holds that script; the server sending cannot be held by any banner.
What to do: Turn "Bypass Google Analytics" off and use the normal Google tag. The plugin is no longer maintained.
Seen in our tests, 17 October 2026, Swift Performance Lite 2.3.7.3.
Full detail
With Bypass Google Analytics on, Swift Performance Lite replaces the Google tag with its own script: it sets the cookie spcid for 180 days on the first page and the site's server then sends the visit to Google Analytics. Cookie Rocks 2.5.1 holds that script; the server sending itself cannot be held by any banner.
Depends on a setting · Swift Performance LiteA Swift Performance Lite setting has no effect because of a misspelled name
setting “Exclude 3rd Party Scripts (Merge Scripts)”
The option that keeps third-party scripts out of Merge Scripts is never read. External scripts are served from the merged file, so a tracker a banner does not recognise loses its address.
Read in its code, 16 October 2026, Swift Performance Lite 2.3.7.3.
Full detail
In Swift Performance Lite, the setting that keeps third-party scripts out of Merge Scripts is saved as merge-scripts-exlude-3rd-party but read as merge-scripts-exclude-3rd-party, so it has no effect: external scripts are downloaded by the server and served from the site's merged file, and a tracker a banner does not recognise loses its original address in the page. Its page cache key ignores cookies and Set-Cookie headers are not cached.
Good to know · Swift Performance LiteSwift Performance Lite can merge a banner's scripts; Cookie Rocks 2.5.1 opts out
Held scripts stay in place, but a banner's own scripts are merged and may run only at the first gesture. Cookie Rocks 2.5.1 marks its tags data-dont-merge and clears Swift's cache on save.
Read in its code, 16 October 2026, Swift Performance Lite 2.3.7.3.
Full detail
Swift Performance Lite opens its output buffer when plugins load, before a banner's template_redirect buffer, so it receives the page already rewritten. Merge Scripts only merges scripts with no type or a JavaScript type, so scripts held as text/plain stay in place; the only exclusion it reads is data-dont-merge. Without it, a banner's own scripts are merged into the footer file and, with Delay Async Scripts, run only at the first gesture. Cookie Rocks 2.5.1 puts data-dont-merge on its tags and clears Swift's cache when its settings are saved.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- Swift Performance Lite 2.3.7.5, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- Settings of the test: Default settings after activation.
- Last run: Swift Performance Lite 2.3.7.5 on 7 November 2026, with WordPress 7.1.3.
Light as a pebble
11.43 kB once, 1.00 kB per page. Measured, not promised.
lighter than the font on this page*
Every kilobyte costs your visitors time and costs you Core Web Vitals. Cookie Rocks adds 11.43 kB to the first page a visitor opens, then 1.00 kB to each page after that, because its files stay in the browser cache. It calls no outside server and never shifts your layout.
11.43 kB First visit, in total
1.00 kB Each next page
7.74 kB JavaScript, first visit
3.48 kB Stylesheet, first visit
0 Requests to other servers
0 Layout shift caused
* The font on this page is Inter, compressed and cut down to the Latin alphabet. It still weighs 26.23 kB.
Page cache
Other plugins of the same kind.
Questions
Should I keep Swift Performance Lite?
It is no longer maintained. If you keep it, leave Bypass Google Analytics off.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For Swift Performance users
Merged scripts, held trackers.
bypass ga off
Every feature of the complete plugin for 30 days, no card.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.