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
Font display mode
When using your font files on the site, you can set a strategy for loading and displaying the font.
We recommend using the auto mode, which is used by default if the font-display property is not set. If you select `swap’, the text on the page will be displayed earlier, but then users will see the font change during loading. At this point, the text will “twitch” and it will be perceived as a “glitch”.
Also, after the download of each font file is complete, the user’s browser will “recalculate” the size and location of the blocks on the page, as the height and width of the letters change. This creates an additional load on the user’s computer or smartphone.
There is another good reason to hide the text in the first half second of loading. At this point, the CSS files that form the basic framework of the page have not yet loaded and the blocks on it represent “porridge”. The user will momentarily see a pile of blocks and stuck lines. This will negatively affect the overall impression.
The auto loading strategy allows you to save the user from contemplating a “glitch” when loading fonts and “porridge” from text blocks.
A detailed article with code examples is available [here](https://webformyself.com/css-font-display-budushhee-rendera-shriftov-v-vebe /). Official documentation here.