I got the following email from siteground a few weeks ago not sure if this is relevant to you also
This could also make loading faster- when your site loads it loads fast its just that starting part which is slow- I wonder if this is adding to the time it takes to load
_______________________
We
have identified that some of your domains that are not registered with
SiteGround may still be using legacy name servers that need to be
updated as the support for your current name servers will be gradually
discontinued starting from next month. In order to avoid any downtime,
please update your name servers as soon as possible. |
|
|
Why is the update needed?
|
Last year we introduced a new central DNS service,
which has a great impact on boosting our clients website loading speed.
Since the activation of this service, the recommended name servers for
all our customers are ns1.siteground.net and ns2.siteground.net. |
The
name servers your domain name is currently using are based on the
specific name of your host server, which is a legacy setup from the time
before the central DNS. These legacy name servers will be gradually
discontinued and we recommend that you update your name servers by May
15, 2022 as otherwise you may start experiencing service interruptions
when the old DNS stops working. |
| If you need assistance with updating your DNS settings, you may refer to our Help Center > Domain > Domain pointing.
_______________________
still working on the staging site but check if you have the nameservers correct |
I used to use gogeek- it should be strong enough to support eventon- will work on it right now
I’m on GoGeek
I’ve set up staging. you can use credentials provided on https://staging2.northernriversnow.com.au/wp-admin/
I’ve added the live now shortcode on the homepage
what siteground hosting package do you have (I’m with siteground as well)
siteground offers staging sites so perhaps use that feature and we can go to town on the staging site to sort things out if the entire site is fully live
Eleven hours later and I receive notification from my web host (Siteground) that there had been a huge increase in CPU seconds.
So I’ve had no choice but to remove the element from my homepage. In the absence of it not being on site, here is a screenshot
https://www.dropbox.com/s/r30nn205opd2m5g/Screen%20Shot%202022-05-22%20at%2011.24.41%20am.png?dl=0
I really need a resolution on this.
I will endeavour to be around to reply promptly to the ticket as I can imagine you would want to see it on site and run any appropriate tests. So I will re-enable when you reply
I have updated to 2.0.4 locally. Tried it and the bug is still present.

Hello !
Sure I tried to share the event before writing you… Even if the link seems fine :
https://www.google.com/calendar/event?action=TEMPLATE&text=Camp+P%C3%A9niel&dates=20220725/20220806&ctz=Europe/Paris&details=Camp+P%C3%A9niel&location=Centre+de+Vacances+et+de+Loisirs+P%C3%A9niel185+route+de+Chalias%2C+07560+Montpezat-sous-Bauzon
With dates : beginning from 20220725 and finishing on 20220806, when clicking the link on the Google interface it says starting from July 25, 2022 and finishing on August 05, 2022
So there is still the one day shift !!
Thanks!
Best regards
In addition to my last you will see “no events at the moment” text is grey. It’s supposed to be white as per screenshot
https://capture.dropbox.com/2u0J5ixcwjCKKWT4
But please, my previous message is the priority here
I added the “live now” shortcode to the homepage. It’s gone from ~3 seconds to load to ~20 seconds to start loading. Is this usual?
Shortcode in use is [add_eventon_now show_et_ft_img=”no” etc_override=”yes” ux_val=”4″] so no images and opening the single event page
I have no choice but to leave it up until you look at it (and my traffic will plummet), so please look at this as soon as you can
FYI, I had to renew my Envato support to ask this question so I really do hope you can help answer as to why it is so slow and whether it can be fixed, otherwise I will need to find a better plugin.
Thanks
Thanks for your help. Increasing the system memory solved the issue.