Skip to main content

Request to Increase Cache Headers for Performance

Kiwi Size Chart & Recommender💡 Feature Request

Hi Kiwi Sizing Team,

We're using your app on thedressoutlet.com and noticed that your static assets have very short cache lifetimes:

  • SizingPlugin.prod.js (164 KiB) - 30 minutes

  • kiwiSizingPlugin.prod.css (11 KiB) - 30 minutes

Since these are versioned files (v=329), could you increase the cache headers to 1 year? This would significantly improve performance for our repeat visitors.

Best practices suggest:

  • Versioned assets: 1 year cache (cache-control: max-age=31536000)

  • You can bust cache by changing the version number

This would save 178 KiB of bandwidth for repeat visitors.

Thank you!

Posted by Developer 01 ·
1 comment

Comments1

  • Imee (Staytuned)

    •

    Dec 17, 2025

    Hi there,

    Thanks for sharing your feedback and for your interest in improving the overall experience. This cache value is something we’ve been actively tuning over the past year and will continue to evaluate.

    Previously, these assets were cached for up to one year. However, we ran into frequent cases where visitors cached outdated versions, which caused the size charts not to load properly. These issues were then reported to store owners and escalated to us as support requests. In many cases, the only resolution was asking customers to manually clear their local cache or forcing a cache refresh by incrementing the file version for all users.

    To reduce these issues, we lowered the cache duration to 30 minutes. This allows us to cover a typical browsing session without repeatedly loading the files, while also preventing long-lived cached versions from causing display problems. Since making this change, we’ve seen a significant drop in reports related to size charts not loading.

    That said, the assets are still served from a CDN close to each visitor, so load times remain fast and low-latency. We’re also open to adjusting this further if your average customer session tends to be longer.

    If you’re doing additional performance tuning and extending the cache beyond 30 minutes has a meaningful impact for your store, let us know. If there’s enough interest from merchants, we’ll prioritize allowing per-store customization of this cache value.

    Best,

    Imee