• Resolved JDTravel

    (@jdtravel)


    Hi there,

    I have the same issue that @deanysus posted nearly a year ago.

    The WordPress Redirection plugin is reporting dozens of 404s to .js and .ccs files such as wp-content/cache/autoptimize/js/autoptimize_758b987dfc913fc72cbce2b… caused by Autoptimize when Googlebot accesses my site.

    The reply to @deanysus post was to update the autoptimize .htaccess file to change 404 error to 401 error. Support mentioned that the code to do so has already been posted in this support forum but I cannot find it. Please could this be reposted if relevant.

    I am using Siteground memcache and Cloudflare , could this be causing the issue.

    I have disabled Autoptimize temporarily.

    Please could you help on this Thank you.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    well, first and foremost; disabling AO will not help ??

    the problem is that Google is using pages of your site in its own cache and those (older) pages refer to old AO’ed CSS/ JS that was removed when you cleared AO’s cache, disabling AO does not change this.

    secondly; although it can be hard on they eye & heart, having those errors is actually a minor issue; this has no impact on visitors and -as far as I know- does not get penalized by big G (see also this reply on stackexchange).

    If you absolutely want to, you can “fix” this with this solution.

    hope this clarifies,
    frank

    Thread Starter JDTravel

    (@jdtravel)

    Hi Frank,
    Thank you for the prompt answer, much appreciated.
    I’m using Siteground hosting and use there caching options and Cloudflare.
    Siteground advised me to remove WP Super Cache from my site as it was clashing with their own cache. Also Cloudflare has options to minimize js, css amd html, that’s another reason I removed Autoptimize. It can be quite confusing at times especially since Siteground had previously said that their cache would complement WP Super Cache. Sometimes it just seems like trial and error to see what works best.
    Thanks for posting the link to the fix, I’ll have a look at it.
    Regards
    John

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    Evening John; I’m biased (obviously), but based on my own performance optimization service experience, AO outperforms Cloudflare’s minification (esp. if you use some of the “extra” features, of which more are coming). The thruth is in the testing-results though! ??

    frank

    Thread Starter JDTravel

    (@jdtravel)

    Hi Frank,
    Yes, Autoptimize does work very well it has improved page load speed very well according to Google Page speed Insights. Although the results are not always consistent which is probably due to the state of the cache and whatever else is going on in the server at the time. Yes agree the truth is in the test results, lots of test results! ??

    John

    I tend to agree with Frank. I use Autoptimize and siteground cacher. Also with cloudflare, but i remove the option to minimize etc, on cloudflare and allow for autoptimize to do this… works better, when i tested it. Just my two cents.

    Thread Starter JDTravel

    (@jdtravel)

    I tend to do a lot of site tweaking and delete the cache quite often which I understand is not recommended when using autoptimize. This causes problems with with Googlebot trying to access old autoptimize cache js and css cache files.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘404 autoptimize errors’ is closed to new replies.