Skip to main content

Why Am I Still Getting Browser Cache TTL Warnings?

Updated this week

FlyingPress automatically sets long browser cache TTL headers for static files, helping them get cached efficiently. This helps resolve the “Serve static assets with an efficient cache policy” warning in Google PageSpeed Insights.

Possible Reasons:

  1. Unsupported Web Server
    FlyingPress can set these headers only if your server is Apache, LiteSpeed, or OpenLiteSpeed.
    If you’re using Nginx, you’ll need to either:

    • Contact your hosting provider, or

    • Manually update your Nginx config.

  2. Third-Party Scripts
    Browser caching policies for third-party resources (e.g., fonts, ads, analytics) cannot be controlled by FlyingPress or your server.

Did this answer your question?