# Pages with Poor Cache Policies

**Priority**: Critical

**Impact**: Neutral

## What issues it may cause

<ul>
  <li>
    Increased Network Requests: Without appropriate cache TTL values, resources may need to be fetched from the server
    each time a user requests them, resulting in more network requests and slower load times.
  </li>
  <li>
    Higher Bandwidth Usage: Fetching resources repeatedly from the server increases bandwidth usage for both the user
    and the server, potentially leading to higher costs and slower page load times, especially on slow or congested
    networks.
  </li>
  <li>
    Longer Page Load Times: When resources are not cached or have very short TTL values, the browser must download
    resources from the server for every page load. This can result in longer page load times and a less responsive user
    experience.
  </li>
  <li>
    Reduced Efficiency: Constantly fetching resources from the server puts additional strain on server infrastructure
    and can lead to higher latency and slower page loads. Potential for Traffic Congestion: In scenarios with high
    traffic or peak usage times, the lack of caching can lead to server overload and potential downtime.
  </li>
</ul>

## How do you fix it

<ol>
  <li>HTTP Headers: Set cache TTL values using HTTP headers such as Cache-Control and Expires in server responses.</li>
  <ul>
    <li>
      Cache-Control: This header allows you to specify the maximum age (max-age) that a resource can be cached by the
      browser. For example, Cache-Control: max-age=604800 sets the TTL to one week (604,800 seconds).
    </li>
    <li>
      Expires: This header specifies a date and time when the resource should be considered stale and fetched from the
      server again. For example, Expires: Wed, 15 Feb 2023 12:00:00 GMT.
    </li>
  </ul>
  <li>Resource Type Considerations: Different types of resources require different cache TTL strategies:</li>
  <ul>
    <li>
      Static Resources: Resources like images, fonts, CSS, and JavaScript files that change infrequently should have
      longer TTL values (e.g., days or weeks) to maximize caching benefits.
    </li>
    <li>
      Dynamic Resources: Resources like APIs or frequently updated data should have shorter TTL values or may not be
      cached at all.
    </li>
  </ul>
</ol>

## What is the positive impact

<ul>
  <li>
    Reduced Network Requests: By allowing resources to be cached and reused, cache TTL minimizes the need for repeated
    network requests, which can speed up page load times.
  </li>
  <li>
    Faster Page Load Times: Serving resources from the cache is faster than downloading them from the server, especially
    for users on slow connections or high-latency networks.
  </li>
  <li>
    Lower Bandwidth Usage: Using cached resources reduces bandwidth consumption for both users and servers, which can
    lead to cost savings and better performance.
  </li>
  <li>
    Consistent Performance: Longer cache TTLs can help improve performance consistency, as cached resources are
    available locally and less affected by fluctuations in network conditions.
  </li>
</ul>

## How to fetch the data for this report template

You will need to run a crawl for report template to generate report. When report has been generated and you have
crawl id you can fetch data for the report using the following query:


```graphql
query GetReportStatForCrawl(
      $crawlId: ObjectID!
      $reportTemplateCode: String!
      $after: String
     ) {
        getReportStat(
          input: {crawlId: $crawlId, reportTemplateCode: $reportTemplateCode}
        ) {
          crawlSiteSpeedAudits(after: $after, reportType: Basic) {
            nodes {
              url
              auditId
              title
              displayValue
              savingsKib
              pageviews
              productOfSavingsKibAndPageviews
              itemsCount
              auditResult
            }
            totalCount
            pageInfo {
              endCursor
              hasNextPage
            }
          }
       }
     }
```

**Variables:**
```json
{"crawlId":"TjAwNUNyYXdsNDAwMA","reportTemplateCode":"uses_long_cache_ttl_failed_audits"}
```