Reading Status Codes by Class First
Every HTTP status code's leading digit signals its general category before you even need to know the specific number: 1xx (informational, request still processing), 2xx (success), 3xx (redirection, further action needed), 4xx (client error, something about the request was wrong), and 5xx (server error, the server failed on an apparently valid request) — checking just this first digit is often enough to triage a problem before reading the specific code at all (see HTTP Status Codes Explained for the full breakdown of the pairs people mix up most, like 401 vs. 403).
Searching by number or by keyword both matter for different situations — sometimes you have a specific code from a log or error message and need its meaning; other times you know roughly what kind of error occurred (an authentication issue, a redirect problem) and need to find the right specific code for it, which is exactly why a keyword-searchable reference is more useful than a code-only lookup table.
The color-coding by class (grouping 2xx, 3xx, 4xx, 5xx visually) reinforces the same leading-digit triage instinct — glancing at a color is faster than reading a full code number when scanning a list of several different status codes at once, like when reviewing a server log with a mix of response types.