Viewing 12 replies - 1 through 12 (of 12 total)
  • Hi japanworm,

    Try deleting WP Performance Score Booster from your plugins (you don’t need this with W3TC), clear all caches, then re-check .HTACCESS to make sure WP Performance Score Booster is no longer writing. You should also make sure to remove anything manually added to .HTACCESS related to caching, as W3TC manages all Best Practices according to the setting you choose.

    Best,
    AJ

    Thread Starter japanworm

    (@japanworm)

    Hello,
    thank you so much.
    Are you saying I should delete everything that is within this:
    # BEGIN WP Performance Score Booster Settings?
    Also the GZIP compression?

    As for browser catching, I suppose you’re referring to this?
    ## BEGIN Expires Caching (Leverage Browser Caching) ##
    (….)

    First, try deleting WP Performance Score Booster from your plugins in WP Admin –> Installed Plugins; then, clear all caches. You don’t need this plugin with W3TC and it could be causing some sort of wonky conflict with the enabling of Keep Alive since WP Performance Score Booster also writes to .HTACCESS.

    Best,
    AJ

    Thread Starter japanworm

    (@japanworm)

    I don’t have a plugin that’s called “WP Performance Score Booster”.

    I think what you see between the hashtags is something I found online and added manually to my HTACCESS file.

    Make sure to triple check that WP Performance Score Booster is indeed not installed, since it will continue to write to .HTACCESS even if you delete what it/you added.

    Regardless, yes: remove anything having to do with WP Performance Score Booster.

    Best,
    AJ

    Thread Starter japanworm

    (@japanworm)

    Ok, it seems to work now.

    I double-checked, but I don’t have the plugin or any plugin files anywhere. I’m not even sure I ever installed that plugin.

    Thank you! ??

    ??

    Thread Starter japanworm

    (@japanworm)

    Unfortunately, it’s still not working.

    I still think it’s got to do with W3 Total Cache as it only happens when it’s enabled.

    My new HTACCESS file looks like this: https://pastebin.com/7bWg3kXy

    Any other ideas?

    So it was working then stopped?
    You are certain your host supports Keep Alive?
    Are there errors in your error logs?
    Have you tried removing everything that writes to .HTACCESS except W3TC and everything in .HTACCESS except what W3TC has written (without removing the .HTACCESS directive you’ve added)?

    Best,
    AJ

    Thread Starter japanworm

    (@japanworm)

    I’m confused.
    Most of the time I get a “Keep alive enabled” when I’m testing.
    Only sometimes and on some articles it doesn’t seem to be enabled.

    Does that make any sense?

    If Keep Alive is enabled it should be enabled everywhere, mate.

    Looks like it is in fact working: https://www.webpagetest.org/result/150526_C3_T6T/

    Best,
    AJ

    Thread Starter japanworm

    (@japanworm)

    Thank you.
    I used this to check: https://www.feedthebot.com/pagespeed/
    And sometimes the Keep Alive seems to be off according to that page.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘W3 Total Cache kills "Keep Alive"?’ is closed to new replies.