How to fix it
Investigate server response time for this URL — caching, database queries, or slow third-party calls are the usual causes.
When it is not a problem
This measures the server's time to respond, not how fast the page renders. A site with a poor Core Web Vitals score can be fast here, and the fixes are in different places.
How Rankelle handles it
- SeverityWarning. It costs traffic or clarity without stopping anything, which is where most real work lives.
- DetectionDetected on a single page while crawling it, then grouped with the other pages under the same URL pattern.
- GroupingEvery page with this finding under the same URL pattern becomes one cause, with a confidence taken from how much of the pattern is affected. 400 of 400 is a template; 6 of 14 is phrased as a question.
- LandingThe affected URLs stay under cheap watch. When this finding is gone from all of them, the fix is marked landed without anyone reporting the deploy.
- VerdictAt landing, comparable untouched URLs are frozen as a control set. Twenty-eight days later the two are compared, and the fix can come back as having done nothing.
Try it on your own site, free
No card, and the free tier does not expire — the first verdict takes about six weeks to arrive.