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
HTML Validation
Errors in the HTML code can lead to a breakdown of the appearance and interactive functions. It is also more difficult for programmers to work with poor-quality HTML code. Developing and debugging new features will take more time in the future.
We only check for really relevant errors. Academic compliance with HTML specifications is of little use, since browsers are able to correct various minor errors on their own.
We check:
- Whether the
<html>tag has thelangattribute and whether it is correct. Helps to determine the language of the site. - Correctness of the ID attribute of the elements: format, absence of duplicates, presence of a value. This attribute plays a key role when implementing interactive functions using JavaScript.
- Whether the
<head>tag has content. - Closing tags for elements.
- Correctness of the `autocomplete’ attribute.
- Correctness of the ‘as
attribute in the` tag. - Correctness of the ‘hreflang` attribute.
- Whether the tag is framed
<code>with the `
<
pre>tag.
- Using the meta tagshttp-equiv=refresh,http-equiv=content-typeandcharsetin addition to or instead of the corresponding HTTP headers.
- Specifying the 'width and height attributes for the <img>' tags. Instead, you need to use CSS, since it allows you to set the image size for any screen width. The 'width and height attributes set the same image size for all screens.
- Correctness of meta tags of favicons <link rel=icon>, <link rel=apple-touch-icon>, <link rel=apple-touch-icon-precomposed>, <meta name=msapplication-config>, <link rel=manifest>.
- Correctness of the meta tags of DNS preloading and pre-connection <link rel=dns-prefetch>, <link rel=reconnect>.
- Correctness of <doctype>.
- Correctness of the <meta name=viewport> meta tag.