Audit rules
Response Time
Observed total time of the fetch in milliseconds (one measurement from the audit server, not a Core Web Vital); review above 2,000 ms (legacy threshold). In a QuikSEO audit, a failure has info severity and counts against the score. The exact condition, its exceptions and its sources follow below.
performance.response_timeInfo01 — Definition
How This Rule Is Checked
The rule is a pure function of the fetched page: no extra requests, no account settings. The same input always gives the same result.
Rule Severity and Score
- Rule id
performance.response_time- Group
- Performance
- Severity of a failure
- Info
- Counts in the score
- Yes, whenever it applies to the page
- Required for a score
- No
- Replaces the check
response_time
Condition and Exceptions
- Condition
- Observed total_ms; review above 2,000 ms (legacy threshold)
- Exceptions
- No timing → not_checked
Sources and Project Decision
- Sources
- No authoritative document covers this check: it is a project decision (see the decision below and the source register).
- Project decision
- Threshold inherited from 66audit.
02 — Performance
Other Rules in This Group
The other checks of the same group, each with its own condition and sources.
- DOM Sizeperformance.dom_size
- HTTP Requestsperformance.http_requests
- HTML Page Sizeperformance.page_size
- Render Blocking Scriptsperformance.render_blocking_scripts
- Render Blocking Stylesheetsperformance.render_blocking_stylesheets
- Time to First Byteperformance.ttfb