Lessons
-
Introduction
-
Search engine optimization
- Broken links
- Site map
- Micro-markup
- Robots.txt
- References
- Text
- Duplicates
- Basic
- Pictures
-
Speed
-
Minification
-
CSS minification
Minification of JavaScript files
Minification of inline CSS code
Minification of images without loss of quality
Minification of JavaScript files
Unused CSS code
Data optimization:Image URLs
Format of animated images
Unused JavaScript code
Using WebP
Image compression is missing
Video bitrate
-
Reducing requests
-
An overabundance of small pictures
Ungrouped CSS files
Ungrouped JavaScript files
An overabundance of fonts
Availability of end-to-end CSS, JS files
The presence of a monochrome font
Uploading duplicate files
Using JS facades
Redirecting JavaScript code
Adding lazy loading
Redirect from/to www version
- Fonts
- Loading time
- Server Settings
- Pictures
- The first content
-
Minification
- Mobility
- Bugs
-
Convenience
- Social networks
- Web Application Manifest
- Favicons
- Basic
- Text readability
-
Security
- Encrypted connection
- Exploits
- Vulnerabilities
An overabundance of small pictures
To download a file, the browser spends time on service operations. It is constant and does not depend on the speed of the Internet connection. That is, it may take 1 millisecond to download a file, and up to 100 for service operations.
To speed up the site, programmers group many small icons into one large file. This is called sprite layout.
It is better to transfer some SVG images to a CSS file. For example, it is more reasonable to place the site logo from the header in a CSS file. This way you will reduce the number of requests and reduce the total size of the transmitted data due to better compression. So if the CSS file weighs 100KB in compressed form, and the logo in SVG is 20KB, then when combined, their size will be less than 120KB. This is due to the features of GZip compression algorithms.
Lesson on using sprites. [Service for generating SVG sprites](https://svgsprit.es /).