Why a page cannot be read · error
The result was inconclusive
Something went wrong that we cannot attribute to your site. We would rather say we do not know than publish a finding we cannot stand behind.
The result was inconclusive. We do not know, and we would rather say so.
§01 · what is actually happening
What is actually happening.
This covers the cases where the read failed for a reason that is not evidence about the page: an unexpected status, a connection that did not complete, or a refusal that one request path saw and a second did not.
That last case is the important one. During development a plain request received 403 from two well-known newspapers while a different client received 200 and 302 from the same machine seconds apart. The difference was the HTTP client, not the sites. Recording the first would have published a false accusation against both.
So when the evidence disagrees with itself, the verdict is this one rather than the more interesting one.
§02 · what it costs
What it costs.
None that can be established from this read. Anyone treating it as a problem with your site is reading more into it than it says.
Run it again. If it settles into a specific finding, that finding is the one to act on.
§03 · what would change it
The fix.
Nothing yet. The result was inconclusive rather than bad, and the honest response to that is to read the page again rather than to report a finding we cannot stand behind.
Who does it. Nothing yet. The honest response to an inconclusive read is another read.
Check your own site.
One request, one verdict, no account. If this is the finding you get back, the page above is the one that applies.
See what a machine seesThe other findings