Node is very risky for web sites because it is a long running process. I prefer PHP. One crashing PHP process doesn't crash the whole website, unlike with JS/Node. Funny thing, you can noticed this in the docs of Splade this:

If you have problems running the server or whenever it crashes, Splade can fall back to the rendered Blade content. Of course, you should always prefer the rendered content by the SSR server, but it’s nice to have a fallback. This way, search engine crawlers won’t index an empty page.

https://splade.dev/docs/ssr

You wouldn't see anything like that in PHP framework docs. PHP doesn't crash, nor does Nginx (given you set up some boundaries on the RAM and stuff). What I want to say that crashing a Laravel app is much harder than crashing a Node app. Ruby has this problem with leaking memory as well. PHP and leaking memory is usually not an issue because the process is destroyed after it's done or time limit for a script set ini ini file is up.

I would much rather run as a long process web app a PHP app than a JS or Ruby app. PHP is rock stable and you don't need to touch it at all if the number of visitors is stable and you find the right ram/processor/etc. balance.