Therefore, scrolling or zooming is not included. This is why on a site, if there is no user action other than scrolling or zooming, there is no first input delay metric to pass. The method of modifying the first input delay is closely related to TTI and FID. Therefore, the first input delay can be improved by passing JavaScript more efficiently to improve the interaction time. If the browser’s main thread is in use, user input will not respond, so efforts should be made to avoid splitting long tasks or running on the main thread. This keeps the main thread open. Third party advertising and social widgets are known for being greedy when consuming resources on the host page, so they should aim to include as few third-party iframes as possible. One way to improve the first input delay is to delay unimportant tasks until they are requested. To learn more about how to use this method, call it idle to urgent. What is the first CPU idle state of Lighthouse? The first CPU idle time of Lighthouse is to measure most of the time, although the page can have minimal interaction, and most elements are not ready for interaction. If you interact with elements on the page, there may be a delay, but the page responds. The first CPU idle of pagespeed insights is called time to first interactive. Indicates that after the first contentative paint, if there is a task less than 50 milliseconds, the main thread will have the first range of 5 seconds. The first CPU idle receives JavaScript event handlers to return accurate measurements, so it is similar to timeto interactive, but in the first CPU idle, the browser does not have to respond to user input within 50 milliseconds. The 2 to 4 second value of WordPress’s first CPU idle state is approximately average. How can I improve the first CPU idle state? The first CPU idle modification is to minimize the number of resources that must be run before the page is loaded and reduce the size of the remaining resources. This is the same strategy used to improve TTI and FID, optimize important rendering paths, and optimize content efficiency. The user experience Interaction guide lighthouse does not evaluate the entire site. Audit one page at a time, so to understand site performance, you must test various page types on the site. Test blog page, product page, payment, etc. Pay special attention to important switching pages, such as access pages and shopping carts. Lighthouse evaluates six test measures, but when calculating the total score, not all measures are the same. Each weight is different. The measurement item with the largest weight has a greater impact on the overall performance of the page, so it is interactive time. Then there is the order of the speed index, the paint with the first content, the first CPU idle, and the first meaningful paint. The score improvement method found patterns in recommendations to improve the interactive time, the first CPU idle, and the first input delay. These three measures are closely related, so we take a holistic approach to improve them. By improving user interaction, you can improve three areas. To improve your score, you can take the following measures: Optimize critical render paths to minimize or delete critical resources in the main thread. Please postpone the and load asynchronously if possible. Compress or shrink to reduce time and optimize asset size. To shorten the critical path length, all important assets as soon as possible. Image deferred load – image does not scroll
If possible, wait until you need it. If the page is loaded first, and then the visitor scrolls down the page when the main thread has free time, the image can be loaded. Enable browser caching – file caching stores assets in the cache for faster retrieval, significantly reducing the load time of additional pages. Through HTTP caching, the browser saves a copy of the asset ed by the user through HTTP in the cache, so you can search without accessing the server. We recently compared hummingbird with other popular caching plug-ins, and Hummingbird has been optimized. Using CDN – using intermediate caches, such as content delivery networks, can provide you with assets faster in data centers closer to you. Use JavaScript wisely, removing unwanted JavaScript files and unused parts of files. Split large JavaScript files. Delay loading JavaScript files with lower priority. JavaScript file folding and compression Smush Pro has a CDN to help delay loading images. Hummingbird can help enable browser caching. To improve your Google pagespeed insights scores, you can get a free trial of both products here. If this document is helpful or to improve the user experience of the website, please leave a message and let us know. Tag: Google pagespeed website
