I have a REST API made with Laravel and a WebApp (which uses the features of this API) made in Angular.JS. My WebApp is a unique registered user portal, but now I'm creating a website so that non-registered users can only check out a few things.
I decided to make a normal website because this way search engines can more easily index the site and this should help improve the site's position in Google search results, for example.
In the meantime I'm facing a big problem now. My idea was for the site to leverage the features that the API already provides (so you do not need to make new deployments). So far so good, it worked, but it was soooo slow due to HTTP Request overhead. Basically when a link is clicked on the site an HTTP Request is generated and when the server fetches the content in the API another HTTP Request is generated.
In my local development environment, simple access to a page with a list of items provided by the API already takes 2.5 seconds, making me very concerned about the performance this will have in other scenarios. In the end it seems to me that it is very advantageous to have an API for WebApps and for Apps but very bad for Sites.
My questions are : How to resolve this situation? Is this a price to pay for using an API? Is there anything I can do to avoid this overload of requests? Any plugins, packages, or network schemas?