Solve issue: Serve the following static resources from a domain that doesn't set cookies on cloudflare

caching

#1

Today I was checking on tools.pingdom.com for the performance of my site btsudama.com . There is an interesting issue about “Serve the following static resources from a domain that doesn’t set cookies:”

I’m pro subscriber on cloudflare, is there anything I can do to resolve this issue?

When I checked this solution on cloudflare I found below article that stated “Cloudflare will add a security cookie to any domain or subdomain that is being proxied by our service. In addition, since Cloudflare is already caching your static content by default, there really is no need to have a cookieless domain.”

Source: https://support.cloudflare.com/hc/en-us/articles/200169816-Can-I-serve-a-cookieless-domain-or-subdomain-through-Cloudflare-?flash_digest=498b98acad395e05eb41c19faef08306f09605c8

In my case this issue keep getting worst. Now I had 20 of them saying:

Serve the following static resources from a domain that doesn't set cookies:
*https://btsudama.com/images/BTS.png
*https://btsudama.com/images/Easyblog/ajamila-yama-duta.jpg
*https://btsudama.com/images/Easyblog/ratha_yatra_pastimes.jpg
*https://btsudama.com/images/Krishnaandcowherdboy.jpg
*https://btsudama.com/images/com_droppics/20/Back-To-Godhead-Viratrimurti.jpg
*https://btsudama.com/images/com_droppics/20/Envy-Vaisnavas.jpg
*https://btsudama.com/images/com_droppics/20/flute.jpg
*https://btsudama.com/images/com_droppics/20/forgiveness.jpg
*https://btsudama.com/images/obgrabber/2018-06/8af9fbd879.jpeg
*https://btsudama.com/media/com_easyblog/scripts/vendors/ui/position.min.js
*https://btsudama.com/media/mod_falang/images/en.gif
*https://btsudama.com/media/mod_falang/images/id_id.gif
*https://btsudama.com/media/plg_jchoptimize/cache/css/8f9c5ae6454c7b9fe92648f494f3c6cf_0.css
*https://btsudama.com/media/plg_jchoptimize/cache/js/b98c6b31d2ad2c1073e8d176f7f590a2_0.js
*https://btsudama.com/media/plg_jchoptimize/cache/js/c04bc2618aea50f6c8f8e306517b94d2_0.js
*https://btsudama.com/media/sourcecoast/images/provider/facebook/icon_label.png
*https://btsudama.com/media/sourcecoast/images/provider/google/icon_label.png
*https://cdn.onesignal.com/sdks/OneSignalSDK.js

Thank You
I Kadek Sudama


#2

It’s a minor quibble from Pingdom, as the Cloudflare cookies don’t negatively impact performance.

If it really bothers you, then you would have to host your static content on a subdomain set to :grey:. If onesignal belongs to you, you’d have to set that CDN to :grey: as well.

Again, this warning isn’t an issue I feel is worth pursuing.


#3

Hi sdayman,
Thank you so much for your reply and clarification.
Worth for me to know your opinion on this.

If you feel is not necessary, I will certainly follow your opinion on this.

I Kadek Sudama


#4

We have the same issue as @btsudama.bvms – as I’m sure many others do too.

While Cloudflare may add a security cookie to every domain/subdomain, this issue is causing the following:

(1) Website performance issues (FTTB and overall image download speeds). ’

(2) Cookies for each image are being downloaded. When we check our browser(s) for downloaded info, we see that the culprit are these images. (Note: All of our images have been reduced in size and optimized using reSmush.it)

So, can anyone suggest a solution to solve this? Also, if we implement the “fix” provided in the link below (and with Cloudlfare “on”), can we expect this issue to be fixed?

Thank you!


#5

I’m not seeing any significant performance degradation from image cookies (see image below). With HTTP/2, they all load in parallel, and very quickly. You’ll see from my sample, 12 images (there are quite a few more on that list) all load in a span of less than a tenth of a second.

Regardless, Cloudflare cookies are never going away. They don’t add significant overheard and are required for Cloudflare functionality.


#6

Thanks, @sdayman. We’ll continue to monitor and implement other possible solutions.


#7

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