Dashboard Slow but Site Fast

  • carinvazef

    (@carinvazef)


    2 months, 3 weeks ago

    Hi,

    Over the past couple of days, we’ve been optimizing our client’s site to improve performance. At one point, nothing was loading, but we’ve managed to get the frontend operational. Overall, it functions reasonably well.

    However, the dashboard loads extremely slowly, and sometimes it fails to load altogether. We reached out to the hosting provider (OVH), but they haven’t been very helpful. I want to set up a staging site to troubleshoot without risking the live site. Unfortunately, due to the slow load times, the clone process for the staging site fails. My plan is to review all the plugins one by one to identify any that might be causing issues, but I’d prefer not to do this directly on the live site in case something goes wrong.

    Here are some of the errors I found in the host logs:

    • The web server is looking for an index file but cannot determine which file to serve. I am thinking index.php or index.html is missing or inaccessible and there is .htaccess misconfiguration that is preventing the correct file from being served. Could this be a file permission issue blocking access?
    • A script timed out before returning headers for index.php indicating that a PHP script (likely WordPress) is taking too long to execute and is getting killed before it can return a response. This was the first thing I checked with no success. I found slow database queries with a high server load. I am guessing it is due to an unoptimized or conflicting WordPress plugin. I have gone through each plugin and nada.
    • An error that happened during FastCGI processing, fallback to CGI which suggests a problem with FastCGI, possibly due to high server load PHP execution errors; memory limits being exceeded./Comm with server aborted due to idle timeout (160 sec). The server is waiting too long for a response from PHP, which is then killed due to timeout due to heavy queries in the database, poorly optimized plugins and/or Insufficient server resources
    • Lastly, end of script output before headers where index.php PHP script is crashing before it can send a proper response. Is there a Fatal PHP error, corrupt WordPress installation, theme or plugin issue? This could explain the issue with the dashboard and site.

    Here is the error I receive when trying to clone the site for staging:

    Warning: require(/home/tothvioldj/www/sutherland/wp-includes/version.php): Failed to open stream: No such file or directory in /home/tothvioldj/www/sutherland/wp-settings.php on line 33

    Fatal error: Uncaught Error: Failed opening required ‘/home/tothvioldj/www/sutherland/wp-includes/version.php’ (include_path=’.:/usr/local/php8.4/lib/php’) in /home/tothvioldj/www/sutherland/wp-settings.php:33 Stack trace: #0 /home/tothvioldj/www/sutherland/wp-config.php(100): require_once() #1 /home/tothvioldj/www/sutherland/wp-load.php(50): require_once(‘/home/tothviold…’) #2 /home/tothvioldj/www/sutherland/wp-blog-header.php(13): require_once(‘/home/tothviold…’) #3 /home/tothvioldj/www/sutherland/index.php(17): require(‘/home/tothviold…’) #4 {main} thrown in /home/tothvioldj/www/sutherland/wp-settings.php on line 33

    Any help is greatly appreciated.

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • threadi

    (@threadi)

    2 months, 3 weeks ago

    How are you trying to set up the staging? An option in the hosting, manually or with the WP Staging plugin?

    You can also download a backup of the site and set up a test system for it locally. You can then use tools such as XAMPP, MAMP, localwp etc. to get it running on your site.

    I would also ask what changes have been made to the project recently. For example, have plugin updates been installed? That could be a reason. You can find out the last updated plugins by looking at the modification times of their directory in /wp-content/plugins/ via FTP.

    Thread Starter carinvazef

    (@carinvazef)

    2 months, 3 weeks ago

    @threadi, thank you for your reply!

    I am trying to set up staging with WP Staging Pro. I will test locally then. Thank you for that suggestion. I did receive these errors on the dashboard. Are they related to WP Staging?

    ce\PayPalCommerce\WcGateway\Settings\SettingsListener::__construct(): Implicitly marking parameter $logger as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Settings/SettingsListener.php on line 197

    Deprecated: WPStaging\Vendor\GuzzleHttp\HandlerStack::create(): Implicitly marking parameter $handler as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/HandlerStack.php on line 37

    Deprecated: WPStaging\Vendor\GuzzleHttp\HandlerStack::__construct(): Implicitly marking parameter $handler as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/HandlerStack.php on line 49

    Deprecated: WPStaging\Vendor\GuzzleHttp\Handler\StreamHandler::invokeStats(): Implicitly marking parameter $response as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/Handler/StreamHandler.php on line 59

    Deprecated: WPStaging\Vendor\GuzzleHttp\Middleware::tap(): Implicitly marking parameter $before as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/Middleware.php on line 103

    Deprecated: WPStaging\Vendor\GuzzleHttp\Middleware::tap(): Implicitly marking parameter $after as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/Middleware.php on line 103

    Deprecated: WPStaging\Vendor\GuzzleHttp\Middleware::retry(): Implicitly marking parameter $delay as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/Middleware.php on line 144

    ooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\DotNotation::transform(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/DotNotation.php on line 27

    Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\DotNotation::validate(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/DotNotation.php on line 72

    Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\TransformerInterface::transform(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/TransformerInterface.php on line 24

    Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\TransformerInterface::validate(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/TransformerInterface.php on line 33

    Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\ArrayColumn::transform(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/ArrayColumn.php on line 26

    Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\ArrayColumn::validate(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/ArrayColumn.php on line 41

    Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\ArrayKeys::transform(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/ArrayKeys.php on line 23

    Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\ArrayKeys::validate(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/ArrayKeys.php on line 38

    I updated the hosting package, which definitely helped speed things up, I also solved some issues with several plugins that weren’t updating and I disabled some others that weren’t really doing much to the website. I have cleared up the database tables and have cached left and right. I want to believe it has something to do with the hosting provider. They did report an issue with various clusters one of which was ours.

    Speaking of, would you recommend disabling plugins through via FTP? I was thinking I could disable one by one and see how the dashboard reacts.

    Thanks again for all your help!

    threadi

    (@threadi)

    2 months, 3 weeks ago

    The error messages mostly refer to the commercial version of WP Staging that you are using. Since we cannot support commercial products here in the forum, I would recommend that you contact their support for clarification: https://wp-staging.com/your-account/

    To test the effect of plugins, you can deactivate them via FTP. I would recommend that you create a backup of the project before doing this.

    This plugin can also be helpful in the analysis: https://wordpress.org/plugins/health-check/ – there you can deactivate all plugins in your session and test the effect.

    Thread Starter carinvazef

    (@carinvazef)

    2 months, 3 weeks ago

    @threadi, I contacted them, but they are slow. I will keep trying to troubleshoot. Thank you for all your help.

    Thread Starter carinvazef

    (@carinvazef)

    2 months, 3 weeks ago

    @threadi,

    I was able to work on the site locally and noticed that the WooCommerce plugins significantly slow down the dashboard—particularly Bookings/Appointments, Gift Cards, PayPal Payments, Google Reviews, and Smash Balloon Instagram. After deactivating them locally, the dashboard performance improved.

    However, when I deactivated them one by one on the Live site, the lag persisted. This suggests there might be additional factors affecting performance. Do you have any insights or recommendations on further troubleshooting?

    threadi

    (@threadi)

    2 months, 3 weeks ago

    Check Tools > Site Health to see what recommendations WordPress generally provides.

    If a caching plugin is used, not only deactivate it but also check the wp-config.php and .htaccess files to see if there are any remnants of it left. Possibly also in wp-content/advanced-cache.php or wp-content/object-cache.php.

    Deactivate all plugins and then activate them one by one, possibly starting with WooCommerce as many other plugins in the project seem to depend on it.

    Thread Starter carinvazef

    (@carinvazef)

    2 months, 3 weeks ago

    @threadi, hi again! I have not been able to identify what exactly is going on. I performed all these steps and nothing. The website is running after I enable WP_DEBUG. However, the dashboard is still struggling to load.

    I am hoping to the hosting provider will have someone onboard who can assist me because I am not sure what else to do and my client is getting anxious.

    Thread Starter carinvazef

    (@carinvazef)

    2 months, 3 weeks ago

    @threadi , the dashboard is now loading. At the Plugins > Add Plugin page, I received the following message:

    Warning: plugins_api(): An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /home/tothvioldj/www/wp-includes/functions.php on line 6114

    Thread Starter carinvazef

    (@carinvazef)

    2 months, 3 weeks ago

    Deprecated: ElementorProDeps\DI\create(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/functions.php on line 32

    Deprecated: ElementorProDeps\DI\autowire(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/functions.php on line 44

    Deprecated: ElementorProDeps\DI\ContainerBuilder::writeProxiesToFile(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/ContainerBuilder.php on line 231

    Deprecated: ElementorProDeps\DI\Definition\Source\ReflectionBasedAutowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/ReflectionBasedAutowiring.php on line 17

    Deprecated: ElementorProDeps\DI\Definition\Source\Autowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/Autowiring.php on line 21

    Deprecated: ElementorProDeps\DI\Definition\Source\DefinitionFile::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionFile.php on line 25

    Deprecated: ElementorProDeps\DI\Definition\Source\DefinitionArray::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionArray.php on line 33

    Deprecated: ElementorProDeps\DI\Definition\Source\DefinitionNormalizer::normalizeRootDefinition(): Implicitly marking parameter $wildcardsReplacements as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionNormalizer.php on line 42

    Deprecated: ElementorProDeps\DI\Proxy\ProxyFactory::__construct(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Proxy/ProxyFactory.php on line 38

    Deprecated: ElementorProDeps\DI\Container::__construct(): Implicitly marking parameter $definitionSource as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Container.php on line 87

    Deprecated: ElementorProDeps\DI\Container::__construct(): Implicitly marking parameter $proxyFactory as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Container.php on line 87

    Deprecated: ElementorProDeps\DI\Container::__construct(): Implicitly marking parameter $wrapperContainer as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Container.php on line 87

    Deprecated: ElementorProDeps\DI\Definition\ObjectDefinition::__construct(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 62

    Deprecated: ElementorProDeps\DI\Definition\ObjectDefinition::setClassName(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 75

    Deprecated: ElementorProDeps\DI\Definition\ObjectDefinition::setLazy(): Implicitly marking parameter $lazy as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 158

    Deprecated: ElementorProDeps\DI\Definition\Resolver\ObjectCreator::setPrivatePropertyValue(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ObjectCreator.php on line 158

    Deprecated: ElementorProDeps\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ParameterResolver.php on line 34

    Deprecated: ElementorProDeps\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $method as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ParameterResolver.php on line 34
    Thread Starter carinvazef

    (@carinvazef)

    2 months, 3 weeks ago

    The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.

    The REST API did not process the context query parameter correctly.

    threadi

    (@threadi)

    2 months, 3 weeks ago

    Please contact your server administrator.

    Have you already spoken to him? It is the support of your hoster. Because apparently WordPress can’t “phone” outside. This seems to be blocked by the hoster.

    The deprecated messages are only hints, not errors. They refer to the commercial Elementor Pro plugin you are using. If you have any questions, please contact their support: https://elementor.com/support/

Viewing 11 replies - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.