High TTFB and bypassing cache

[user369]

Hi, our site has a TTFB over 1 second:
https://app.sitespeedbot.com/a5ca4a68d70484e0f5b1

I’ve run a diagnostic test and it confirmed it:
https://www.cloudflare.com/diagnostic-center/?url=https%3A%2F%2Fwww.guttercleaningdirectory.co.uk

Any ideas how i can reduce this?

Also noticed this in the response headers:
cf-cache-status: BYPASS
cache-control: no-store, no-cache, must-revalidate

So it doesn’t look like the caching is working.

I’ve added a rule to cache everything too.

Can you help? Thanks

[trichstir]

Do you have Development Mode enabled in your Cloudflare dash or the WordPress plugin?

Or something else that is modifying the HTTP response?

I don’t know exactly what these responses mean but it could be causing the cache bypass:

set-cookie: devmode=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/
set-cookie: editor=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/
set-cookie: invite_code=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/

EDIT: If you’re not in dev mode, it’s probably a WordPress caching / optimization plugin that’s setting incorrect headers somehow.

[user369]

Dev mode is off.

The site is running on the brilliant directories platform. I asked their support about using cloudflare with their platform and they wasn’t very helpful. They just said we can’t help you with 3rd party software.

[sandro]

@user369

So it doesn’t look like the caching is working.

Caching is working, however Cloudflare by default does not cache HTML. Considering that you have a login area you most likely cannot cache HTML either as otherwise logins would not work any longer.

This delay comes straight from your server I am afraid and needs to be fixed there.

[user369]

Ok thanks. I didn’t realise people would not be able to login

[sandro]

Depending on what gets cached people would either always get the non-logged-in pages or logged-in pages from other accounts. Unless you only have a subset of pages which are login relevant, you won’t really be able to cache HTML and would need to make sure your webserver itself returns the content faster.