How to Learn and optimize 1.1 points in IIS

IIS, an Internet Information Server that comes with Windows Server, is a common tool for setting up website servers. It is simple and troublesome, new users can use the IIS server to set up a decent Web site. However, it is not easy to configure and optimize the IIS performance so that the website access performance can reach the optimal state, here I will introduce how to optimize the IIS server step by step.

For the Server environment, take IIS6.0 of Windows Server 2003 as an example. The client environment is Mozilla Firefox 3.0 and the YSlow extension of Yahoo is installed.

YSlow is a Firebug-based plug-in released by the Yahoo developer team. It is used to analyze Web pages and rate the pages according to the rules of some high-performance websites. It is helpful for web page performance optimization and tells you that some of them affect the speed of your web pages, it also shows you how to optimize IIS based on certain rules. Our policy to optimize IIS is based on YSlow.

Optimize IIS and use Firefox with YSlow installed to open the target website. Then, click the YSlow icon and click Performance.

Among them, Performance Grade is YSlow's rating for your website, A100 points) is the highest, F is the lowest, and how to modify it is listed later, the following uses IIS 6.0 as an example to describe how to optimize website performance.

1. To optimize IIS, reduce the number of HTTP requests

This is mainly to modify the website code, reduce the number of external images, CSS, JS and other files, and manually Merge multiple CSS/JavaScript files. You do not need to set IIS.

2. Use CDN to optimize IIS

This is free for small websites. Of course, rich people can try to solve the problem of slow response speed when users access the website.

3. Optimized IIS enabling content expiration

Enabling content expiration for static files improves access performance. First, the website directory should be reasonably divided, and images, CSS, and JavaScript should be placed in a separate directory. Then, in IIS, select the directory, click Properties-HTTP header, and enable content expiration, you can select 30 days later.

In this way, the user's browser will compare the current date and end date to determine whether to display the cache page or the page requested to be updated from the server, because the image, CSS, and JS are usually less changed, therefore, it is basically read from the local cache to speed up the display.

In this way, we have completed part of the IIS optimization. Of course, we will learn more about the optimization. I hope you can continue learning.