• So this is kind of a double-edge sword situation. Within gtmetrix, my scores are high (99% on PageSpeed) and (92% on YSlow). The only “issue” is with my cookies. I am getting an ‘F’ on the (Use cookie-free domains) portion of gtmetrix (YSlow) report. Let me explain how I got here.

    Upon first install of my WP site, the WordPress Address (URL) & Site Address (URL) were identical (https://jbehrmusic.com). I ended up changing my Site Address (URL) to put WWW in front of it, (https://www.jbehrmusic.com), out of preference. This caused issues with the default block editor in WordPress [I wasn’t able to create any pages or posts]. After researching, there were countless threads on this topic, and they had a range of “solutions” available.

    – Resetting Permalinks
    – Switching to Classic Editor
    – Make WordPress Address (URL) & Site Address (URL) identical

    Switching to classic editor worked fine for me, but I didn’t want to use the classic editor, as I liked working with the blocks. So I then changed the URLs to match, in which I set both the WordPress Address (URL) & Site Address (URL) to be https://www.jbehrmusic.com. My site has been working great ever since, until I ran this gtmetrix report, which gave me an F grade on the cookie portion.

    So now I’m not sure what to do. Some people (across forums and YouTube) have stated that cookies aren’t much to worry about, while others say you should offload those cookies by creating a subdomain, such as static.jbehrmusic.com

    Here are my questions.

    1) Should I even worry about this cookie-free domain stuff?
    2) If I should, how do I go about fixing it? (Without causing the block editor to be unusable)

    FYI: I am using Cloudflare, which I know handles cookies differently, and I will unable to achieve a 100 score while using it. But I think the main problem is being caused by my WordPress Address (URL) & Site Address (URL) being the same.

    • This topic was modified 5 years, 10 months ago by jbehrmusic.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator bcworkz

    (@bcworkz)

    Sorry for the late reply. You’ve probably already decided for yourself by now, but here’s my two cents worth all the same. Unless one logs in, WP does not utilize cookies by default. Your theme or plugins might utilize cookies though. The issue might be moot for the majority of your visitors.

    The point of cookieless domains is to avoid sending data that is not needed. Unless you have a huge volume of static data, IMO the difference is negligible. While it’s possible to force WP to serve static content from a different domain, it’s not setup to make this easy. In most cases I don’t think it’s worth the effort in terms of real world speed improvement.

    Thread Starter jbehrmusic

    (@jbehrmusic)

    @bcworkz thanks for the reply. After further research, I decided not to worry about it. As you stated, the difference will probably be negligible.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘cookie free domain problem’ is closed to new replies.