# Pages with Slow Server Response Time

**Priority**: Critical

**Impact**: Negative

## What issues it may cause

The initial server response time significantly influences the overall page load time since the browser must wait for the initial response before it can start rendering the page content. In short, the knock-on effect is that nothing else can happen until the initial response is received. This may cause the following:<ul><li><strong>Increased Page Load Time:</strong> Slow server response times delay the entire page loading process, impacting the user experience.</li><li><strong>Poor User Experience:</strong> Users may become frustrated and abandon the site if they experience long wait times, especially on mobile devices or slower internet connections.</li><li><strong>SEO Impact:</strong> Search engines like Google consider page speed as a ranking factor. Prolonged server response times can negatively affect search engine rankings.</li><li><strong>Resource Wastage:</strong> Slow response times can lead to higher resource usage, increasing costs and reducing the efficiency of server infrastructure.</li></ul>

## How do you fix it

Since there are many possible causes of slow server response times, there are various optimization strategies. First try to identify what might be causing the initial server response to be slow. Things to consider:<ul><li><strong>Server Load:</strong> The current load on the server, including the number of concurrent requests it's handling, can affect response time. A heavily loaded server may take longer to process incoming requests and respond to them.</li><li><strong>Server Resources:</strong> The resources available to the server, such as CPU, memory, and disk I/O, can impact response time. Insufficient resources may lead to bottlenecks and slower response times, especially during periods of high traffic.</li><li><strong>Network Latency:</strong> The physical distance between the client (e.g., your web browser) and the server can introduce network latency, which delays the transmission of request and response data. Longer distances or congested network routes can result in higher latency and slower response times.</li><li><strong>Website Architecture:</strong> The design and architecture of the website, including the complexity of server-side code, database queries, and content delivery mechanisms, can impact response time.</li><li><strong>Caching Mechanisms:</strong> Implementing caching mechanisms, such as content caching and database query caching, can help reduce the need for repeated server-side processing and speed up response times for subsequent requests.</li></ul>[Learn more about server response time.](https://developer.chrome.com/docs/lighthouse/performance/server-response-time)

## What is the positive impact

<ul>
  <li>
    <strong>Faster Page Load Times:</strong> Improved server response times reduce overall page load times, enhancing
    the user experience.
  </li>
  <li>
    <strong>Better User Retention:</strong> Quicker responses lead to happier users who are more likely to stay on the
    site and engage with its content.
  </li>
  <li>
    <strong>Improved SEO Rankings:</strong> Faster response times can contribute to better search engine rankings,
    potentially driving more organic traffic.
  </li>
  <li>
    <strong>Efficient Resource Utilization:</strong> Optimizing server response times can lead to more efficient use of
    server resources, potentially lowering operational costs.
  </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
              savingsScore
              auditResult
              productOfSavingsKibAndPageviews
              productOfSavingsSecsAndPageviews
              savingsKib
              savingsSecs
            }
            totalCount
            pageInfo {
              endCursor
              hasNextPage
            }
          }
       }
     }
```

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