Table of content

DJIA Cache – Warm Cache Tab

The Warm Cache tab controls how DJIA Cache preloads pages before users open them.
This improves perceived performance by preparing cached pages in advance.

Warm cache works by prefetching links when users hover or touch them, so the next page loads almost instantly.

This feature works site-wide and is compatible with all major page builders, including Bricks Builder.

Hover Warm Cache (Prefetch)

Hover warm cache preloads linked pages when a user hovers over or touches a link.

Instead of waiting for the user to click, DJIA Cache starts loading the page in the background.

Benefits:

  • near-instant navigation
  • improved user experience
  • faster page transitions
  • reduced server spikes

Enable hover/touch warmup

Enables warm cache on:

  • hover events (desktop devices)
  • touchstart events (mobile devices)

This works site-wide for all internal links.

Purge page cache on login / logout

Automatically purges page cache when a user logs in or logs out.

This is recommended when logged-in caching is enabled, as it prevents cached HTML from mixing between guest and logged-in sessions.

Benefits:

  • prevents cache conflicts
  • ensures correct content visibility
  • avoids serving guest HTML to logged-in users

Warm for logged-in users

Also warms cache for logged-in users.

⚠ Enable this only if your page cache system separates guest and logged-in cache buckets.

If guest and logged-in caches are not separated, this may lead to incorrect cached content.

Warm mode

Defines which links will be prefetched.

Available options:

All internal links (site-wide)

Prefetches all internal links on the page.

This provides the fastest navigation but generates more background requests.

Only listing / query loop links

Prefetches links only inside listing components such as:

  • post grids
  • product loops
  • query loops
  • archive listings

This reduces the number of background requests while still improving navigation inside content listings.

Max warmups per page view

Defines the maximum number of prefetch requests allowed per page view.

Example:

10

This prevents excessive background requests and keeps resource usage under control.

Exclude patterns

Defines URL patterns that should not be warmed.

Each pattern should be placed on a separate line.

Example:

/cart/
/checkout/
/my-account/

Any URL containing these patterns will be excluded from warm cache.

This is useful for excluding:

  • WooCommerce checkout pages
  • account pages
  • dynamic or private pages