Slow backend api to frontend redirection

Hello, my issue is that I have a redirection from my server using Traccar from http://34.xxx.5.xxx:8082 to http://34.xxx.5.xxx:3000 for customization available in Traccar Web. However, when I attempt to access my server on port 3000, the page loading is slow, taking around 40 seconds to display content from http://34.xxx.5.xxx:8082. In my vite.config.ts file, I have this configuration.

export default defineConfig(() => ({
  server: {
    host: '0.0.0.0',
    port: 3000,
    proxy: {
      '/api/socket': 'ws://34.xxx.5.xxx:8082',
      '/api': 'http://34.xxx.5.xxx:8082',
    },
  },

When I enter the page on port 3000, the network console shows 516 requests, which I believe is causing the slow performance. I'm unsure how to resolve this; I need to improve the loading time.

My server have 4gb ram and 2 cores, so the performance of the VM are not the problem, i have 1.3gb free of ram and 20gb of disk free.

What requests do you see there?

The request are the same that tracar makes when you enter, but in normal port 8082, the request are 41 aproximately, but on my port 3000 are 541. All the requests that Traccar makes seem to be duplicated. It appears that they are being made first to ws://34.xxx.5.xxx:8082, and then again on my frontend at http://34.xxx.5.xxx:3000. However, Traccar itself seems to be functioning properly. The issue lies in the slow loading time when opening the page, taking approximately 40 seconds. I'm unsure what the problem could be.

Here it's a same problem
https://github.com/vitejs/vite/issues/15177

Different version though.

I solve the problem, Thank you for your time Anton. Greetings from Ecuador.

Do you want to share the solution?

The problem it's that i was running two services, so on the traccar on port 3000, i forget to make the npm run build to make the package for the web on Traccar port 8082, i make the npm run build and i got the folder with the package, i replaced on my traccar port 8082 and i just have right now one service, and service on port 3000 it's disabled right now.