Lessons
-
Introduction
-
SEO
- Snippet CTR
-
Indexing
-
Headings H1-H6
Images have the alt attribute.
The Title attribute of links
Splitting the page into HTML5 sections
Content robots.txt
Duplicate "title"
Duplicate "description"
Human-understandable name of the picture
Rules for formatting text on a page
Micro-markup format requirements and recommendations
Validation microdata Google
Human-friendly link format
Errors in Robots.txt
The content of the site map
The site map file
Link formatting requirements
Hreflang tag
"canonical" tag
Spelling of interactive interface elements
-
Speed
-
Number of network requests
-
An overabundance of small pictures
Grouping CSS files
Grouping JavaScript files
An overabundance of font files
Redirects when uploading files
Availability of end-to-end CSS, JS files
Uploading duplicate files
Using JavaScript facades
Redirecting JavaScript code
Redirect from/to www version
Using sprite technology
The video player is connected correctly
- General assessment
- Caching
- Showing the first content
-
File size
-
Minification of CSS to reduce its volume
Server GZip compression function
Minification of the embedded JavaScript code of the page
Acceptable size of the HTML code of the page
Minification of the embedded CSS code of the page
Minification of images without loss of quality
Minification of JavaScript files to reduce its volume
The total size of all images on the page
Unused CSS code
Font Optimization
An overabundance of monochrome icons
The presence of a monochrome font
Data optimization:Image URLs
Animated image format MP4, WEBM, SVG instead of GIF and WEBP
Unused JavaScript code
Cropping monophonic fields in images
Using the WebP format in images
Too high-quality images without using compression
Suitable video bitrate
Excessively large images
-
Slow files
-
HTML code generation time
Title "Keep alive"
Optimal time to download files from the server
Using the modern HTTP2 protocol to speed up the site
Adding lazy loading
Long JavaScript code execution time
Time to download files from the server under load
The server is located in the same country where the users of the site live
No requests to another country that cause page loading to be blocked
Blocking files
-
Number of network requests
-
Mobile adaptation
- Broken layout
- Compliance with guidelines
-
Software errors
- Code
- Mail operation
- Availability
- Server software
-
UX User Experience
- Text readability
- Logic and convenience of the interface
- Visual defects
-
Integration with programs
-
Phones without a clickable link to start a call quickly
Links for Email addresses
Manifest validation.json with a list of favicons
Snippets of the site when sending links in social networks and instant messengers
Tag for specifying a large favicon
The BrowserConfig file
Apple touch bar icon for Mackbook pro
Favicon.ico file
-
Vulnerabilities
- Code
-
Server Settings
-
Uploading all page files via HTTPS
Strict-https header for increased security
Private access to service files
Encrypted IPv6 connection
Enabled error display in the north
SSL certificate validity
HTTPS Availability
Redirects to protected
Vulnerabilities of a secure SSL connection
HTTP headers for increased security
- Third-party software
Font display mode
When connecting custom font files on the site, you can set a strategy for displaying text on the page.
The standard auto mode hides the text display for up to 3 seconds while waiting for the file to load. If the file did not have time to load, then the text is displayed using a spare font. If you specify the swap mode, the text on the page will be displayed immediately using the replacement font. But at the time of downloading the font file, users will see a change in the text style. 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 requires additional calculations on the user’s computer or phone, which slows down the loading of the page.
For these 2 reasons, use auto mode.
There is another good reason to hide the text in the first 3 seconds 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”. If you show the text right away, the user will see a pile of blocks and stuck lines in the first moments of loading the page. 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.
Demonstration of the operation of different text display modes:
<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<style>
@font-face {
font-family: 'roboto-regular';
font-style: normal;
font-weight: 400;
src: url('./wrong.php?font=1783232591.338') format('woff2');
unicode-range: U+21-23,U+25-5F,U+61-7E,U+AB,U+BB,U+401,U+410-44F,U+451,U+2013-2014,U+2018-2019,U+201C,U+201C-201E,U+2026,U+20BD;
font-display: swap;
}
body {
font-family: 'roboto-regular';
}
.btn {
color: #000;
display: inline-block;
margin-bottom: 5px;
text-decoration: none;
padding: 5px 10px;
border: 1px solid #000;
border-radius: 5px;
}
.btn:hover {
background-color: #ddd;
}
.btn.active {
background-color: #000;
color: #fff;
}
</style>
</head>
<body>
<a class="btn active" href="./wrong.php">font-display: swap</a> <a class="btn " href="./wrong.php?mode=auto">font-display: auto</a>
<h2>Файл шрифта загружается через 1 секуну. При font-display равном swap текст отобразится сразу и вы увидете шрифт по умолчанию. В режиме auto текст будет скрыт, ожидая загрузки файла.</h2>
</body>
</html>