Cf-cache-status: HIT but still takes > 5s

Why might a resource (<50kb) being served from Cloudflare’s cache (evidenced by the cf-cache-status: HIT header) take so long (>5s)?

1 Like

This can happen for multiple reasons.

It is usually an indication that your ISP is takinga long time to establish the connection to our Edge Network.

Do you see the issue if you connect to a different network?

Do you see it on different machines on the same network?

It loads slow every so often: several times a day. Subsequent loads (even with local browser cache disabled) seem to load much faster. Could it be loading slow because CF is fetching fresh from the origin server? How would I know when CF is updating its cache? Is there a header that would indicate such?

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.