How To Optimize Blog High Pagespeed Insights - How2Stuff

How To Optimize Blog High Pagespeed Insights -->

Sunday, December 22, 2019

How To Optimize Blog High Pagespeed Insights

How To Optimize Blog High Pagespeed Insights
How To Optimize Blog High Pagespeed Insights: Google Developer's PageSpeed ​​Insights is very useful for blog optimization. Most bloggers want the best performance of their site by doing SEO optimization and expect to get the best SERP in google search results.

Then on what platform do the managers take the correct reference or benchmark? yes, what is clear in the Google alias search owner. What does Google value on pagespeed? of course the speed and performance of the site that you manage, of course. And of course, there are many aspects that affect the pagespeed score itself and simply if you refer to the following review

What is Google PageSpeed ​​Insights (PSI)?


PSI is a way for Google to assess the performance of your site with the step you include the desired blog page and then a score will appear as a result. Please check your site's performance score on Google PageSpeed ​​Insights. The score includes both mobile devices and desktop screens. There are six things reported about site performance and in what parts are recommendations for improvement (audit) on these aspects:

1. First Contentful Paint (FCP)


FCP is a value obtained based on the time taken to load text and images. The speed in loading text and images on a page means that it has something to do with the audit of the following:

  • CSS Render-Blocking: Blocking rendering very often occurs when views are loaded by relying on overlapping CSS, while over-using CSS to overlay layout will only burden rendering.
  • Loading Third-Party JavaScript: Like CSS, scripts also need time to load a view. More and more JS is used at the wrong time it will hamper the running rendering process. JS that is loaded internally are usually heavier than using Third-Party (third party) by means of external hosting. 
  • Optimizing Encoding and Transfer Size of Text-Based Assets: In terms of text and image compression, there is a need for a mild default font selection and compression dimensions of the image that will appear. Reducing writing styles such as icons in various formats will reduce the rendering performance as well as the optimal image size according to layout also needs to be considered.
  • Optimize JavaScript bootup: Still related to JS issues, there are special tricks to compress JS programs to minify (minimalist) with parse or compile techniques. Thus, it will ease the rendering because the writing format of the program has been changed to a minimum. But if the JS is not used it would be nice to just delete it.


2. Speed ​​Index (SI)


SI - The index speed on the page is judged by how fast it takes until the display appears as a whole on the screen. A good indication according to the Google developer is to conduct an audit or improvement of the following:

  • Optimizing Material Efficiency: The material in question is fundamental (basic) regarding the weight of the file in the display that is loaded on the site. Did you know that when content is opened through a browser it has a file size in units of bytes (bits)? If imagined assuming, for example, a CSS file, JS, images, text, and videos that are loaded together on one page, of course, you are downloading the file to your device, right? Most SEO experts recommend using a CDN (Content Delivery Network) so that the file is loaded just once without repeating download views. So that the traces (cookies) left on the browser can still be used to be loaded again.   
  • Optimizing the Rendering Path Important: Because this has something to do with the speed index by Google, then you need to understand that the browser (browser) has a series of processes to load important resources on your site. These resources must appear first according to assets (CSS, JS, text, images) in a minimalist form (minify). For example, in external CSS or JS that is inserted into the html structure of the site is still placed separately, then you can outsmart by combining the two into one path.


3. Time To Interactive (TTI)


TTI is the time it takes the browser to respond to a view so that the page can interact fully. Then to pass the audit or improvement can be done with the following:

  • Measuring Performance with the RAIL (Response-Animation-Idle-Load) Method: If your site has a display that uses simple animations such as image content loaded with a rotating loading animation, or a text that moves when the cursor is directed, then you need to reconsider its use. Because the animation must successfully respond to less than 10 milliseconds when the entire display content has been loaded full of less than 100 milliseconds, for reference, can be read here.

4. First Meaningful Paint (FMP)


Is the time needed to capture important information on the content of a page? Like the speed index (SI), the audit method is the same as optimizing important rendering paths.

5. First CPU Idle


Intended CPU idle is how much influence the process of loading content on the CPU used on the device (mobile or desktop) when the browser (chrome, Firefox, etc.) renders a site page. This has to do with the number of bytes (bits) produced by the page files that are loaded. To pass the audit is the same as TTI and FMP, namely the efficient optimization of material and the most important rendering path.

6. Max Potential First Input Delay


First Input Delay (FID) in question is a pause or delay that occurs as a whole when loading content in milliseconds (MS). So, to pass the audit, you need to be able to study it in "User Focused Performance Metrics" here.

Google Pagespeed Insight Score


The audit review above can be applied by you by making real-time improvements using the Chrome webstore extension, Lighthouse. Thus, the best score results will appear in accordance with the expected PageSpeed ​​Insights. 

Install it on your chrome browser, because it is very useful to see the results of your blog score and performance along with solutions to fix things in detail directly from the Google developer

NEXT ARTICLE Next Post
PREVIOUS ARTICLE Previous Post
NEXT ARTICLE Next Post
PREVIOUS ARTICLE Previous Post
 

Delivered by FeedBurner