I have tested Amelia in different setups and it has always resulted in slowed page load speed.
Earlier it was only limited to the fronted but now my WordPress Admin panel has slowed down as well. I deactivated all the plugins and activated them one by one.
As soon as Amelia was activated my average page load time (inside of WordPress Admin panel) went from < 3 seconds to almost 30 seconds.
That is strange, we haven't added anything that could cause this in version 2.9 and we haven't had such complaints. If you want update Amelia to 2.9 again and provide me a temporary WP-admin login for your site where this happens, so we could log in and take a look.
We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course we do not provide login data to third party. You can write credentials here just check Private Reply so nobody can see them except us.
Hi, I'm sorry to say I have this very same problem. Only after de-activating Amelia in the backend the response time is back to normal from >18 seconds. I am on WP 5.5 and Amelia 2.9
I was hoping to implement Amelia om several sites replacing Calendly. I'll just have to wait till this problem is solved. Cheers,
Please open a new Private ticket and provide us with a temporary WP-admin login for your site where this happens, so we could log in and check where the issue is coming from. Thank you!
Sorry, apparently I am not the only one having this problem and I would think it's easy for you to check this problem on one of your own test sites. I don't like support asking for login credentials unless it is a very specific site problem.
There are couple of users reporting this but we couldn't reproduce it on our testing site, this is why we ask for credentials to narrow down the issue. This is forwarded to our developers so they will check out if they can reproduce the issue and see where it is coming from. Sure, we respect your choice.
If you have any other questions or concerns feel free to open a new ticket and we will gladly help.
I have tested Amelia in different setups and it has always resulted in slowed page load speed.
Earlier it was only limited to the fronted but now my WordPress Admin panel has slowed down as well. I deactivated all the plugins and activated them one by one.
As soon as Amelia was activated my average page load time (inside of WordPress Admin panel) went from < 3 seconds to almost 30 seconds.
I have downgraded from v2.9 to v2.8
For now the Admin speed issue has been fixed but I don't know what problems will it create with the database
v2.9 was firing multiple 10-14 HTTPS requests
Hello Nishant Raj,
That is strange, we haven't added anything that could cause this in version 2.9 and we haven't had such complaints. If you want update Amelia to 2.9 again and provide me a temporary WP-admin login for your site where this happens, so we could log in and take a look.
We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course we do not provide login data to third party. You can write credentials here just check Private Reply so nobody can see them except us.
I have also had this problem having just installed Amelia for the first time. When it is active the entire backend is slow. Wordpress 5.4.
Hello Oliver,
We see you opened a separate/new ticket regarding this matter so we will get back to you there.
If you have any other questions or concerns feel free to open a new ticket and we will gladly help.
Hi, I'm sorry to say I have this very same problem. Only after de-activating Amelia in the backend the response time is back to normal from >18 seconds. I am on WP 5.5 and Amelia 2.9
I was hoping to implement Amelia om several sites replacing Calendly. I'll just have to wait till this problem is solved.
Cheers,
Charles
Hello Charles,
Please open a new Private ticket and provide us with a temporary WP-admin login for your site where this happens, so we could log in and check where the issue is coming from. Thank you!
Sorry, apparently I am not the only one having this problem and I would think it's easy for you to check this problem on one of your own test sites. I don't like support asking for login credentials unless it is a very specific site problem.
Charles
Hello Charles,
There are couple of users reporting this but we couldn't reproduce it on our testing site, this is why we ask for credentials to narrow down the issue. This is forwarded to our developers so they will check out if they can reproduce the issue and see where it is coming from. Sure, we respect your choice.
If you have any other questions or concerns feel free to open a new ticket and we will gladly help.