Caching plugin data paths

Where WordPress caching plugins keep or send visitor traffic

Caching plugins promise speed. Some keep cached pages on your WordPress host. Others route visitor assets through an outside content delivery network (CDN). This table summarizes the documented setups below. Your settings can change where requests go.

Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group caching plugins

We compare the caching setups named below. Local cache keeps files on your host. CDN and accelerator add-ons send visitor asset requests through an outside network. Visitor-page vs admin-only scope is called out per row. We have not tested when requests start relative to cookie consent or assessed how long logs are kept.

Caching and CDN plugins

No paid placement. On your server first, then outside networks, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorReceiving domainsVisitor page scopeHow long data is keptBefore consentLinksSource
Cache Enabler (local page cache)

WordPress.org listing: Cache Enabler writes static HTML files on your WordPress host for visitor pages. The documented default path does not require an outside CDN.

On your serverNone in the documented default path.Visitor pagesNot assessedNot tested
  • None
WP Super Cache (local page cache)

WordPress.org listing: WP Super Cache stores static HTML on your WordPress host to serve visitor pages faster. The default page-cache path does not require an outside CDN. Optional CDN settings you configure yourself are outside this row.

On your serverNone in the documented default path.Visitor pagesNot assessedNot tested
  • None
Jetpack (Site Accelerator on)

Jetpack Site Accelerator docs: when the feature is on, images and static assets can be served from wp.com CDN hosts (including i*.wp.com). Visitor asset requests then reach Automattic infrastructure. Jetpack features you leave off are outside this row.

Outside CDN / acceleratori0.wp.com, i1.wp.com, i2.wp.comVisitor pagesNot assessedNot tested
  • None
WP Rocket (RocketCDN enabled)

RocketCDN docs: when RocketCDN is enabled, fonts, images, JavaScript, CSS, and other cacheable assets are served from a delivery.rocketcdn.me CNAME so visitor asset requests reach the RocketCDN network. WP Rocket states the core plugin alone does not add cookies; this row covers the RocketCDN setup only.

Outside CDN / acceleratordelivery.rocketcdn.meVisitor pagesNot assessedNot tested
  • None
Breeze

We have not reviewed this plugin's caching data path yet.

Not reviewedDocumentation not reviewed yet.Not reviewedNot assessedNot tested
  • None
Cloudflare

We have not reviewed this plugin's caching data path yet.

Not reviewedDocumentation not reviewed yet.Not reviewedNot assessedNot tested
  • None
Hummingbird

We have not reviewed this plugin's caching data path yet.

Not reviewedDocumentation not reviewed yet.Not reviewedNot assessedNot tested
  • None
LiteSpeed Cache

We have not reviewed this plugin's caching data path yet.

Not reviewedDocumentation not reviewed yet.Not reviewedNot assessedNot tested
  • None
SiteGround Optimizer

We have not reviewed this plugin's caching data path yet.

Not reviewedDocumentation not reviewed yet.Not reviewedNot assessedNot tested
  • None
W3 Total Cache

We have not reviewed this plugin's caching data path yet.

Not reviewedDocumentation not reviewed yet.Not reviewedNot assessedNot tested
  • None

What this table does and does not prove

This table describes the named caching setups. It does not show what loads on your site. Local cache and outside CDNs can both apply. We have not tested consent timing, and we have not assessed how long logs are kept. The site scan linked below does not read cache files on your server.

Documentation snapshot: Sep 29, 2026. Sources are linked in each reviewed row.

Scan your site for third-party requests

/wp-caching-plugin-privacy