Web project engineering and performance optimization method

Abstract

The invention discloses a web project engineering and performance optimization method. According to the engineering optimization method proposed for a single page application (SPA), optimizing single-WebView page request resources is adopted as an objective; a project is created; a page WebView routing file in the project is written; a file project is divided into a component template file and a page template file according to componentization requirements and page planning; a compiler obtains a client request by reading routing settings, and processes and integrates JS and CSS codes needed inthe component template and the page template in advance, so as to realize a pre-compilation process; and original (src) tags and (script) tags in the file are substituted, and connection numbers anddata loading can be optimized.

Description

technical field [0001] The invention relates to a Web front-end optimization method, in particular to a Web project engineering and performance optimization method. Background technique [0002] With the increase of demand, the current web projects are becoming more complex, large-scale, and customizable. Especially with the emergence of single page applications (SPA: Single Page Application), the complexity of web projects has doubled. [0003] However, the existing project organization and optimization methods are still relatively primitive. The general Web project does not integrate and optimize project files. The only optimization methods are some processing such as compression and regularization, and the performance is still good in relatively simple projects. , but in modern large-scale projects, due to the development of different teams and the requirements of componentization, the files and references in the project are very complicated. Large-scale projects, especia...

AI Technical Summary

Problems solved by technology

There are two optimization methods for existing SPA Web projects. The first one is to optimize the entire project as a whole, and integrate all styles and scripts in the project into as few files as possible. The advantage is that there are fewer loading requests, and the disadvantage is that if the project If the complexity is high, the volume of a single file will be too large, which will cause slow loading, and the browser's css and js code parsers are executed sequentially, and files that are too large may be slow to parse or even blank, and the functional style is temporarily missing question

The second method is to split and modularize, but overly fragmented scripts and style files will cause a large number of fragmented requests. On the servers of some cloud service providers, the number of concurrently requested connections is limited. Fragmentary requests for style elements Request links that occupy data will also cause page freezes and slow responses

[0006] In addition, there are some traditional on-demand loading optimization methods for single html files. Due to different optimization dimensions and ideas, these optimization methods are not completely suitable for single page application (SPA) projects, and can only do some rough optimization. Can't really play a role in re-integrating resources

Images