Title: robeyupdraft's Replies | WordPress.org

---

# robeyupdraft

  [  ](https://wordpress.org/support/users/robeyupdraft/)

 *   [Profile](https://wordpress.org/support/users/robeyupdraft/)
 *   [Topics Started](https://wordpress.org/support/users/robeyupdraft/topics/)
 *   [Replies Created](https://wordpress.org/support/users/robeyupdraft/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/robeyupdraft/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/robeyupdraft/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/robeyupdraft/engagements/)
 *   [Favorites](https://wordpress.org/support/users/robeyupdraft/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] Great Cleanup Tool](https://wordpress.org/support/topic/great-cleanup-tool-2/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/great-cleanup-tool-2/#post-18876097)
 * Thanks Bernard, glad the cleanup made a noticeable difference. WordPress databases
   have a real knack for hoarding old revisions, transients, and leftover junk from
   plugins you uninstalled months ago, so a good clear-out usually pays off.
 * If you want to keep that “smoother” feeling without having to remember to run
   it, head to **WP-Optimize > Database > Settings** and set up a schedule. Weekly
   is a sensible default for most sites.
 * Worth mentioning too: WP-Optimize isn’t just a database tool these days. The 
   same plugin also handles **page caching**, **image compression and WebP conversion**,
   and **CSS/JS minification**. If your site feels smoother after a database clean,
   it’ll feel faster again once those are switched on. Might be worth a poke around
   the other tabs when you get a moment.
 * Thanks again from the team.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] Great Product!](https://wordpress.org/support/topic/great-product-1217/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/great-product-1217/#post-18876094)
 * Thanks Jeff, really appreciate you taking the time to leave a review. The feature-
   rich free version is something we feel strongly about keeping that way. A huge
   chunk of WordPress runs on sites that can’t justify another monthly subscription,
   and we’d rather those sites have access to proper performance tools than lock
   all the good stuff behind a paywall.
 * Thanks again from the team.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] WP-Optimize Database Performance](https://wordpress.org/support/topic/wp-optimize-database-performance/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/wp-optimize-database-performance/#post-18876092)
 * Thanks for the review, and glad to hear your site is loading faster after a cleanup.
   The database side of things is where WP-Optimize started all those years ago,
   so it’s always nice to hear it’s still pulling its weight.
 * One quick tip: if you head into **WP-Optimize > Database > Settings**, you can
   schedule the cleanups to run automatically on whatever cadence suits your site,
   so the junk never really gets a chance to build up.
 * Something a lot of our long-time users don’t realize: WP-Optimize has grown well
   beyond database cleanup over the years. It’s now a full performance suite, and
   all of it is in the free plugin you already have installed. Worth a look if you
   want to squeeze even more speed out of your site:
    - **Page caching** to serve pages without hitting PHP or the database on every
      request
    - **Image compression** (including WebP) to shrink one of the biggest sources
      of page weight
    - **Minification** of CSS and JavaScript, with options to defer and async scripts
    - **Preloading** so your cache is warm before visitors arrive
 * Pair those with the database work you’re already doing and you’ll likely see 
   another jump in load times. Thanks again from the team.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] Reliable All-in-One Optimization Solution for WordPress](https://wordpress.org/support/topic/reliable-all-in-one-optimization-solution-for-wordpress/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/reliable-all-in-one-optimization-solution-for-wordpress/#post-18876086)
 * Thank you for taking the time to write such a thoughtful review, this is exactly
   the kind of feedback that makes our day.
 * You’ve actually put your finger on one of the things we care about most: the **
   all-in-one angle**. A lot of WordPress sites end up stacking a caching plugin,
   an image optimizer, a database cleanup tool, and a minifier all on top of each
   other, and the irony is that the plugin bloat starts eating into the performance
   gains you were chasing in the first place. Keeping everything under one roof (
   and one settings page) is a deliberate design choice, so it’s really rewarding
   to hear it landing the way we hoped.
 * We’re also glad the balance between beginner-friendly and powerful-enough-for-
   advanced-users is working for you. That’s a surprisingly hard line to walk, and
   it’s something we’re always tweaking.
 * If you ever bump into something that could be smoother, the support forum is 
   the fastest way to get it in front of us. Thanks again from the whole team.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] Great plugin](https://wordpress.org/support/topic/great-plugin-41377/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/great-plugin-41377/#post-18876081)
 * Short review, big smile on our end. Thanks for the five stars, and for taking
   a moment to let us know WP-Optimize is doing its job. Reviews like this genuinely
   make the team’s day, so cheers from all of us.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] Excelente](https://wordpress.org/support/topic/excelente-4229/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/excelente-4229/#post-18876079)
 * Muito obrigado pela avaliação! Ficamos felizes em saber que o WP-Optimize está
   atendendo às suas expectativas. O seu apoio significa muito para a nossa equipe.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] Рахмет.](https://wordpress.org/support/topic/%d1%80%d0%b0%d1%85%d0%bc%d0%b5%d1%82-2/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/%d1%80%d0%b0%d1%85%d0%bc%d0%b5%d1%82-2/#post-18876077)
 * Жылы пікіріңіз үшін рахмет! WP-Optimize сізге пайдалы болып жатқанына қуаныштымыз.
   Қолдауыңыз бізге көп нәрсені білдіреді.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] Can interfere with other elements/plugins](https://wordpress.org/support/topic/can-interfere-with-other-elements-plugins/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/can-interfere-with-other-elements-plugins/#post-18876072)
 * Hi [@yb1313](https://wordpress.org/support/users/yb1313/), thanks for taking 
   the time to leave feedback. I’m Robey, Product Manager for WP-Optimize, and I’d
   like to help you get to the bottom of this rather than leave it as an unresolved
   conflict.
 * You wrote: _“it caused a rotating graphics element that I had on my website, 
   to malfunction and mess up its clickable links. After disabling the WP-optimize
   plugin, the issue was resolved.”_
 * That description points very strongly to a specific, fixable cause: our Minify
   feature was almost certainly merging or minifying the JavaScript that powers 
   your slider or carousel, and the merged bundle broke the script’s initialization.
   Sliders are one of the most common categories of plugin that need their JS excluded
   from processing, because they often rely on specific load order and inline configuration
   that don’t survive being combined with other scripts.
 * The good news is you don’t have to choose between optimization and a working 
   slider. There are two straightforward options:
    1. Go to **WP-Optimize → Minify → JavaScript**
    2. Scroll to **Exclude JavaScript from processing**
    3. Add a wildcard pattern matching the slider plugin’s folder, for example `*/plugins/
       your-slider-plugin-name/*`
    4. Save, then purge the cache from **WP-Optimize → Cache**
 * Minification conflicts are a real category of problem, and we take them seriously.
   A few things worth knowing:
    - We maintain a growing list of default exclusions for known-problematic scripts,
      and we add to it with every release.
    - Every cache and minification plugin on the market, including the paid ones,
      requires some level of per-site tuning when aggressive JavaScript optimization
      is involved. It isn’t a flaw unique to WP-Optimize, but that doesn’t mean 
      we can’t do better at guiding people through it, and we’re actively working
      on exactly that.
 * If you’re willing to give it another try, please open a thread in the [support forum](https://wordpress.org/support/plugin/wp-optimize/)
   with the name of the slider and a link to the page where it was breaking. We’ll
   make sure you get a working configuration, and if we can reproduce it, we’ll 
   add the fix to our defaults so it stops being a problem for everyone.
 * Either way, I appreciate the feedback. The only reviews we learn nothing from
   are the ones nobody writes.
 * Robey
   Product Manager, WP-Optimize
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] Trash it, before it kills your conversions.](https://wordpress.org/support/topic/trash-it-unless-it-kills-you/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/trash-it-unless-it-kills-you/#post-18876068)
 * Understood, and thanks for the honest follow-up. I’m not going to try to talk
   you back into the product. You’ve made the call, and given the time pressure 
   you’ve described it’s a reasonable one.
 * A couple of things I do want to acknowledge for anyone else reading this thread.
 * > I don’t have time for a PhD in plugin configuration.
 * This is fair, and it’s the part of your feedback I find most useful. When a Woo
   cart issue surfaces, the path from “something is wrong” to “this setting caused
   it” is too long in our product today. Shortening that path, with clearer conflict
   detection and a faster way to isolate whether WP-Optimize is actually the cause,
   is something we’re actively exploring. I can’t undo the hours you’ve already 
   lost, but I can tell you it’s landed with the team.
 * Thanks for the time you spent writing this up, even in frustration. It’s more
   useful than silence.
 * Robey Joyce
   Product Manager, WP-Optimize
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] Trash it, before it kills your conversions.](https://wordpress.org/support/topic/trash-it-unless-it-kills-you/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/trash-it-unless-it-kills-you/#post-18874825)
 * Hi [@and4zej](https://wordpress.org/support/users/and4zej/), Robey here. I’m 
   the product manager for WP-Optimize. Thanks for taking the time to write this
   up. A couple of your points describe behaviour we’d treat as critical if reproduced,
   and the rest I think we can clear up. Let me take them one at a time.
 * > WP-Optimize fails to fully de-register its components even when caching is 
   > toggled off in the UI. Its hooks and filters remain active on every page load[…]
   > Crucially, the “disable” toggle only stops the generation of new cache files;
   > it doesn’t cease the plugin’s interference with WooCommerce internals.
 * You’re partly right, and it’s worth being precise about what’s happening. When
   page caching is disabled via the toggle, WP-Optimize stops serving and writing
   cached pages, but some hooks do remain registered. Specifically, the ones that
   manage:
    - Purge triggers (so the plugin knows when to clear cache on content changes)
    - Exclusion rules and conditional tags
    - The admin UI and settings screens
 * That’s by design, and it’s the same pattern every major cache plugin uses, because
   those hooks need to be present for the plugin to respond to settings changes 
   and purge events. What those remaining hooks should **not** be doing is modifying
   the `wc-ajax=get_refreshed_fragments` response. If you’re seeing evidence that
   they are, that’s a bug I want to see fixed, not defended.
 * > This results in critical UI failures, such as customers seeing incorrect cart
   > contents or random items.
 * This is the claim I’m taking most seriously. A cache serving one customer’s cart
   to another is a critical issue, and it’s not something we’ve been able to reproduce
   in-house or seen reported through our support channels. To investigate properly
   I need more than I can get from a review thread.
 * If you’re willing, please open a support topic at [wordpress.org/support/plugin/wp-optimize](https://wordpress.org/support/plugin/wp-optimize/)
   and include:
    - Your WP-Optimize version
    - Your WooCommerce version
    - Any other caching or optimization plugins active, including at the server 
      or CDN level
    - Your active theme
    - The steps that produced the incorrect cart contents, ideally with a timeline
 * If there’s a genuine session-bleed bug here I want my team to take a look ASAP.
 * > The “broken site” symptoms post-update are a direct result of 24-hour stale
   > cache being served, where outdated CSS/JS assets no longer align with the updated
   > plugin output.
 * Here I’d push back gently. The 24-hour figure is the default cache lifespan, 
   which is configurable under **Cache > Page cache > Cache options**. More importantly,
   WP-Optimize purges its own page cache and minify cache automatically when the
   plugin updates, so visitors shouldn’t be served stale assets from us after an
   update completes.
 * If you’re seeing stale CSS or JS after an update, the usual culprits are one 
   of the following:
    - A separate minify cache from another plugin
    - A CDN that wasn’t purged as part of the update
    - Browser cache on the tester’s own machine
 * Happy to help diagnose which, if you can share a specific example.
 * The public support forum is the right place to take this forward, and it’s where
   our team actively triages reports from our users. Open a topic with the details
   above and we’ll pick it up from there. I’d genuinely like to get to the bottom
   of what you saw.
 * Robey
   Product Manager, WP-Optimize
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] Catastrophic. Their backup plugin was excellent, but their caching plugin…](https://wordpress.org/support/topic/catastrophic-their-backup-plugin-was-excellent-but-their-caching-plugin/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/catastrophic-their-backup-plugin-was-excellent-but-their-caching-plugin/#post-18874815)
 * Hi Camille, thanks for taking the time to write this up, and sorry it’s taken
   us a while to respond. A Speed Index regression after installing a performance
   plugin is exactly the opposite of what should happen, so I want to address it
   properly rather than brush it off.
 * Page caching on its own almost never makes Speed Index worse. What can, and what
   we suspect happened here, is the minify and combine CSS/JS settings interacting
   badly with your theme. Merged and deferred stylesheets can delay first paint 
   on some themes even while server response time improves, and that shows up in
   Lighthouse as exactly the pattern you described: red scores, higher Speed Index,
   worse LCP.
 * We took this class of problem seriously enough that in version 4.5.0 (February
   2026) we **disabled CSS and JS merging by default**. If you installed before 
   that release, the old defaults were more aggressive than they should have been
   for a first-run experience, and that’s on us.
 * A few other things that commonly cause the symptoms you saw, in case any apply:
    - **Cache not preloaded yet.** The very first visit to each URL generates the
      cache file, so if you ran PageSpeed Insights right after activation, Lighthouse
      was measuring uncached pages. Enabling “Preload cache” and letting it finish
      changes the picture significantly.
    - **Another caching layer active.** If Cloudflare APO, LiteSpeed Cache, or a
      host-level cache was already running, the two can fight each other.
    - **GZIP doubled up.** If your server already sends GZIP, enabling it again 
      in WP-Optimize adds CPU overhead for no benefit.
    - **Delay JavaScript** enabled on a JS-heavy theme can push LCP later. It’s 
      off by default, but worth checking if you’d toggled it on.
 * If you’re open to giving it another try, the shortest path is: install 4.5.1 
   or later, enable only page caching and GZIP (leave minify off for now), run the
   preloader, then test. If Speed Index is still worse than baseline after that,
   please open a support thread at [https://wordpress.org/support/plugin/wp-optimize/](https://wordpress.org/support/plugin/wp-optimize/)
   with a URL and we’ll dig into it properly, it shouldn’t be happening and we’d
   want to understand why.
 * Either way, thanks for the honest feedback, it’s the kind that helps us make 
   the defaults better for the next person who installs.
 * Robey,
   Product Manager, WP-Optimize
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] Not working for me](https://wordpress.org/support/topic/not-working-for-me-314/)
 *  [robeyupdraft](https://wordpress.org/support/users/robeyupdraft/)
 * (@robeyupdraft)
 * [4 months ago](https://wordpress.org/support/topic/not-working-for-me-314/#post-18874811)
 * Hi Jan, Robey here, Product Manager for WP-Optimize. Thanks for the detailed 
   feedback. I’d rather respond to each point properly than brush it off with a 
   generic reply, so working through them in order:
 * > breaks websites with the newest Divi Theme (Divi 5)
 * If WP-Optimize is breaking Divi 5 sites, that’s a regression we need to reproduce
   and fix. I’d like to get this in front of our dev team directly. If you’re willing,
   please open a ticket at [teamupdraft.com/support](https://teamupdraft.com/support/)
   with your Divi 5 version and what specifically breaks, and I’ll flag it personally
   so it doesn’t sit in the queue.
 * > missing options to cache query strings (very important if you use WooCommerce
   > filter for example)
 * I want to make sure we’re talking about the same thing here, because WP-Optimize
   Premium does have a query variables setting by going to **Cache** → **Advanced
   settings** → **Ignore these query variables when caching**. You can list query
   string keys there that shouldn’t break cache lookup.
 * > impossible to completely disable/hide the image compression
 * You’re right. There isn’t a clean way to remove the entire image compression 
   module from the plugin today. The existing toggles do this much:
    - **Auto-compress new images on upload**: switches off automatic processing
    - **Show WP-Optimize meta box on media page**: hides the per-image controls 
      in the Media Library
 * The Images tab itself stays visible either way. It’s fair criticism, and it connects
   to a wider conversation we’re having about letting people turn off parts of the
   plugin they don’t use. Noted.
 * > my email address is shown in plugin list
 * This one I want to understand better before saying anything definitive. Are you
   referring to the licensed user email being displayed on **WP Dashboard** → **
   Plugins**?
 * If WP Rocket and WP Fastest Cache are working for you, I’m not going to argue.
   But the issues you’ve raised are ones we should either fix or explain properly,
   and I’d rather hear them than not. Thanks for taking the time to write this up.
 * Robey
   Product Manager, WP-Optimize

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