Lessons
-
Introduction
-
Search engine optimization
- Broken links
- Site map
- Micro-markup
- Robots.txt
- References
- Text
- Duplicates
- Basic
- Pictures
-
Speed
-
Minification
-
Minification of CSS to reduce its volume
Minification of JavaScript files
Minification of inline CSS code
Minification of images without loss of quality
Minification of JavaScript files to reduce its volume
Unused CSS code
Data optimization:Image URLs
Animated image format MP4 and WEBM instead of GIF and WEBP
Unused JavaScript code
Using the WebP format in images
Too high-quality images without using compression
Suitable video bitrate
-
Reducing requests
-
An overabundance of small pictures
Grouping CSS files
Grouping JavaScript files
An overabundance of font files
Availability of end-to-end CSS, JS files
The presence of a monochrome font
Uploading duplicate files
Using JavaScript facades
Redirecting JavaScript code
Adding lazy loading
Redirect from/to www version
- Fonts
-
Loading time
-
Acceptable size of the HTML code of the page
HTML code generation time
The total volume of all images on the page
Total loading time
Total page load time.
Display time of the first graphic
Optimal time to download files from the server
Time to download files from the server under load
Blocking files
- Server Settings
- Pictures
-
The first content
-
The sequence of connecting JavaScript files
Font display mode
Setting up a pre-connection
Removing lazy loading
Long JavaScript code execution time
File upload delayed or on demand
The server is located in the same country where the users of the site live
Requests to another country that cause page loading to be blocked
-
Minification
- Mobility
- Bugs
-
Convenience
- Social networks
- Web Application Manifest
- Favicons
- Basic
- Text readability
-
Security
- Encrypted connection
- Exploits
- Vulnerabilities
Optimal time to download files from the server
The server response time is the period from sending the request to receiving the first bytes of information. The site page consists of dozens of files. A long server response to a request to download content slows down the site.
If the delay in processing the request is periodic, then the problem is high load. The current server resources are not enough to serve all users at peak load.
You can speed up the return of files in the following ways:
- Use HTTP2.
- To prevent the server from compressing the file every time before giving it to the user, use pre-gzip compression or caching of compressed files. So, once compressed text files will not require repeated processing, which will greatly save resources.
- Reduce the size of headlines. Cookies are sent at every request. By reducing them, you will reduce the size of the data transmitted over the network.
- Use a faster nGinx web server.
- Check that service procedures like “Keep-Alive”, SSL handshakes, caching headers are configured correctly. Make sure that the connection to the server is established 1 time and does not reset after downloading each file.
Any comments or additions? Send us an email admin@site-alarm.com .
Check your website