The page took 4.2 s to load

Short answer

The HTML took more than 3 seconds to arrive when fetched from the AISeeWhy server, measured from the first request to the end of the body, redirects included. Images, scripts and styles are not part of this time. Look at server caching, the CDN and slow work done before the page is sent.

seo.slow_response · Priority: P2

What it means

The HTML alone took over 3 seconds. Slow pages are crawled less often and lose visitors. Check server caching and the CDN.

Why it matters for AI search

Search engines adjust how much they crawl a site to how fast it answers, so a slow server means fewer pages fetched in the same time. Tools that fetch a page while an AI answer is being written cannot wait long, and a slow page may be left out. Visitors leave slow pages too.

One slow result can be a one-off, since the time includes the network between our server and yours. If it repeats, the cause is usually on the server: no page cache, slow database queries or external API calls during the request, cold starts on serverless hosting, or a CDN that does not cache HTML.

How to fix it

  1. Check whether it repeats: load the page in a private window with the browser's network panel open and look at the time for the document request.
  2. Cache the HTML where it is the same for everyone: a page cache in WordPress, static generation or incremental regeneration in Next.js, or a CDN rule that caches HTML.
  3. If the page cannot be cached, find the slow part in server logs or the application's traces: database queries, external API calls made during the request, or cold starts.
  4. Remove redirects in front of the page, since their time is included.
  5. Run "Check again" on the page report to confirm the result.

How to confirm the fix

After the change, press "Check again" on the report: it lists what was fixed and how the score changed.

Check my page →

All findings and how the score works