Skip to main content

Overview

Page speed directly impacts user experience, conversion rates, and search rankings. SEO Crawler tracks response times for every URL discovered during crawls, helping you identify and fix performance bottlenecks.
Available on: All plans (basic metrics), Pro/Agency (trend analysis)

What We Measure

Time to First Byte (TTFB)

The time between our crawler sending a request and receiving the first byte of the response. This measures server-side performance:
  • Database queries
  • Server processing
  • Network latency

Total Response Time

The time to download the complete response body. This includes TTFB plus:
  • Content transfer time
  • Network throughput

Performance Thresholds

We categorize response times into three levels:
RatingTTFBTotal TimeImpact
๐ŸŸข Fast< 200ms< 1sExcellent user experience
๐ŸŸก Moderate200-600ms1-3sAcceptable but room for improvement
๐Ÿ”ด Slow> 600ms> 3sNegatively impacts users and SEO
Google considers page speed a ranking factor. Pages with TTFB over 600ms may be deprioritized in search results.

Why Response Time Matters

User Experience

Studies show clear correlations between speed and user behavior:
DelayImpact
+1 second7% reduction in conversions
+2 seconds40% of users abandon the page
+3 seconds53% of mobile users leave

SEO Impact

  • Core Web Vitals: Google measures Largest Contentful Paint, which correlates with TTFB
  • Crawl Efficiency: Slow pages consume more of Googleโ€™s crawl budget
  • Mobile-First Indexing: Mobile users on slower connections are particularly affected

Using Response Time Data

Dashboard View

The Response Time section shows:
  • Average TTFB: Mean response time across all pages
  • Slowest Pages: Top 10 pages by response time
  • Distribution Chart: Histogram of response times
  • Trend Graph: Performance changes over time (Pro/Agency)

Identifying Slow Pages

Click any slow page to see:
FieldDescription
URLThe slow page URL
TTFBTime to first byte
Total TimeComplete response time
Response SizeTotal bytes downloaded
HistoryPerformance trend across crawls
Look for pages that are both slow AND high-traffic. Fixing these provides the biggest impact.

Common Performance Issues

Server-Side Problems

Symptoms: High TTFB, especially on dynamic pagesSolutions:
  • Add database indexes
  • Optimize queries (avoid N+1 problems)
  • Implement query caching
  • Use database connection pooling
Symptoms: Consistently high TTFB on repeat visitsSolutions:
  • Enable server-side page caching
  • Use a CDN for static assets
  • Implement edge caching for dynamic content
  • Add proper cache headers
Symptoms: High TTFB on pages that fetch external dataSolutions:
  • Cache API responses
  • Make API calls asynchronous
  • Implement circuit breakers
  • Add timeout limits

Content Problems

Symptoms: Low TTFB but high total timeSolutions:
  • Compress images
  • Enable gzip/brotli compression
  • Minify HTML, CSS, JavaScript
  • Remove unused code
Symptoms: High number of requests in waterfallSolutions:
  • Bundle JavaScript files
  • Use CSS sprites
  • Inline critical CSS
  • Lazy load non-critical resources
Response Trends requires the Response Trends scan option to be enabled.
Track performance changes over time to:
  • Detect Regressions: Spot when deployments slow down your site
  • Measure Improvements: Verify optimization efforts are working
  • Identify Patterns: Find time-based performance issues (peak traffic)

Trend Analysis

The trend view shows:
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚  Average TTFB Over Time                                 โ”‚
โ”‚                                                          โ”‚
โ”‚  300ms โ”€โ”ค                    โ•ญโ”€โ”€โ”€โ•ฎ                       โ”‚
โ”‚         โ”‚               โ•ญโ”€โ”€โ”€โ”€โ•ฏ   โ•ฐโ”€โ”€โ”€โ•ฎ                   โ”‚
โ”‚  200ms โ”€โ”ค    โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ             โ•ฐโ”€โ”€โ”€โ”€โ•ฎ              โ”‚
โ”‚         โ”‚โ”€โ”€โ”€โ”€โ•ฏ                            โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€       โ”‚
โ”‚  100ms โ”€โ”ค                                                โ”‚
โ”‚         โ””โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€    โ”‚
โ”‚            Oct 1  8   15   22   29  Nov 5  12   19       โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
Set up alerts to notify you when average response time exceeds a threshold. This catches performance regressions quickly.

Optimization Checklist

1

Identify Slowest Pages

Review the โ€œSlowest Pagesโ€ report to find your biggest bottlenecks.
2

Check High-Traffic Pages

Cross-reference with analytics to prioritize pages that affect the most users.
3

Analyze Server Response

For high TTFB, investigate server-side code, database queries, and caching.
4

Optimize Content

For high total time, compress and optimize page content and assets.
5

Enable CDN

Serve static assets from a CDN to reduce latency for global users.
6

Monitor Continuously

Enable Response Trends to track improvements and catch regressions.

Filtering Options

FilterDescription
Speed RatingFast, Moderate, Slow
Page TypeHTML, Images, CSS, JavaScript
URL PatternFilter by URL contains/starts with
Time RangeCompare different crawl periods

Integration with Other Features

Response time data enhances other analyses:
  • Broken Link Detection: Timeouts are tracked with response data
  • SEO Analysis: Slow pages flagged as SEO issues
  • AI Review: Performance incorporated into health scores