• Resolved grafx77

    (@grafx77)


    LoftLoader will only load at the last second of the page load, near the very end. How do I get it to load as intended, just as as soon as a page loads?

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter grafx77

    (@grafx77)

    NOTE: please browse the site as you may likely view a “cached” page which will load quickly and show the loader quickly. The pages that are not cached will load the loftloader at the very end.

    Plugin Author loftocean

    (@loftocean)

    Hi,

    Thank you for contacting us.

    We visited your website in different browsers on different computers, but when the page opens, the preloader shows immediately every time, even when the page opens in our browser for the first time (so the page is not cached). We did not see the problem you mentioned.

    If the preloader is displayed late on the website, this problem usually occurs because the site is using some caching/performance optimization plugins. You may like to read the FAQ “LoftLoader doesn’t work properly” for more information.

    Thank you very much.

    Best regards,
    The Loft.Ocean Team

    Thread Starter grafx77

    (@grafx77)

    No.

    The page loads for a very long time before your loader appears. This is generally due to the loader being suppressed til the end of the page load. I was asking you if there is a way where I can have the loft loader, load at the very beginning of a page load (move code to the header of the page).

    Your loft loader is NOT working properly with or without cache plugins. I’d like to purchase the pro version, but your support is still lackluster. I can’t purchase a plugin that doesn’t work properly with little to no support.

    Plugin Author loftocean

    (@loftocean)

    Hi,

    Thank you for your reply.

    We recorded a video of what we did on your website, please click this link to see it.

    In the video, you can see that we first cleared the browser cache, then entered your website URL in a new tab. You can see that the preloader was the first element that appeared on your website. The logo loaded (revealing from bottom to top) more than twice, then the page was fully loaded, the preloader disappeared, and the page content displayed.

    Then we clicked on a few menu items, and the preloader was immediately displayed on each page (please note the URL was changed in the browser’s address bar, which means the new page was opened at that time).

    Then at timeline 0:46 we clicked on the site logo to return to the (cached) homepage. This time the preloader disappeared earlier than when we first visited the home page. You can see the differences.

    Then we went to another page, cleared the browser’s cache again, then went back to the homepage again, this time the loading time was much longer than the last time, because the cache has been cleared.

    Therefore, we really did not see the problem you mentioned.

    And here is the code logic of LoftLoader Lite:

    1). The CSS code (controlling the prealoder style) will be loaded in the < head > section.

    2). The HTML code of LoftLoader will be added to the first place inside of the < body > section via PHP code, so usually it will be the first HTML element on a web page. All other HTML content will be loaded afterwards. Sometimes other plugins may add their HTML code to the first place in the < body > section in the same way. When this happens, it’s unpredictable which plugin’s HTML code will be the first element. For example, we found that there is another div element ( < div id=”yith-wcwl-popup-message” > ) before LoftLoader’s div on your site. But it does not seem to affect LoftLoader.

    Therefore, once the LoadLoader’s CSS and HTML code are loaded, the preloader will display immediately.

    3). The JS code will be placed in the footer because this is the WordPress coding standard. The JS code in the Lite version is very simple: detect when the page is fully loaded so that it ends the preloader. Therefore, even if the JS code has been put in the footer of the site, it will not affect the results.

    In the FAQ, we mentioned that a cache/performance optimization plugin might move all JavaScript/CSS on your site into the footer of your page (and minify these code to optimize the web speed). This is the main reason why LoftLoader loads later than the page content. If it is the cause, the solution is to exclude files of LoftLoader.

    And there may be another reason (although this rarely happens): if there are multiple preloaders on the same website, it can cause problems. Other preloaders can be created by other preloader plugins installed, or it might be a functionality in the theme. If this is the reason, then the user only needs to deactivate the other preloader plugins and disable the preloader functionality in the theme.

    Since we don’t see the problem, we don’t know the exact cause of the problem. We can only rely on experience to speculate on the cause of the problem and give some advice.

    Sorry to hear that you are not satisfied with our support. In fact, our support services have always been highly praised by our users (both lite and pro versions). And we are very proud of this.

    Because we didn’t see the problem while checking your site, and in the FAQ it mentioned the solution when there was a similar problem. We guessed that you may have seen the FAQ and fixed the problem on your website. In addition, most users do not like to see a lot of professional explanations, preferring to get solutions directly. Therefore, we usually use the most simplified sentences when supporting our users.

    Thank you very much.

    Best regards,
    The Loft.Ocean Team

    • This reply was modified 7 years, 2 months ago by loftocean.
    Thread Starter grafx77

    (@grafx77)

    Thanks for the video and the “more extensive” troubleshooting this time around.

    So when I stated “cached” page above, I was talking about the sites cache, not your browser cache. I realize I didn’t clearly make the distinction. You only viewed the homepage and a category page which was already internally cached by our WP Rocket cache plugin.

    If you viewed one of the product pages, you would see that the LoftLoader takes a while to load before it shows up, which is near the end of the page load.

    Fortunately, this was a site that I was selling and just recently sold it to a new owner. I will revisit this thread again in the near future and showcase the bug on another store of mine.

    Thanks

    Plugin Author loftocean

    (@loftocean)

    Hi,

    Thank you for your reply.

    Here are some suggestions for your reference:

    1. If the problem you see is: When the page is opened, the content on your page shows first, then the preloader appears.

    Then this may be a problem caused by a conflict between our plugin and other plugins. As we mentioned in the previous reply, it may be caused by the cache plugin, and the solution is to exclude the LoftLoader file from the cache plugin.

    2. If the problem you see is: When you visit your website or refresh a page, if you see your page is blank before the preloader displays, it means that the browser has not received any data of that page from your server.

    And a similar situation: If you click the links to jump between pages, it takes a while to leave the current page (please note if the URL in the browser address bar changes), which also means it takes a long time to receive data of the new page from your server.

    Server response time measures how long it takes to load the necessary HTML to begin rendering the page from your server. As a part of HTML of your page, LoftLoader will only show when the necessary HTML is loaded from your server.

    Therefore, if this happens on your website, you will need to improve the server response time.

    Please test your site via Google PageSpeed Insights.

    And you may like to read the following resources:

    3. If the problem you see is: When you visit your website or refresh a page, if you only see the preloader’s background color you set (for example, the preloader background color on the website you mentioned is black), but the loader image (the logo) is not displayed immediately. Then after a while, the loader image finally shows.

    This problem is also caused by a slow server response time. The preloader is displayed (HTML & CSS are working), but the data for the logo image has not been returned from the server.

    If this is the case, you can try changing to another loader animation that doesn’t use a custom image, such as dots, waves.

    You can also try to improve server response time.

    If you still need our support in the future, please provide the following information:

    • You website URL.
    • The URL of the page(s) where the issue occurs.
    • Please also record a video and show us the problem you see, and we can also see how to reproduce the problem.

    Thank you very much.

    Best regards,
    The Loft.Ocean Team

    Plugin Author loftocean

    (@loftocean)

    Topic closed due to inactivity.

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

The topic ‘Load Before Anything Else’ is closed to new replies.