Skip to main content

Feed Server Abort Timeout

Overview​

The Feed Server Abort Timeout improves page load performance by aborting slow feed requests on the server so they don't block server-side rendering (SSR). When a feed exceeds the configured timeout:

  • The feed is aborted on the server
  • The page continues loading immediately
  • The feed is loaded from the client afterward (same behavior as enabling “Load feed from the client” on the component)

This prevents a single slow feed (or multiple slow feeds) from delaying the entire page.

How It Works​

If a feed request takes longer than the defined timeout, the server aborts loading that feed during SSR. After the page loads, the client fetches the feed normally.

Configuration and testing​

  1. Open the Caching plugin.
  2. Enable “Enable Feed Server Abort Timeout”.
  3. Set the timeout value (for example, 1000–1500 ms).
  4. Load a page that contains multiple feeds, including a slow feed.

Expected result:

  • Page loads faster
  • The slow feed appears shortly after, fetched from the client

Choosing the Right Timeout​

  • Too low (e.g. 100 ms): may abort too many feeds and worsen overall performance
  • Too high (e.g. 5000 ms): minimal performance benefit

Recommended values:

  • Start with 1500 ms
  • Reduce to 1000 ms if needed
  • Do not go below 500 ms
  • 2000–3000 ms is reasonable for customers without performance issues

Important Notes (Caching)​

We use multiple caching layers (Redis, CDN, browser). The feature has the biggest impact on the first page load; subsequent loads are usually faster due to caching.

To test accurately:

  • Disable browser cache
  • Be mindful of CDN/Redis effects
  • Testers should understand basic caching behavior and how to disable browser cache during testing