All fix guides

Page speed (A2)

Server TTFB (bot first byte)

What this check means

This guide helps you act on one scan finding. It is not legal advice or a compliance verdict.

What to fix

Lower bot TTFB with page cache and a warmer PHP/edge path for the scanned URL.

Step-by-step fix

  1. Enable full-page cache for anonymous HTML on the host or via WP Rocket / LiteSpeed / Cloudflare Cache Everything (HTML) for this public URL.
  2. Confirm the URL is not forced dynamic (nocache headers from a membership, cart, or “disable cache for logged-in” rule accidentally applied to anonymous).
  3. If the host offers a PHP OPcache / worker keep-alive setting, leave it on for production.
  4. Purge once, then request the URL twice yourself before scanning so the cache is warm.

Choose the path for your setup

  • Cloudflare

    Use a Cache Rule that caches the HTML path and respects marketing query strings you need (see also C14).

  • WP Engine / Kinsta / Flywheel

    Use the host panel “clear cache” and their recommended page-cache plugin; avoid stacking a second full-page cache.

Confirm it is fixed

Re-scan and compare bot TTFB (A2) on the same URL after the cache is warm.

Rescan this check on your site

Scan the same URL again, then compare this check with your previous report.

Run a free leak scan