Image can query case script on one server

Image can query case script on one server Recommendations on optimizing website loading speed-- Technical support after website development is a task that must be fully responsible and cannot be ignored. Let's take a look at suggestions for optimizing (reducing) website loading speed. -Any image or file can be requested. If the requested object cannot be found or does not exist, the speed of the site will be significantly reduced and the load on the server will increase, resulting in a large number of false requests for non-existent objects. There are more requests like this than you think. If you find any wrong requests, just remove unnecessary code from or file or adjust it. It is very important to control the page loading speed and track calls to non-existent resources! It may slow down the loading speed of particularly style and general pages. The biggest difficulty lies in loading the styles sequentially (one after another) instead of using the possibility of parallel (simultaneous) loading of styles. This adds additional steps to the website loading process.
Site pages used-files will increase time and slow down page loading speed (connect→download, connect→download, etc.). Sometimes it is inevitable to use multiple style files (for example, when it is easier and more convenient to use multiple files for site design), but if possible, it is necessary to combine them into one file.
Forget to delete unnecessary links to old files in the code of the page. Or, to connect to external resources, you can use this function, but it should be noted that when using it to execute it through code, the browser will perform unreasonable load-read and write operations, which will have a negative effect on the speed of loading website pages influences.
-Usually used by including a large number of external scripts. As other measures, you can use the function of including small scripts and delayed loading scripts in the body of the page. Berne swellnet Each site uses a large number of various images. To display each of them, the browser sends a request, in response to which the server has the corresponding image. And, therefore, by combining multiple images into one-(-), the page loading speed can be reduced. Now, your browser will no longer load a large number of images, but one! This is the beauty of elves! Of course, this is more about combining several small images used in the design elements of the page (menu background, emoji, corners, icons, etc.). In this case, to use an element separate from, you will need to call this, then specify the size and position the desired element relative to the total size of. As you might guess, lazy loading of external scripts will make site pages load much faster than sequentially loading line-by-line source code. Some people may say that putting the calling script at the end of the page is enough and the matter will be resolved. But this is not the case. Only the solutions outlined below allow external scripts to be loaded after the page is fully loaded and will not issue a warning in Webmaster Tools. You need to wait until the page is fully loaded and then execute the script.
Simply because they have an important impact on page loading speed, which in turn is an important factor in search engine rankings. You can enable compression by adding some code to the. File located in the site root folder on the host site. Using one of the above methods, you can check the compression rate of your website pages. To do this, click on the link /-and enter the site address in the field. Agree, this is quite a serious reduction in the amount of data transferred. To display a web page, the browser must continuously download certain data from the server. First, the files and other data (files, images, scripts) are sent to the browser. If-is not enabled, the page may take a long time to load: a different network connection will be opened for each file request. If the keep-alive feature is enabled, some kind of activity is created between the browser and the server and functions in the same connection. However, in some cases, your site may not use it, or it may be disabled in your hosting parameters. To enable keep-alive, you need to add headers to requests that use the same file. To avoid loading unnecessary files with small fragments of style, you need to embed these fragments directly into the code of the website page. Loading an embedded file is much faster than loading two files (+ ). On the bright side, the browser does not have to request and download many files. On the other hand-this is undoubtedly a negative sign-the styles placed in the file are not cached. As we all know, caching can also help browsers avoid unnecessary reading operations on static information (such as styles). Each time you move between pages on your site, you load the styles placed in the code of the site's pages again and again. It doesn't matter whether the website style is small. However, if there are many, then of course you need to separate the style from the original code. This is very useful when creating loading pages, login pages, etc. of a site, when you need to display them quickly. When the browser displays any page of the website, it will load code, styles, scripts, images, logos, and other resources. When the visitor moves from one page to another, the browser must reload the information he needs. But in most cases, there is no need to do this: a considerable amount of duplicate data has been preloaded from the first few pages of the site. And in order to not have to download the same information again and again (information that the browser already has), a cache must be used.
Caching eliminates the need to reload previously loaded information, thus making your website faster. In order to enable caching, you need to add the following code to the file we are already familiar with.

Set the cache time of the selected data type. You can adjust these values ​​according to your preferences.

Alternate code to enable caching via file. It does not matter whether the style is used inline in the code or as a separate include file. By reducing the code in this way, you can save a lot of code and can significantly increase the speed at which your website loads pages! Every day, the pages of our website are becoming more and more advanced and fully functional, but as a result, their speed slows down. Add calls to other servers, statistical tools, fonts, social buttons, etc. In the process of loading the webpage, the browser will contact other hosts to obtain the necessary information (execute other queries). Due to the auxiliary call to external resources, even very fast website pages (which only take a fraction of a second to load) will become very slow.
One of the most vivid examples of such requests is the buttons of social networks (, +, etc.): when they are formed on your website, calls to external websites occur. Another example is the use of (connected) fonts. Two queries are required for each font. When connecting to external resources, it is important to strike a balance between using them and the speed of website loading. It should be understood that they also affect the performance and speed of the site. The most common redirection is used when redirecting a site from to a site without (and vice versa) to avoid re-indexing mirror sites.
Make multiple redirects to reach the required resources. It is important to choose the correct loading order for the styles and scripts in the code of the website pages. First, you need to specify the internal style declaration, then include the external style file, and then the script. Tested and concluded that this is the necessary order when declaring styles and scripts.
The resources (styles, scripts, images, etc.) specified in the code are called sequentially. When the browser starts loading the script, it will stop loading anything else until the script is completely read (loaded). It claims that a typical web page spends 81% to 91% of its time waiting to load from the web. Of course, images of any size you specify can be displayed. However, it should be understood that if a large image is reduced to a thumbnail, the browser will take some time to load the complete image. This is all extra time. In the opposite case (forcing a small image to be enlarged to a large size), the quality is significantly reduced.
Specify the following parameters. If the information on the page loads slowly, the browser will not form the page, but two or more times (depending on the number of images on the page): First, the browser will not consider the size of the image Under the circumstances, read and place the text, then load the image, enter the text and perform different movements. If you tell the browser the size of the image in advance, it will already know the space allocated for the image, and there is no need to redraw the web page multiple times. By using the browser to indicate the required size, it is forced to be compressed onto the page. The original image (filled in red), in addition to its huge size, occupies 5.75 (6026,240 bytes) on the host. Now, the optimized image (filled in green) with a size of 251×168 pixels is only 11.5 (11,805 bytes). Reduction of 558 (!
Using these simple rules will make your website load faster!

At the same time, it is a very powerful tool that can clarify many aspects and set the server and site mode. Redirection, compression, caching, setting permissions, etc.-all of which can be controlled through this file. It should be noted that not all hosting companies can fully control the operation of the server through this file. However, even if you make a small mistake while editing a file, it may lead to undesirable consequences, so it is very important to be as responsible as possible during the process of creating and changing.
In any case, it is recommended to back up this file before modifying it!
Use a regular text editor to edit this file. How to Read Someone Else's Temp Table - then Watch Brent Tune Queries