Issues with plugin and with WP Fastest Cache

  • I have WP Fastest Cache with the following settings:
    * Preload
    * Purge cache when post is created/updated
    * Don’t show cache to logged in users

    Autoptimize is set up so it doesn’t touch CSS for logged in users as well.

    RapidLoad settings:
    * Enabled CriticalCSS
    * Minify
    * Optimize inline CSS
    * Inject original CSS files on user interaction.

    I have the following issues:

    1. RapidLoad seems to only add pages in queue when they’re not in cache.
    2. Occasionally when viewing cached pages I get error 410 (gone) for the uucss files.
    3. I’m a bit confused as to why “autoptimize_fallback.css” exists and is visible by PageSpeed Insights. It’s basically a pre-optimization file, why is it added? It has tons of unused css.
    4. My front page had unused css removed first, but now, even though I didn’t change it, it has unused CSS again. Changes got reverted for some reason and now it’s queued again. Why? I assumed that once page has unused css removed it won’t be touched again until it’s updated.
    • This topic was modified 2 years, 4 months ago by rinart73.
    • This topic was modified 2 years, 4 months ago by rinart73.
    • This topic was modified 2 years, 4 months ago by rinart73.
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Shakeeb Sadikeen

    (@shakee93)

    1. Some plugins don’t execute PHP on the server when it caches the page. It serves the static version of the page. This is the reason why cached pages don’t get added to the queue. Click on the “Add” button and select “Sitemap” to crawl all the pages on your website.

    2. That happens when your cache gets expired. Clear your page cache and re-queue the RapidLoad job for that URL will fix it.

    3. This is probably a conflict between the plugins you are using. The “autoptimize_fallback.css” file is loaded when the Autoptimize file is missing.

    4. RapidLoad has automatic file change detection with CSS hash change. This could happen when you update a plugin or theme that they update their CSS files. You can turn this off by enabling the “Disable Auto Queue” option.

    If you have a hard time fixing it all by yourself, Please send a support ticket to our support channel and we will help you resolve any conflicts that you may have.

    Regards,
    Shakeeb

    Thread Starter rinart73

    (@rinart73)

    1. Yes the cached pages are served statically in my case. From what I understand I will have to manually add sitemap again when I create new pages, correct?
    May I suggest adding optional AJAX request to the frontend RapidLoad script that would notify the backend that page is visited and add it to a queue automatically?

    • This reply was modified 2 years, 4 months ago by rinart73.
    Plugin Author Shakeeb Sadikeen

    (@shakee93)

    Good idea, but sending that request from the frontend will open up a lot of space for vulnerabilities. I suggest you clear all your page cache once, or use the sitemap to add all pages to the queue.

    Thread Starter rinart73

    (@rinart73)

    I’m getting RapidLoad warnings “Response code 410 (Gone)” and “RapidLoad optimized version for the file missing” even though before those pages were optimized normally. And despite warning they’re not getting automatically requeued.

    Thread Starter rinart73

    (@rinart73)

    I’ve noticed that the 410 code points to inline CSS and Autoptimize CSS merged file. Does CSS merging conflict with RapidLoad?

    • This reply was modified 2 years, 4 months ago by rinart73.
    Plugin Author Shakeeb Sadikeen

    (@shakee93)

    @rinart73 There was a bug with finding back the original CSS file for a missing uucss file. It’s been fixed and will be released with the next update.

    Plugin Author Shakeeb Sadikeen

    (@shakee93)

    @rinart73 The latest update is live with the hotfix. Please test and let me know if you are still having this issue.

    Thread Starter rinart73

    (@rinart73)

    Situation has become better it seems. Although the home page still has: “RapidLoad optimized version for the inline style missing. //inline-style@fc5d2170920e18e402aa1b9731822ba3”

    • This reply was modified 2 years, 4 months ago by rinart73.
    Plugin Author Shakeeb Sadikeen

    (@shakee93)

    We will identify any critical warnings and RapidLoad will automatically re-queue the jobs if it does. So you can re-queue it and the warning will disappear.

    In some cases there are dynamic inline CSS will be injected by some plugins. If it is the case you will have to turn off optimizing inline CSS blocks. This won’t affect your page score though.

    Please let me know if you have any further questions, I’ll be happy to answer you.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Issues with plugin and with WP Fastest Cache’ is closed to new replies.