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
Long JavaScript code execution time
The execution time for a separately loaded JavaScript file is 0.05 seconds. And the total of all inline scripts in the HTML code of the page is 0.15 seconds.
The long execution is due to the following reasons:
- Not optimized JavaScript code. Code that does not perform the task in the fastest way. It is necessary to rewrite such code so that it continues to perform the same task, but requires less computing resources.
- Large JavaScript file. There are files larger than 1 megabyte. For example, the Google captcha code weighs 900 KB. Postpone the download of similar files so as not to delay the page loading.
JavaScript code optimization
First of all, you need to find the problem area of the JavaScript code. To do this, you need to profile it. Profiling is a measurement of the speed of execution of different sections of the code. These can be either individual lines or entire functions. This can be done in 2 ways: by placing beacons with runtime output and using a special profiler built into the browser ([FireFox] (https://profiler .firefox.com/docs/#/) Chrome).
The beacon for measuring the execution time of a section of code looks like this:
language-javascript
console.time('name');
// Here we have the code for counting the time
console.timeEnd('name');
// Output "name: 3241ms - timer is over"
At the beginning of optimization, you need to find a function whose execution takes several tens of percent of resources. The easiest way to do this is with the help of a profiler built into the browser ([FireFox](https://profiler .firefox.com/docs/#/) Chrome).
After you have found a slow section of the code, you need to investigate it and find ways to optimize it. The following solutions may work:
- Find a specific JavaScript API method or string that takes a long time to execute and try to rewrite them.
- Simply remove the slow code, if possible.
- Call this code not immediately, but after loading the page.
Profiling and code optimization is one of the most highly qualified works in programming. Solving such problems is a great way to grow professionally.