Extra plugins or counters
Posted: Sun Feb 02, 2025 6:57 am
Often, the site page code may contain links to plugins that the resource does not use. For example, the slider plugin was replaced, but the old version was forgotten to be deleted. Various counter codes may also remain, the statistics for which are not tracked by the webmaster. All unnecessary garbage should be removed from the page code.
If possible, you should optimize the usev of manufacturing email list auxiliary scripts. For example, if sliders are installed on several pages of the site, it is better if the same plugin is used for them.
Read also!
"Website Speed Test: 14 Best Tools"
Read more
Step 7. Using CDN
CDN (Content Delivery Network) is a network of multiple servers distributed across the country and the world. Each such server duplicates the information received from the main hosting of the resource (content duplication is performed at the first request of the visitor). The received data will be stored for some time.
For example, a user from Vladivostok, when loading data from a CDN, will receive information not from the main server, which may be located in St. Petersburg, but from the nearest one storing the required content (it may also be located in Vladivostok). Accordingly, a request along the Vladivostok-Vladivostok route will work faster than Vladivostok-St. Petersburg. The difference will be calculated in milliseconds, but when multiplied by the number of files, this can significantly reduce the page loading time.
Let's consider two options for using CDN:
Loading used scripts . These can be popular jQuery plugins, Bootstrap, WebFonts fonts, etc. For example, you can instruct the browser to load scripts not from the main server, but from Google, Bootstrap, and other CDN servers.
Loading images, pictures and scripts from your CDN . The most powerful Internet resources (Ozon, Avito, etc.) set up their own CDN on their servers or CDN network servers (for example, Google Cloud or Stack Path). The functionality of the most popular CMS platforms already includes CDN support. Thus, Bitrix uses the free plugin "Site Acceleration (CDN)".
Step 8. Reducing the number of http requests
To prevent the browser from sending http requests to the server so often, you should reduce the number of files that it may need to download. For example, you can combine several separate scripts (for the slider, for pop-up windows and tips) into one file. After that, the combined file can also be minimized (see step 4).
Manually merging files is not very convenient. In addition, in the future it may be necessary to replace one of the scripts. To avoid complications, you should use automatic file merging, for which many CMS have special plugins (for example, Autoptimize for WordPress).
You can also reduce the number of http requests for the browser by setting up caching (step 3) and removing unnecessary scripts (step 6).
If possible, you should optimize the usev of manufacturing email list auxiliary scripts. For example, if sliders are installed on several pages of the site, it is better if the same plugin is used for them.
Read also!
"Website Speed Test: 14 Best Tools"
Read more
Step 7. Using CDN
CDN (Content Delivery Network) is a network of multiple servers distributed across the country and the world. Each such server duplicates the information received from the main hosting of the resource (content duplication is performed at the first request of the visitor). The received data will be stored for some time.
For example, a user from Vladivostok, when loading data from a CDN, will receive information not from the main server, which may be located in St. Petersburg, but from the nearest one storing the required content (it may also be located in Vladivostok). Accordingly, a request along the Vladivostok-Vladivostok route will work faster than Vladivostok-St. Petersburg. The difference will be calculated in milliseconds, but when multiplied by the number of files, this can significantly reduce the page loading time.
Let's consider two options for using CDN:
Loading used scripts . These can be popular jQuery plugins, Bootstrap, WebFonts fonts, etc. For example, you can instruct the browser to load scripts not from the main server, but from Google, Bootstrap, and other CDN servers.
Loading images, pictures and scripts from your CDN . The most powerful Internet resources (Ozon, Avito, etc.) set up their own CDN on their servers or CDN network servers (for example, Google Cloud or Stack Path). The functionality of the most popular CMS platforms already includes CDN support. Thus, Bitrix uses the free plugin "Site Acceleration (CDN)".
Step 8. Reducing the number of http requests
To prevent the browser from sending http requests to the server so often, you should reduce the number of files that it may need to download. For example, you can combine several separate scripts (for the slider, for pop-up windows and tips) into one file. After that, the combined file can also be minimized (see step 4).
Manually merging files is not very convenient. In addition, in the future it may be necessary to replace one of the scripts. To avoid complications, you should use automatic file merging, for which many CMS have special plugins (for example, Autoptimize for WordPress).
You can also reduce the number of http requests for the browser by setting up caching (step 3) and removing unnecessary scripts (step 6).