Zero percentage cached after hours

Website, Application, Performance
1

We have a cached percentage of zero after hours of setting up the CDN on our Wordpress website.

Our site url is different from our main hosting domain name where all our DNS records are.
So cloudflare has example.com but our site resolves to example.studio ( using a redirect and a rewrite rule in the htaccess doc )
Could this be why our cache isnt building up?

The first wordpress plugin we used gave us this error when we entered the API token 'No zone named example.studio ’ - because the Cloudflare account is for example.com

We did find a plugin that seems to connect. It allowed us to enter the API token and the domain name - that seems to have allowed a connection.

ANd in the browser, if we inspect the network load, response headers for images are served from a Cloudflare server. But still, after 3 hours, our Percent Cached is 0. ( we do have requests, visitors and a tiny bit of data served from Cloudflare)

Can anyone help us please?

4

Could you please share the domain name?

5

kentridge.studio

and

kentridgestudio.com

6

This domain is redirecting to kentridge.studio so Cloudflare doesn’t cache anything.

This domain is also using Cloudflare. I see most of the static assets are being cached. Is this domain not in your Cloudflare account?

7

kentridge.studio is not on our cloudflare account because it have no dns records.
on our hosting, its just set up as a domain forwarded to kentridgestudio.com

we host the site on a package as kentridgestudio.com then we forward kentridge.studio to kentridgestudio.com and do a rewrite rule in the htaccess so people see kentridge.studio in the location bar (that sounds complicated now but its seemed easier than moving the site when client wanted a different domain name

does that make sense?

8

www.kentridgestudio.com redirects to www.kentridge.studio.

$ curl -is https://www.kentridgestudio.com | grep 'location' 
location: http://www.kentridge.studio/

Both domains are using Cloudflare.

$ dig +noall +answer NS kentridgestudio.com kentridge.studio
kentridgestudio.com.    86400   IN      NS      emely.ns.cloudflare.com.
kentridgestudio.com.    86400   IN      NS      watson.ns.cloudflare.com.
kentridge.studio.       86400   IN      NS      liz.ns.cloudflare.com.
kentridge.studio.       86400   IN      NS      miguel.ns.cloudflare.com.

I assume you are rewriting/reverse proxying at an origin server? In that case the request never goes through your Cloudflare account (the traffic goes through kentridge.studio, which you say is not in your Cloudflare account). Therefore Cloudflare has no opportunity to cache the content in your account. It will be cached in the account of kentridge.studio, but this will naturally not affect the cache hit ratio of kentridgestudio.com.

1 Like
9

That’s not how it works. What you’re doing is essentially telling people to close your site and open kentridge.studio instead.
And that is also why you got the following error:

1 Like
10

Thank you so much for your help.
We understand the issue better now.