When it comes to improving the performance of an application using Peqi, there are several factors to consider. One of the main issues that can hinder optimization efforts is related to how the application's static content is handled. This article explores one of the most common obstacles faced by Peqi users and provides a solution to maximize the benefits of this powerful tool.
Separation of static content
One of the practices that can negatively impact the performance of your application on Peqi is separating static content, such as CSS files, JavaScript, and images, on a different domain. For example, suppose you have registered the main domain, example.com, on Peqi, but the static content is hosted on static.example.com. In this scenario, all requests for static content will be treated as external requests. Peqi performs optimization and caching only for the registered main domain, that is, example.com. As a result, the application will not fully leverage Peqi's optimization resources.
Recommended solution
To overcome this issue, we suggest you register the subdomain hosting static files separately on Peqi. Using the above example, you should register the domain static.example.com separately on Peqi. By doing this, Peqi can optimize and cache requests for static content, thus maximizing the overall performance of your application.
By following this best practice and ensuring that all content, including static content, is optimized by Peqi, you will be on the right track to significantly improve your web application's performance.