Slow Speed on backend and front end of Radicle Site, Diagnosing...

I am trying to determine why my WP site running a Radicle theme on cloudways is running so slowly. Initially I was on 1gb of memory and it didn’t seem to bad this was just QA so I thought we could get away with that but eventually things seemed to slow down with maybe 2-3 users on it. I upped the memory to 2gb, and still not much of an improvement.

I installed Laps GitHub - Rarst/laps: Light WordPress profiler.

And here is a particularly long loading time





I really just need a point in the right direction to where I should start optimizing or figuring out what is causing such slow loading times.

I am happy to provide much more information, but since so many files are responding slow here I don’t know where to start. Sometimes the response is 1-3 seconds or on average it is that but I’d still like to get that down.

In production I can up memory but I think there is something wrong that it is so slow on 2gb with barely anyone using it since it has htaccess password across the whole site, so there shouldn’t be any other traffic.

What theme version are you using? You did provision the VPS on Cloudways with Trellis? What type of VPS - Ubuntu 24.0.4? Seems that Cloudways do their own VPS setups as they are managed so not sure if that is an issue but could be. Also see Trellis on Cloudways without Root access

So I am not using Trellis I had used the default wordpress install on cloudways. It runs Debian 11 bullseye PHP 8.1.30.

I just installed the basic wordpress cloudways install deleted its folders to keep its config and deployed my site via envoyer using this setup.

Maybe a dumb question but how do I know what version of the theme I am on, if it’s not a package itself I just downloaded the zip, I don’t know where the original zip is, so where is the version tracked. Sorry if it’s super obvious I am tired just finished moving houses :wink:

Sage theme style.css should show version installed . But I assume that is one of the latest versions then. And if theme was composer installed the composer lock file will show it too of course. You should also have access to the Radicle repository https://github.com/roots/radicle/ .

When you use Bedrock, Sage you need to run composer install in two locations, in Bedrock and theme. You would also need to run yarn and yarn build in the theme directory. See documentation https://roots.io/sage/docs/installation/ , https://roots.io/sage/docs/compiling-assets/ and so on.

I understand you used Laravel’s Envoyer for Cloudways https://www.cloudways.com/blog/php-laravel-envoyer-deployment/ . Not familiar with that tool. Only used Forge.

Checking logs for PHP FPM, Nginx or Apache would be useful too.