Hello Saurabh,

Thank you for reaching out to us.
Slow load can be caused by a lot of things - the number of appointments you have, the number of customers, the number of employees, etc. 
Other than Amelia, it could be caused by the amount of other data you have on the page. 
Are you on a dedicated, or on a shared hosting? Can you increase the php_memory_limit on your site? 
If you're not sure how to do that, you can reach out to your hosting provider. 
Please check out our demo sites (https://wpamelia.com/demos/) and see how the plugin should behave on a site with dedicated hosting and good server performance.

Hello Saurabh,

Thank you for the details. Please provide the following so we can investigate further:

1. The error message from the browser console when you try to access the Amelia dashboard.

2. Admin access so we can check the configuration.

3. Try reinstalling the Amelia plugin and let us know if the issue persists.

Looking forward to your response.

Hello Saurabh,

Thank you for the update on this.

The "MySQL server has gone away" error usually occurs when a MySQL query takes too long to execute, or the server disconnects unexpectedly due to issues like timeouts, memory limits, or large query executions. Here are some steps to troubleshoot and resolve this issue:

In your my.cnf or my.ini file (usually located in the MySQL server’s root directory), increase the values of wait_timeout and interactive_timeout to prevent the server from closing idle connections too early.

After changing these values, restart your MySQL server.

If you're running large queries or inserting large blobs, the packet size might be exceeding the limit. You can increase the max_allowed_packet value:

Again, restart MySQL after making the change.

The MySQL error log might contain more details about why the connection is lost. This can help identify whether the issue is caused by a specific query or an external factor (e.g., resource limitations).

If the server is under heavy load or has low resources, it may close connections. Monitor the server's CPU, memory, and disk usage to ensure there are no resource bottlenecks.

In some cases, simply restarting the MySQL server can resolve the issue if it's caused by temporary connection problems or server overload.

If these steps do not resolve the issue, there might be additional configuration issues or server-specific problems that need to be addressed. Let me know if you need further assistance!