Performance
99  / 100
First Meaningful Paint
1,753  ms
Consistently Interactive
1,753  ms

Eliminate render-blocking resources

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Serve images in next-gen formats

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Your website reacts quickly on user input

Max Potential First Input Delay (FID) describes the delay between a users input and the website's reaction. Your FID is very low, granting your visitors an instant user experience.

Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn more.

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Remove unused CSS

Remove unused rules from stylesheets to reduce unnecessary bytes consumed by network activity. Learn more.

Your images are perfectly optimized

Optimized images load faster and consume less cellular data.

Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Server response times are low (TTFB)

Time To First Byte identifies the time at which your server sends a response. Learn more.

Preload key requests

Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more

Avoids enormous network payloads

Large network payloads cost users real money and are highly correlated with long load times. Learn more.

Uses efficient cache policy on static assets

A long cache lifetime can speed up repeat visits to your page. Learn more.

Avoids an excessive DOM size

A large DOM can increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

JavaScript execution time is optimal

Your JavaScript files take little time to be interpreted or executed.

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

Possible Cause: The First Contentful Paint is the time when elements such as text or images are loaded from the DOM for the first time. If the browser has to load many JavaScript or CSS files right at the beginning, it can extend the time until the FCP occurs. This can also result in long Server Response Times.

How to solve the problem:

  • Minimize the download size of JavaScript and CSS files
  • Compress and minify your JavaScript code
  • Use HTTP caching
  • Reduce the number of external scripts and stylesheets that could block rendering

Show detailed information

Preconnect to required origins

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.

Diagnostics

Collection of useful page vitals.

Tasks

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.

Your users instantly see the primary content of your page

First Meaningful Paint measures the time in seconds the browser needs to render your primary content above the fold. A short First Meaningful Paint provides your users the feeling of a fast loading website.

Your content of a page are visibly populated fast

Speed Index shows how quickly the contents of a page are visibly populated. Learn more.