Support » Plugin: WP-Optimize - Clean, Compress, Cache. » bloated and buggy

  • werdpres

    (@werdpres)


    the developers decided to fatten the already bloated plugin with page caching because apparently they prefer the ‘we-do-it-all’ approach which of course all too often results in doing nothing well

    no thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • joemilesudp

    (@joemilesudp)

    Thanks for your feedback. We agree that it’s only worth launching something if we think it’ll do something at least as well as the alternatives. There’s no point launching something that’s second best – because why would anyone use it?

    So we’ve built the caching part around the best established caching engine technology we could find, and we’ve spent a couple of years improving it. As a result, our tests of the caching part of the plugin show this rivals or beats every caching plugin currently on the market on caching alone.

    However, once combined with database and image optimization, this beats all the competition by some margin. For example, our test site which took 4.2s to load without cache, takes the following time with the alternatives when configured:

    – WP Rocket: 2.0s
    – W3 Total Cache 2.4s
    – WP-Optimize: 1.7s

    In other words the site is 15% faster than with with WP-Rocket and 30% faster than W3 Total Cache.

    We’d encourage you to run your own tests comparing WP-O with the alternatives and send us the results. Otherwise the statement ‘if it tries to do everything, then it’ll do nothing well’ is just an assumption.

    • This reply was modified 2 months ago by  joemilesudp.
    werdpres

    (@werdpres)

    […] once combined with database and image optimization, this beats all the competition by some margin.

    have you tested with the LiteSpeed cache plugin on a server running LS? otherwise the statement that WP-O “beats all the competition by some margin” is just an assumption

    even the basic functions of WP-O fall short – after dumping WP-O i installed Plugins Garbage Collector and it found a bunch of db tables that were left by 4 plugins i uninstalled long ago which further reinforces my statement that trying to do everything results in doing nothing well

    There’s no point launching something that’s second best – because why would anyone use it?

    agreed

    Plugin Author David Anderson

    (@davidanderson)

    Plugins Garbage Collector (you can read the source) detects unused tables by crude string matching on the contents of code in wp-contents/plugins. So, it’ll find more than WP-O, because WP-O errs on the side of false negatives – it only lists as “unused” tables it can definitively categories, rather than on the side false positives (e.g. perhaps you have a theme that creates tables – PGC will list those as unused). So, the metric we’re using for “best” there isn’t “will find+delete everything possible, including stuff it shouldn’t”.

    I’ve explained this because it seemed to be important to you. I do get something of the feeling, though, that you made your mind up already, as you posted this 1-star review minutes after opening a support request and before anyone on our team could even know it had existed. We are very happy to engage with constructive feedback.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this review.