Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Author Raul P.

    (@alignak)

    Hi there,

    Is that on Google Chrome or Firefox.

    If it’s Firefox, take a look at this: https://stackoverflow.com/questions/45879671/only-on-firefox-loading-failed-for-the-script-with-source

    If it’s on Chrome, I’ll need a bit more info on that.
    Do the .js files open if you copy paste the .js urls in your browser directly?

    If they don’t, it could be file permissions on the server.
    Check that your wp-content/uploads directory has write permissions and is owned by the correct username, then purge FVM cache.

    FVM will replicate the file permissions of the uploads directory.

    Thread Starter johndos

    (@johndos)

    It was on several browsers mozilla,chrome, safari, ie but I could not wait for long so I rolled back.

    Plugin Author Raul P.

    (@alignak)

    Can you try the latest update and see if it works?

    If it doesn’t, can you save a copy of your frontend html (save as html from your browser, as logged out user) and send it to me? I need to evaluate if there is something wrong with how FVM is merging the js files in the html code.

    Thread Starter johndos

    (@johndos)

    sure give me a about 20 minutes to backup everything and I will give it a try

    Thread Starter johndos

    (@johndos)

    it seems its working mate for now but I will monitor it for a few days to see if something comes up

    Thread Starter johndos

    (@johndos)

    nope after I cleared cache today everything is rumbled again. This is what you want? https://files.fm/u/e4e9x8wz

    • This reply was modified 7 years, 8 months ago by johndos.
    • This reply was modified 7 years, 8 months ago by Jan Dembowski.
    Thread Starter johndos

    (@johndos)

    I just now uploaded the cached files from 4-5 days ago and it started loading again. I am not sure what’s wrong

    Thread Starter johndos

    (@johndos)

    Hey guys I am still experiencing the same issue. https://files.fm/u/nd6kdjka this is the console log. Can you check it out? This time it happened without even clearing FMV cache which is weird.

    • This reply was modified 7 years, 8 months ago by johndos.
    • This reply was modified 7 years, 8 months ago by Jan Dembowski.
    Plugin Author Raul P.

    (@alignak)

    You are the only person complaining about this, so I am inclined to say it’s something related to your server, which may have changed around the time you updated.

    Furthermore, accessing your site shows an error:
    http://prntscr.com/me7mn2

    Anyway, looking at the error messages on the log you attached, it says:

    header-ceb60cc1-1548416754.min.js:1 Failed to load resource: the server responded with a status of 404 ()

    This “should only happen” if you purged the FVM cache files without purging your page cache. That page cache can be from a plugin you use, or something on the server side.
    I would suggest, for your server to select the option to preserve cache files on FVM settings.

    HOWEVER, further down I see references to rocket-loader.min.js which if I am not wrong, comes from cloudflare.

    Auto Minify, Mirage and Rocket Loader must be disabled at the Speed tab, on Cloudflare.

    Not only those options slow down your site (even without FVM), but they are know to cause conflicts in many websites.

    Mirage for example, states:

    Mirage is considered Beta because it’s an experimental feature that may cause issues displaying images in association with certain Javascript libraries, such as image carousels or photo viewers. Issues with Mirage affect only a small percentage of customers.

    HTML Minify option will cause doing double minification, which can cause conflicts. Double minification, should not occur under any circumstances, ever.
    If FVM is already doing it, you are slowing down the site by doing it yet again on cloudflare.

    Rocket Loader is a pure scam too. On all the sites I have tried to use it, it slowed down the execution time for mobile users.

    I love cloudflare and I use them extensively with hundreds of sites, but I don’t know what cloudflare was thinking when they came out with this option. Using more javascript, to speed up slow javascript… just doesn’t make sense.

    Disable those settings and purge all caches, server, fvm and cloudflare.

    Thread Starter johndos

    (@johndos)

    Well I have disabled the extra cloudflare rocket loader and running gtmetrix to check for the difference, and also cleared all cache site and cloudflare wise, with FMV I am using Super Cache as well but when clearing FMV cache also clears Super Cache as well.

    Thread Starter johndos

    (@johndos)

    So for some reason it just worsened the scores. It UP-ed the Fully Loaded Time/Total Page Size and Requests and it dropped in PageSpeed and YSlow Scores after I disabled the minify and rocket loader on cloudflare.

    • This reply was modified 7 years, 8 months ago by johndos.
    Plugin Author Raul P.

    (@alignak)

    Yes, but tests are always inconsistent.
    Repeat the test a few times and you will see different loading times.

    As for rankings, you have to look down to the recommendations section and compare before and after.

    Thread Starter johndos

    (@johndos)

    These are the changes and it is kind of strange is it not?

    For the YSlow it’s : Make fewer HTTP requests from 56 to 0, Add expire headers from 56 to 34, Reduce DNS lookups from 35 to 40 (this one strangely went up) Use CDN from 100 to 80.

    And for the Page speed it is : for the Defer Parsing of JavaScript from 100 to 44, Optimize Images from 59 to 61 (strangely went up) Serve Scaled Images from 83 to 76, Optimize the order of Styles and Scripts 92 from 100,

    Thread Starter johndos

    (@johndos)

    that’s the link if you wanna check it out
    https://gtmetrix.com/compare/UStPz1kf/3UImY5nN
    I still don’t get it

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

The topic ‘loading failed for the … etc’ is closed to new replies.