Minimizes main-thread work
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Reduce the time it takes to display the first page elements
How to solve the problem:
Use HTTP caching
Reduce the number of external scripts and stylesheets that could block rendering
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.
The amount of time it takes for the page to become fully interactive is good
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
The page responds, on average, to most user input in a reasonable amount of time
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
Your site responds lower than 50ms to user input (Estimated Input Latency)
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.
Minimize Critical Requests Depth
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Collection of useful page vitals.
Lists the toplevel main thread tasks that executed during page load.
Network Round Trip Times
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.
Server Backend Latencies
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.
Total blocking time
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
The Time at which the user feels that the primary content of the page is visible is good
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Your content of a page are visibly populated fast
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.