Connecting to a remote database (depending how far) is quite hard hitting on performance.
But you've obviously tested to make sure it wasn't that...right?
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Connecting to a remote database (depending how far) is quite hard hitting on performance.
But you've obviously tested to make sure it wasn't that...right?
Adise, did you test this setup on actual server or maybe try using sqlite just to eliminate MySQL out of testing.
Also, try using different browser. It could be that Chrome has a security flag on preventing you from connecting to remote database.
@alenabdula That would have nothing to do with Chrome. The remote database would be handled server-side in php.
Think alenabdula is high again :P
How can i resolve this ?
Change this:
remote mySql database
Seriously though.. it looks like you've got debugbar installed, that should show mysql query times. Almost certainly network latency is killing your performance with the DB being remote.
Referring to all the chrome errors in the console. I've had issues with timeouts with chrome when testing stuff locally I was just trying to help him eliminate possible issues. Hence, my suggestion to test on actual server. And I wish I was high.
Generally speaking a remote data base is more common these days but your network has to be cfg for it. Many cloud based apps utilizes a central data base and a local. So you have a few extra layers plus a home or office (even worse) network you will have issues with performance.
@adiss maybe it is because you use variable names in Bosnian and it takes too much time for interpreter to understands what to hell you wanted to say.
I am kidding. You should not use www as 'domain name' for some reason resolving took so much time it say net::ERROR_NAME_NOT_RESOLVED.
Ah now I see that was about some ads after you loaded 'kategorije' when this happen the only way is to do debugging and benchmark time as app goes and see where you burn so much time.
I also have a similar problem like this, although I am only using a local homestead installation:

Even 20 database queries only take up to 5ms in total. For my service providers I only used Debugbar, Sentinel, Bugsnag and HashIds - so nothing too mayor. Even when I had Bugsnag turned off the boot-time was almost the same; very slow.
Running artisan optimize and route:cache did not help with the loading time at all Any ideas?
@addis were you able to solve this? I have the same problem... Please share if you did solve it.
I am use win7 +homestead ,and change my homestead.yaml file like this ,
folders:
- map: E:/out-going/vagrant
to: /home/vagrant/Code
type: nfs
use type:nfs , this help me a lot.
Please or to participate in this conversation.
