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
Excessively large images
The area in which the image is displayed on the page has a different size on different screens. For example, if a picture takes up the entire width of the page, then its size will be from 360 pixels on a mobile device to 3840 pixels for an Ultra-HD monitor.
We optimize the image for the following screens:
- Ultra-HD - 3840×2160 pixels.
- Full-HD - 1920×1080 pixels.
- HD - 1376×768 pixels.
- The phone is vertical - 414×896 pixels.
- The phone is horizontal - 896×414 pixels.
- The tablet is vertical - 768×1024 pixels.
- The tablet is horizontal - 1024×768 pixels.
Mobile devices range in width from 360 to 424 pixels. We chose the 414 width as the standard because it is larger than 95% of devices. That is, by optimizing the pictures for it, they will have the maximum quality on 95% of screens, and on all other screens the quality reduction will be no more than 2.5%.
Also, mobile devices and 2K and Ultra-HD screens have a Device Pixel Ratio or DPR parameter. This means that 1 nominal pixel of the site corresponds to from 2 to 4.5 real screen pixels. For example, on a Full-HD monitor and Ultra-HD, all site blocks have the same proportions. But the Ultra-HD screen has 2 screen pixels corresponding to each pixel of the site. Therefore, for Ultra-HD screens, it is better to use 2 times higher-quality images so that they look more representative and more expensive.
Mobile devices can have a DPR of up to 4.5. Such devices can display large images with high accuracy. But then you will have to upload very heavy images that will slow down the loading of the site, and the increased quality will not greatly affect the user’s perception of the site. Therefore, for mobile devices, we recommend focusing on DPR equal to 2.
Here is the code that uses the image of the desired size depending on the screen size:
“language-html
