Sd2.0-Web website performance tuning practices seems to be a plagiarized article

The class "Performance Tuning for large-scale and high-traffic Internet sites" is the last good class I attended. I thought this class was mostly about background services, in fact, I am mainly talking about client optimization. I mainly talk about 14 standards. I vaguely felt where I met these 14 standards. Then I checked google, it is true that these 14 items are not new, but they are not too concerned 《 Program Wang Zongyi, author of "Performance Tuning practices for Web websites" in the "practice web" Special Issue, explained the content in the article mainly about the expansion of the 14 standards, it seems that Wang Zongyi's Article It seems to be copied.
Tenni Theurer from Yahoo! spoke very well about the cause and effect of the Optimization on the front-end of the entire website, and the achievements of the R & D team over the past few years (this is why I think "Performance Tuning practices for Web websites" is a plagiarism). The general idea is as follows:
1. 5% of the sources that affect website performance come from the backend, while the frontend reaches 95%.
2. These research results come from continuous quantification, Performance Research, and time
14 specific guidelines:
Make fewer HTTP requests
Reduce the number of requests from the server (small images are merged into one image, and the icons are located through CSS to better utilize the browser's cache function. Javascript is merged into one file as much as possible, the style sheet must also be merged into a file)
Use a content delivery network
Try to use the Content Delivery Function and make the content as close as possible to the user through static content
Add an Expires header
Add an expiration page header to the file
Gzip Components
Use gzip to compress pages
Put CSS at the top
Put the style sheet file in the Move scripts to the bottom
Place the script file at the bottom of the page, because JavaScript will block the file behind the page during processing.
Avoid CSS expressions
Avoid Style File expiration
Make JavaScript and CSS external
Place scripts and style files externally
Reduce DNS lookups
Reduce DNS resolution time
Minify Javascript
Minimize scripts, such as obfuscation scripts
Avoid redirects
Avoid redirection
Remove duplicate scripts
Remove duplicate scripts
Configure etags
Configure etags
Make Ajax cacheable
Use Ajax Cache
Supplement:
1. The page uses XHTML and Div + CSS layout to separate the style sheet from the XHTML file so that the style file can be cached.
2. Currently, most browsers support gzip, which can compress text, static pages, style sheets, and scripts to reduce memory read time.
3. The access performance of the client can be further improved through the cache server such as squid
4. Restrict cookie application domains, response directories, and expiration time to reduce cookie requests. A 3 K cookie can increase the latency to 80 ms.
5. The page consists of 2 ~ 4 servers with different domain names provide services to increase the speed. For example, the page is provided by a, the style is provided by B, and the image is provided by C, so that the browser can download files from multiple servers at the same time.
6. Restrict Crawlers
7. Cluster processing should also be considered when the access pressure is too high
8. Optimize the database
In summary, we can see that the front-end optimization is mainly to greatly utilize the browser's cache features, so as to achieve almost local access speed, while minimizing the consumption of server performance, these front-end optimizations can be achieved in our daily work.
Additional information: http://developer.yahoo.com/performance/rules.html