Slow loading

Hello @davet354tfd,

I took a look at your site and it seems that your site is behind multiple layers of caching (CloudFlare + something on the GoDaddy server). I think something is going wrong there, but I’m not sure if it’s due to your specific caching configuration or if it’s something we can prevent from within the plugin. I’ll take a closer look later today, but I just wanted to let you know that we’re on it.

Best,
Danny

Danny:

Sorry I didn’t see this sooner and replied. (Been a really busy few days).

Everything was working fine when I first installed Boxilla. Don’t really know when this started.
There is one piece of info that I forgot to add in the original post. Not sure if it is relevant or not.
Both these sites were originally on AWS. We moved them to GoDaddy due to the AWS not being as user friendly as GoDaddy.

Bob

@dvankooten:

Any progress on this isue? Been 2 weeks since you said you would look into it.

Bob

Hi Bob,

I’m sorry for the late reply, this issue had me scratching my head for a while. It doesn’t seem to be anything in our plugin itself but something in your website is off. The window.load event is firing after a couple of minutes where this should usually run within 2 or 3 seconds (after everything on your page has finished loading).

So there is something on your website which is delaying this event from firing, either because it is very slow to load or because it keeps firing off new requests. I have a feeling the Google Calendar widget may be causing this as it’s causing a lot of HTTP requests to occur, but it’s hard for me to confirm.

Can you try (temporarily) disabling some other plugins one-by-one to see which is the culprit?

Best,
Danny

Danny:

I have tried your suggestion. Disabled all the Plugins 1 at a time. So far still no change to Boxilla. When I am in WP and check the site Boxilla comes up fine. I have it set to test mode so it should come up every time I go onto the Home page, but it does not.

Is this something that you need to go into WP and check the site or is this something with GoDaddy that I can contact them about? I can set up an account so you could go into it and look around too if you want.

Just let me know how you want to proceed.

Thanks

Bob

Hello Bob,

Can you try updating Boxzilla to the version released yesterday? I made a change specifically for you, where the timer starts counting directly when the Boxzilla script has finished loading instead of when the full page has finished loading (which somehow takes minutes now that your site is on GoDaddy).

After updating Boxzilla and clearing your browser caches, does the box show up any sooner?

Danny:

Boxilla was updated yesterday to 3.4.1. It is also in Test mode.

I went into Firefox and cleared the Cache. Closed FF.

Reopened it and went to our site. Boxilla came up quickly after the page loaded. I though great!!

I then closed FF. Then opened FF again went to the website and boxilla did not come back up.

Ran this scenario 3 times with the same result.

So, once my FF Cache is clear it works the first time.

Does that give you any more clues as to what is happening?

I have 2 other sites besides these 2 that I maintain for different groups and I use Boxilla on them too and it seems to be working fine on those sites. They are also hosted by GoDaddy.

Bob

Hi Bob,

I notice that you have configured the box to not re-appear for 2 hours after it has been triggered (and thus shown). Are you sure that is not what’s causing the box to not re-appear for you after it has been shown? You can test this out by clearing your cookies or by setting the cookie value in your box settings to 0 to disable it.

Danny:

I have to apologize to you for taking up so much of your time with this. I figured out what I was doing wrong and corrected it. Now everything is working as it should. Cache was cleared. Set up to appear 1 second after page loaded. Set cookie exp to 1hr. I also had it set to appear everywhere. Turned that off.

Now it seems to be working.

Thanks again for your time and suggestions. This problem was caused by me not looking at my settings like I should have.

Bob