I ran a website through the Google pagespeed insights tool. Have you ever received such a message: \
An important part of a good online user experience is an ultra-high speed website. Because the faster the website loads, the higher the conversion rate. However, many website owners believe that what they do is in the best interests of visitors, so they sacrifice the speed of the website in order to attract attention or provide wonderful new features. Unfortunately, many site visitors are more interested in the time it takes to load the site than these additional notifications. In order to make the question more interesting, Google has repeatedly emphasized that speed is the ranking element of SEO. This is the first time that Google officially released it on its blog in April2010, and Matt Cutts of the web garbage group explained this decision further on his blog. The
Eliminate hummingbird and rendering occlusion problems, and get too fast Pages – free wpmu dev members of your website roam slow sites with the same poor user experience. Google is very focused on providing a good user experience. Obviously, this does not mean that your site is completely invisible in search engine results. This also means that Google can scroll the site at a slower rate, thereby scrolling a limited number of URLs on the site. Therefore, this article will explain the meaning of Google pagespeed’s \
Male Google pagespeed insights helps identify website elements that slow down page loading. So, how slow is too slow? John Mueller of the Google Web master help topic replied that more than 2 seconds would be considered too slow. After two seconds, if there is no blank screen on the page for more than two seconds, it means that there is a problem and readers will leave the site in droves. It is possible for a page to load slowly after two seconds. This is Gomez. COM and Akamai. The research conducted by com further supports this point. The results showed that 47% of consumers expected that the web page would be loaded within 2 seconds, while 40% gave up websites that took more than 3 seconds. Load. The
These results show that website speed is important not only to the eyes of Google, but also to the eyes of ordinary website visitors. If you don’t know how fast (or slow) your website loads, it’s best to start the pindom tool. This service will tell you how long it takes to analyze and load the site. To get a deeper understanding of Google’s scores, you just need to find out what slows down the site and what you can do about it, and then have Google Page Speed insights. Generally speaking, the score is above 90. However, if you do nothing to optimize the page speed, the score will be much lower than this value. The biggest reason why scores tend to be low is discharge
You will notice that this is an uncompressed image and rendering blocking issue. The
Images that are not properly compressed are self explanatory. But what is the problem with preventing rendering? Common rendering occlusion problems, especially word press. The most common rendering occlusion problems are JavaScript and CSS. Before you need to start scrolling down, load from the website area or content that can be viewed without scrolling. Unfortunately, they are also part of an important rendering path. That is, you can’t expect the site to display and run normally except for complete exclusion. Let me explain what it means. Typically, a web page consists of an HTML file that contains the structure of the web page. This file includes a CSS file that is responsible for adding visual styles, and a link to a JavaScript file that adds additional functionality to web pages such as animations, scrolling trigger pop ups, or pop ups. The
An important rendering path is a series of events that occur to render (display) the initial view of a web page. Optimizing these events will greatly speed up the web page. Once you understand how important rendering paths work, you can appropriately apply the changes required to quickly load web pages. The most basic important rendering paths are: The browser the HTML file. The browser reads the HTML and confirms the CSS file, the JavaScript file, and the three additional files for the image. The browser starts ing images first. Browsers realize that they cannot display web pages unless they first import CSS and JavaScript. The browser and reads the CSS file to ensure that no other file is called. Browsers realize that web pages can only be displayed when JavaScript exists. The browser and reads the JavaScript file to ensure that no other file is called. The browser can finally display the web page. In essence, this means that the browser must load and read CSS and JavaScript files before the website displays anything. Visitors stare at the empty screen until this happens. The
Now, imagine how important rendering paths are displayed on a website with multiple CSS files, JavaScript files, images, social media buttons, multiple audio files, PDF files and other attachments and lists. It’s easy to see that things will soon get very bad. Especially for word press, it is too common for a theme to contain multiple CSS and JavaScript files. Adding a large number of plug-ins that tend to be installed will make the situation more complicated and cluttered, thus reducing the loading speed of the website. All this means that when we talk about the importance of page speed and ranking factors, the time users need to wait before they start viewing content, and the speed at which they start interacting with content. The
With regard to page speed optimization, the main concern is to reduce the time required for users to view content and interact. This means that you must do everything possible to optimize important rendering paths. Let’s look at several ways to solve these problems. CSS CSS files that prevent rendering are the look and feel of the web site. Define the color, font, and layout of the web page. The more CSS files, the larger the file, and the longer the browser takes to read the file and display the website. There are several ways to handle CSS that prevents rendering. The
To call CSS files correctly, reduce the number of CSS files on the critical path and reduce the use of CSS in general. 1. call CSS methods correctly
There are two ways to invoke CSS that you need to avoid@ Conditional CSS files with import and inappropriate tags. The @import method that calls CSS is located near the top of the regular stylesheet, as follows:@ Import URL (\
Instead, it is recommended that you copy the contents of the imported file and paste it into the original style sheet. Or, delete the row completely from the source stylesheet and include the CSS file imported with the following code line in the HTML file. \
This is a call to all other social media artifacts such as JavaScript files, Facebook like boxes, or google+ profile badges. This is only part of the solution, because browsers still don’t allow you to load a web page first and then a JavaScript file a second time. In the end, this method will still affect the website speed. A better solution is to defer JavaScript entirely. This will be completely removed from the important rendering path and will greatly improve the page speed. In the HTML that generates the \
