Enlightenment web standards: front-end performance optimization
Front-end performance optimization is completely a technical topic, but it has a great impact on the user experience of the project. If you have to wait three to five seconds to open your website or wait until the browser prompts that it cannot connect, then where does the website get the traffic and where does the brand come from? Influence and user loyalty, just make money.
3s is used to judge the limit of a user's ability to tolerate the speed of your website. If it exceeds 3s, the user has developed a negative psychology towards the website.
What is the relationship between front-end performance optimization and web standards? Next, the first article is about understanding web standards - unifying ideas and following standards . This is a compensation for your compliance with web standards or a recognition of standards.
Quote:
Front-end performance optimization Students who know about Yahoo performance optimization should be familiar with it. Just install a YSlow score and compare it with the optimization. But have you ever thought about why you need to do this to improve speed? Are these related to Web standards in some way? Correlation or causation?
I divided these items into three categories, server-side computing optimization, transmission optimization, and client-side computing optimization:
The first category, server-side optimization
The server side is the execution of your website's dynamic language (asp, php), database query, storage, etc. In general, it is the input/output operation. These have nothing to do with the front end, but they affect the front end. There is no such thing in YSlow. The devil knows how good your website's server performance is. If you can't tell, just optimize the server performance and database performance yourself, and buy more server expansion.
yslow has a method to refresh the Buffer as early as possible (Flush the Buffer Early), which seems to be transmitted before the html is completed.
Improve the DNS resolution speed of domain names. Reduce the number of DNS resolutions. This is difficult to categorize, so I’ll put it here for now.
Backward page engineer system, page code for artists, page code that can only be browsed by IE, page code that can be directly exported with graphics tools without writing code, page code that consumes a lot of traffic, and page code that is as slow as a snail , programmers get dizzy when they see the page code, and they have to be moved every time it is revised. The page code that is generated repeatedly is a kind of page code that makes page engineers and migrant workers the same.
Of course we must revolutionize it, replace it, and create a new page engineer system and page quality. The page code completed by independent page engineers, the page code that spans platforms, can be accessed and browsed by any device that can parse the page, and the handwritten page code , neat, well-structured, page code with the lowest traffic consumption, page code that programmers like, page code with super-fast access speed, revised and reusable page code, so that page engineers can raise their heads and proudly call themselves engineers , what is written is also the page code of computer code.
Front-end optimization just provides an opportunity for Web standards to be tested. Use "Practice is the only criterion for testing truth" to judge whether standardization is good or not.