• Be warned !!!

    If you don’t edit your htaccess file following the advanced configuration found here :

    https://www.keycdn.com/support/wordpress-cache-enabler-plugin/#advanced-configuration

    Then the redirect to the cached files will be made by… PHP… so a lot slower than htaccess.

    The devs really need to add the ability (that WP Super Cache has) to write the needed htaccess rules from the plugin UI directly.

    At the end of the day, if you want webP support you’ll either have to use this plugin… and edit the htaccess files to handle the redirect to the cached files… or use WP Super Cache and manually add the htaccess rules to point to the webP files…

    So, so far, you’ll have to edit manually your htaccess one way or the other, a bit of a pita. Hopefully the devs will add the htaccess rules injection quite soon.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author KeyCDN

    (@keycdn)

    Well, this depends on what plugins you are using.

    The advanced snippet is only need if you have a slow PHP code base, which seems to be the case in your setup.

    E.g. having PHP 7 and only a few lightweight plugins makes the snippet obsolete.

    Thread Starter aguett

    (@aguett)

    Well, you’re the expert, but I have NEVER heard anyone saying that PHP redirect was faster than htaccess / nginx redirects !

    So you’re officially the first 😉

    Joke appart I would bet that 95% of users will have a performance decline by using PHP redirects instead of htaccess, so this snippet is probably not going to disappear anytime soon.

    Kjetil

    (@kjetilgf)

    For those of us not that techy, does this mean we rather should edit the htaccess file than not? Any risk it would do any harm?
    I’m on php 7 on a couple of sites, the rest not.
    Thanks

    Thread Starter aguett

    (@aguett)

    Not techy: don’t bother editing htaccess.

    That’s a current big minus of this plugin right now. Either you don’t edit htaccess and performance won’t be crazy (unless you have an optimized setup, in which case chances are you are techy or have a tech guy), or you need to edit htaccess yourself (without the quick and dirty button WP Super Cache offers), and if you do that, I suspect uninstalling the plugin and forgetting to edit back the htaccess could end up nightmarish.

    Kjetil

    (@kjetilgf)

    Hi – Thanks for coming back to me
    Editing the htaccess is easy enough. Though my question was a bit clumsy, it was more a question about it being of any importance to insert that script in the htaccess file when the server is running on php 7. Just seeing that it still works, answers my initial question.
    By the way:
    On Pingdom, page speed is not much changed (yet – I guess it takes a bit time to build the cache), but the performance grade is rised from 64 to 97.

    Plugin Author KeyCDN

    (@keycdn)

    Adding the htaccess snippets will give you the best performance results. However, it can break your site if you have a special setup.

    Kjetil

    (@kjetilgf)

    OK – thanks
    It seems to work fine. After 24 hours the frontpage of our site is +/- 1-1,5 sec quicker, which is great (but also the (shared) server’s initial reponce is also quicker today, so it’s hard to be precise :o)

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

The topic ‘WARNING: Bad performance unless you edit htaccess’ is closed to new replies.