Skip to content
Raptor home
Menu

Slow server response

performance.slow_server_response
Priority
Medium
Severity
Warning

What we look for

When Raptor crawled these pages, the server took 1.5 seconds or more to start answering, counting any redirects on the way.

Why it matters

A slow first answer delays everything else on the page, and search engines crawl a slow site less.

How to fix

Turn on page caching in your CMS or hosting, use a CDN (a network that serves your site from servers near each visitor), and ask your host about slow database queries or an underpowered server.

What it cannot know

Times are measured from Raptor's computer during this crawl, so distance, the network and the crawl's own requests all affect them.

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal
When it is one of the five findings under Fix first, raptor crawl prints the id under it.
Check: performance.slow_server_response
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "performance.slow_server_response"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=performance.slow_server_response
MCP
raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.
raptor_findings {
  "job_id": "...",
  "check_id": "performance.slow_server_response"
}