Skip to main content

Slow Time to First Byte

All HTML pages with a 200 HTTP status code and a Time to First Byte (TTFB) slower than 600 milliseconds (Google recommends TTFB of 200 ms or faster).

Priority: Low

Impact: Negative

What issues it may cause​

Pages with a high TTFB may cause a poor user-experience and could negatively affect the rankings in search engine results resulting in less traffic and conversions.

A very high TTFB may cause Search Engines to stop crawling and indexing your pages.

How do you fix it​

The pages should be investigated using tools like PageSpeed Insights to identify the issues that may be causing them to have a high TTFB.

What is the positive impact​

Lowering the TTFB may;

  • provide a better user-experience that could positively affect conversion rates.
  • result in higher rankings in search results leading to an increase in traffic and conversions.

  • increase crawl rate of search engines which could result in your pages being discovered faster and updated more frequently.

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:

query GetReportStatForCrawl(
    $crawlId: ObjectID!
    $reportTemplateCode: String!
    $after: String
   ) {
      getReportStat(
        input: {crawlId: $crawlId, reportTemplateCode: $reportTemplateCode}
      ) {
        crawlUrls(after: $after, reportType: Basic) {
          nodes {
            pageTitle
            url
            description
            foundAtUrl
            performanceTtfb
            deeprank
            level
            contentSize
            htmlSize
            foundInGoogleAnalytics
            foundInGoogleSearchConsole
            foundInBacklinks
            foundInList
            foundInLogSummary
            foundInWebCrawl
            foundInSitemap
          }
          totalCount
          pageInfo {
            endCursor
            hasNextPage
          }
        }
     }
   }

Try in explorer