This topic has 9 replies, 4 voices, and was last updated 9 years, 4 months ago ago by Eva Kemp
Hello,
When i loading the homepage http://www.polydesignbvba.be/nl/ it hangs in Chrome-browser.
All the other pages works good in Chrome but the homepage not working.
(The homepage works perfect in Firefox and Safari!)
In the backend I can go to the ‘home’ page and edit it with Visual Composer and save it. But when I look in the frontend the problem doesn’t solved.
In the developer console I see several errors, see screenshot.
I hope you can help me please? Or have you any idea how solve this problem?
PS: I few days ago the site works perfectly. The only thing i did in the past days was adding 4 products for showing the webshop to my client. Thats it!
Regards,
Christophe
I think it’s a problem with the loader-icon.
If disable ‘Show loader icon until site loading’ then it works in Chrome-browser :-/
Regards,
Christophe
Hello,
I’ve just checked your site and there are no problems with home page loading even when option “Show loader icon until site loading” is enabled. Here is the screenshot http://prntscr.com/7z5hf5
Please clear browser cache and check the site.
Best regards,
Jack Richardson.
Hi,
Thanks for the support.
It works!
Regards,
Christophe
Hi,
It works perfect on another pc or laptop, but not on my pc or Chromebook, it hangs, even after clear browser cache it doesn’t work. Only the homepage.
I trying reloading but on my Chromebook don’t work anymore.
Strange!
Christophe
Hi,
I FIND IT!
It was a browser plugin that hangs the homepage!!!!
Thats the ‘bad’ plugin:
https://chrome.google.com/webstore/detail/pagexray/aedmpdookgbneegaeajpoldpnpfbpmlb
Now it works perfect!!!!!
Regards,
Christophe
Hello Christophe,
is your problem solved now?
Regards,
Stan Russell.
Hi Stan,
Yes the problem is solved.
I removed the browser-plugin and now it works perfect 🙂
Regards,
Christophe
Hello,
Glad to hear it.
Have a nice weekend.
Regards,
Eva Kemp.
The issue related to '‘Homepage stop working (hangs) in Chrome browser’' has been successfully resolved, and the topic is now closed for further responses