Slow server response
22.8%
of the 3,044 free scans considered in the last 30 days raised this finding. That is 694 scans across 694 distinct sites. 95% interval 19.8% to 26.1%.
What it means
Time to first byte is the floor every other speed metric sits on: a slow origin response delays everything after it.
How to fix it
Get time-to-first-byte under about 800ms: cache HTML at the edge, and check for a slow database call or a redirect chain in front of the page.
How to check it yourself
Run curl -so /dev/null -w '%{time_starttransfer}' https://example.com to see how many seconds pass before the first byte arrives.
What fixed looks like
The curl time to first byte falls under about 800ms.
How we measured this
Go Voltic scans a site and records which findings it raises. The share above is over every free four-page scan in the last 30 days that loaded at least one page, which is 3,044 scans. Deep scans of paid reports and of the research sweep read a site at a different depth and are a separate population, never in this denominator. It is not a survey and it is not an estimate: it is a count of what our own scanner found. Sites are counted once each in the distinct-sites figure, so a site scanned twice does not weigh double there.
The interval is a 95% Wilson interval. A share printed without its sample size reads as certainty and is indistinguishable from a guess, so both are always shown. Figures on this page were computed on 2026-09-08.
The same share sits beside every other finding on the benchmarks page, which also carries the whole table as CSV and JSON and says how to cite it.
Check your own site
The free scan reads four pages and reports every finding it raises, including this one. It takes about ten seconds and asks for nothing but the address.