Faster search, better first results
Better first results and lower client response time, with no setup changes.
- Published
- Updated
Highlights
- Primary answer first in 89.8% of searches in our 1,000-query Next.js benchmark, up from 81.9%.
- Latest client P95 was 1,047 ms, compared with 1,983 ms in the published benchmark.
- No changes to API calls, indexed content, or project settings.
The most accurate website search just got even better with reduced latency and better top 1 hit rate. Here are the latest results of Ceisium Search on the NextJS docs benchmark.
The right page, higher in the results
We tested the update with 1,000 questions about the Next.js documentation opens in a new tab . The primary answer appeared first in 898 searches, up from 819 with the earlier version. That is 79 more searches with the main answer in the first position.
| Search result | Earlier version | This update |
|---|---|---|
| Primary answer first | 81.9% | 89.8% |
| An accepted answer in the first three results | 93.7% | 97.9% |
| An accepted answer in the first ten results | 97.4% | 98.9% |
Finding the correct results matters. Getting them quickly matters too.
Less time waiting for results (47.2% lower client P95 latency)
Client P95 latency was 1,047 ms in the latest run, compared with 1,983 ms in our published benchmark.
Both figures include the network round trip. In the latest run, 95% of successful searches returned within about 1.05 seconds.
| Client response time | Published benchmark, 3 September | Latest run, 27 September |
|---|---|---|
| Median | 858 ms | 812 ms |
| P95 | 1,983 ms | 1,047 ms |
The quality table above compares the earlier version with this update on the same 1,000 questions. Note: Response time will vary with location, website content, and traffic.
No extra setup
Existing projects receive the update automatically. Your current search integration, indexed content, and project settings continue to work.
You do not need to change your API calls, rebuild your index, or tune new settings.