WP Rocket and Jetpack Accelerator

  • Resolved pharmanext

    (@pharmanext)


    2 years ago

    Hi Saumya,

    Thank you so much for such a great plugin. It is awesome!
    Kindly ask for your help to deal with the following issues.

    I encountered two messages in PageSpeed: Reduce unused CSS and Serve images in next-gen formats. This is probably a temporary problem with high load on the server. Nevertheless, relevant questions arise.

    First, in parallel to your cool plugin, does it make sense to leave Remove Unused CSS enabled in WP Rocket? And for what reason is the default settings (Third Party — WP Rocket) to have the Unused CSS generation process ends option enabled?

    Secondly, does it make sense to use Jetpack function to convert images to WebP format with subsequent cloud delivery (Performance — Enable site accelerator — Speed up image load times)?

    Finally, should WP Rocket leave the integration with Cloudflare via the appropriate Add-on?

    If all of the above (WP Rocket Remove Unused CSS, Jetpack Accelerator and WP Rocket Cloudflare Add-on) doesn’t make practical sense, maybe these features should be kept enabled just in case when the free Cloudflare Workers limit is reached (I haven’t estimated the amount of traffic on the site yet)?

    Thanks in advance for the informative answers.

    • This topic was modified 2 years ago by pharmanext.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    Hi,
    first of all, if you want you can use WP Rocket for static file optimization, just ensure that you have disabled all page caching functionality of WP Rocket before installing this plugin. Check: https://gist.github.com/isaumya/d5990b036e0ed2ac55631995f862f4b8

    The upcoming version of this plugin is also going to support rocket_rucss_complete_job_status hook and will purge cache upon firing of that hook. It will be labeled as RUCSS generation process ends inside the plugin settings page > third-party integration section. The new version is going to be released very soon but if you like you can download the build from here until it gets published.

    Now coming to Jetpack Accelerator, I would rather recommend using Cloudflare Pro. If you enable Jetpack Accelarator for your images, then your images will be loaded from a totally different hostname like i0.wp.com and the requests won’t even go via Cloudflare. WIth Cloudflare Pro you get access to Cloudflare Polish which will give unlimited image optimization and also WebP support.

    Moreover, you can also consider using optimole or imagekit.io both of them has great free plans.

    Hope that answers all your questions.

    Thread Starter pharmanext

    (@pharmanext)

    Thank you for the detailed explanations.

    pldoolittle

    (@pldoolittle)

    You said, “I would rather recommend using Cloudflare Pro. If you enable Jetpack Accelarator for your images, then your images will be loaded from a totally different hostname like i0.wp.com and the requests won’t even go via Cloudflare. WIth Cloudflare Pro you get access to Cloudflare Polish which will give unlimited image optimization and also WebP support.”

    This is the change I have just made, but I am second guessing it. The problem is that for a low volume site like mine, CF cache hits are very low (~30%). But WordPress/JetPack/Automatic cache hits are cached indefinitely.

    Thoughts?

    Plugin Contributor iSaumya

    (@isaumya)

    Hi @pldoolittle,
    Couple questions:
    1. Are you using the default page rule mode or the worker mode of this plugin?
    2. Have you enabled Smart Tiered Cache?
    3. Does the images when served from the origin server has content-length in the response header?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WP Rocket and Jetpack Accelerator’ is closed to new replies.