SiteAud!tLint Support

Warning Performance

Slow response (over 1 second)

Severity
Warning
Impact
High
Effort to fix
High
Issue code
slow_response

Why it matters

The HTML took more than one second to download. Slow server responses hurt Core Web Vitals and crawl rate.

How to fix it

Improve server response time with caching, a CDN, database tuning or better hosting.

What this means

The page took more than one second to download during the crawl. The time shown is measured from the moment SiteAud!tLint sent the request until the full HTML arrived, from your computer and over your connection.

How to read it

The number is a crawl measurement, not a Core Web Vitals score. It reflects server response time plus HTML download, not images, scripts or rendering. Treat it as a strong hint about server speed:

  • A few slow pages usually point to expensive pages: large category pages, search results, or pages that run heavy database queries.
  • Most pages slow points to the server, hosting plan, or a missing page cache.
  • Slow only during the crawl can mean the server is struggling with the crawl itself. Lower Parallel requests in Crawl settings and recrawl before drawing conclusions.

Why it matters for SEO

Slow server responses delay everything after them, including Largest Contentful Paint. They also limit how many pages Googlebot crawls in a session: Google reduces its crawl rate when a server responds slowly, so large sites get new and updated pages indexed later.

How to fix it

  1. Enable full-page caching for anonymous visitors, through your platform, a caching plugin or the CDN.
  2. Serve HTML through a CDN close to your visitors.
  3. On dynamic pages, find the slow part: database queries, external API calls made while the page loads, or very large page templates. See also Large HTML.
  4. Check hosting resources if response times rise under load.

Verify the fix

Recrawl with the same crawl settings and compare with the previous audit in the Action Plan and Compare view. One fast audit can be luck, so confirm the improvement holds across two or three crawls.

How it affects your score

Finding this issue on any page costs the Performance score 3 points, plus up to 12 more depending on the share of crawled pages affected. Weakens rankings, crawling or measurement. Fix after critical issues.

Find the affected URLs

Open Crawl > Issues and pick Slow response (over 1 second). Each affected URL is listed with its evidence, and Copy URLs or Export URLs hands the list to a developer. The issue also appears in the Action Plan, ranked by impact (high) and effort (high), and in the issues CSV under the code slow_response. After fixing, run a new audit and use Compare to confirm the URLs moved to fixed.