Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

khanareeb's avatar

Laravel Website Suddenly Slow After Server Migration – Possible PPA Launchpad Issue with PHP 7.4

Hi Everyone,

I just wanted to confirm something regarding the recent PPA Launchpad issue. My website is built on Laravel 8.83.27 and currently running on PHP 7.4.33.

Before May 1st, I migrated the server from AWS to another VPS cloud provider with better RAM and CPU resources. I initially deployed the website on a temporary domain, and everything was performing well until May 1st. However, after pointing the main domain to the new server, I started noticing that the website response has become significantly slower. I have already cleared all caches and ensured proper permissions for the storage and cache directories, but the issue still persists.

What makes this more confusing is:

  • I cloned the entire project locally using the same PHP version, and the performance is still slow.
  • I also tried accessing the website on the old hosting server via its public IP, and it is now responding slowly there as well.

Given this behavior, I’m wondering if this could be related to the PPA Launchpad issue. Am I thinking in the right direction?

I was also considering upgrading the PHP version, but that would likely require upgrading Laravel as well, since Laravel 8 does not fully support PHP 8.1+. So I haven’t been able to test that path yet. If anyone else is experiencing something similar or has any insights, I’d really appreciate your input.

P.S. There has been no new development or code changes in the past two months. and the site was perfectly working before May 1st on a previous and new hosting..

0 likes
4 replies
martinbean's avatar

Given this behavior, I’m wondering if this could be related to the PPA Launchpad issue. Am I thinking in the right direction?

@khanareeb You need to profile requests instead of just guessing.

Profile a request and see where the most time is being spent. My guess is, if you have moved hosting, that you’re probably pointing to a remote database that’s connecting over the network instead of via a socket on the same machine, thus introducing latency. But again, just a guess. You need to profile to confirm the actual cause.

khanareeb's avatar

Apologies but what does that means "You need to profile to confirm the actual cause" ? How do i do that ?

imrandevbd's avatar

Profiling basically means "measuring" your code while it runs to see exactly which part is taking the most time. It stops the guessing game.

Since you're seeing this locally too, that’s actually a win it means you can fix it without touching the production server.

The quickest way to do this in Laravel is to install Laravel Debugbar. Run this in your terminal:

composer require barryvdh/laravel-debugbar --dev

Once installed, refresh your slow page. A bar will appear at the bottom. Check these two tabs:

Timeline: This shows you the "execution" flow. If you see a massive gap/block, that’s your bottleneck.

Queries: This shows every database call. If one query is taking 2 seconds or you have 500 duplicate queries (N+1 issue), you’ll see it here instantly.

JussiMannisto's avatar

Given this behavior, I’m wondering if this could be related to the PPA Launchpad issue. Am I thinking in the right direction?

No. That's only relevant when you're installing packages on Linux. It has no effect on your app after that.

Please or to participate in this conversation.