The server answers slowly: TTFB 1400 ms on 2 pages
On the listed pages, Time to First Byte is above 800 milliseconds (over 1.8 seconds is poor): the server takes too long to start sending the HTML. Cache pages, serve them from a CDN close to visitors, remove redirects and speed up the work done before the response.
What it means
Time to First Byte is how long the server takes to start answering; up to 800 ms is good. Cache pages, use a CDN and speed up the backend.
Why it matters for AI search
Every other metric waits for the first byte: nothing can load or appear until the HTML starts arriving, so a slow server also makes LCP slow. Crawlers fetch fewer pages from a slow server, too.
The audit gets TTFB from PageSpeed Insights (mobile): real-user data from the Chrome UX Report when it exists, which includes redirects and connection time for real visitors, otherwise the server response time from a Lighthouse lab run. This is not the same as the slow response check on the page report, which times the whole HTML from the AISeeWhy server. The finding is P2 when any page is in the poor range.
How to fix it
- Find out whether the time goes to the network or to the server: compare results from different regions, and look at a
Server-Timingheader or your application's traces. - Cache HTML that is the same for every visitor: a page cache plugin in WordPress, static generation in Next.js and similar frameworks, or a CDN rule that caches HTML. Skip the cache for logged-in users and carts.
- For pages that cannot be cached, speed up what runs before the response: slow database queries, external API calls and cold starts on serverless hosting.
- Remove redirects on the way to the page, such as
http→https→www, and link to final addresses. - Run the site audit again from your account. Real-user data can take up to four weeks to reflect a fix.
Example
# nginx: cache HTML from the application for 5 minutes
proxy_cache_path /var/cache/nginx keys_zone=pages:10m max_size=1g;
server {
location / {
proxy_pass http://app;
proxy_cache pages;
proxy_cache_valid 200 5m;
proxy_cache_use_stale error timeout updating;
add_header X-Cache $upstream_cache_status;
}
} How to confirm the fix
After the change, press "Check again" on the report: it lists what was fixed and how the score changed.