W3 Total Cache and Jetpack CDN

  • Resolved Vincent Verloop

    (@vverloop)


    3 years, 3 months ago

    I’m having an headache for last 5 years about Jetpack CDN and W3 Total Cache.
    W3 Total Cache don’t optimize when a resource is external.
    So when you enable Jetpack CDN and use W3 Total Cache, your website is getting slower.

    I was thinking Jetpack CDN is bad, but Jetpack CDN is good!
    W3 Total Cache is the bad factor, it don’t optimize when a resource is external.

    Get all your files local, so W3 Total Cache can optimize!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Vincent Verloop

    (@vverloop)

    What is the solution? Disable Jetpack CDN? Yes.

    So you have to choose where to optimize…

    Example:
    If you are using for example Cloudflare, then optimze HTML, CSS, JS there not local(with W3 Total Cache) but at Cloudflare. Or local with W3 Total Cache but not with Cloudflare.

    Thread Starter Vincent Verloop

    (@vverloop)

    By disabling Jetpack CDN all my frustrations get away ??

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    I’m having an headache for last 5 years about Jetpack CDN and W3 Total Cache.

    Sorry, do you need support? It looks like you already solved it.

    By disabling Jetpack CDN all my frustrations get away

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘W3 Total Cache and Jetpack CDN’ is closed to new replies.

Tags